Related
Hi all...
I've been getting a lot of suspicious errors recently (force closes and app shortcut names disappearing) and I'd like to go from apps2sd back to just a normal setup with my apps on the internal phone storage.
Can somebody please verify that the instructions here are up to date? I'm a little nervous about wiping my data (or bricking my phone).
http://wiki.cyanogenmod.com/index.php/Apps2SD
Also, can somebody tell me whether doing this will wipe out the (single) app I paid for from the Marketplace? If so, can I redownload it, or will I need to pay for it a second time?
I originally got apps2sd set up by using the recovery ROM prior to flashing Modaco's custom ROM v1.1.
The easiest thing to do would be to load the new RA 1.5.1 recovery image.
Then boot into it.
Go to Partiton SD
Select FAT EXT3 SWAP
and then set the partition sizes of EXT3 and SWAP to 0
Is there a reason you want to do this???
This runs a very very minimal chances of bricking your phone. The other method on that Wiki page has more potential to get you in trouble.
Did see the market place question.
There is a method laying around somewhere to copy all of your apps back to the phone instead of loosing them. Restoring a Nandroid backup would likly put them all back into the /apps/ directory sd card or not. apps2sd just changes the location of that directory really.
But the market does keep track of your google account and what apps you purchase, you wont have to re purchase (maybe on a totaly new handset).
hope my jiberish has made sense
jashdlfjasdhfjablgjkasgjlkasfhlajshf
At first I was interested in the whole apps2sd process, but have yet to implement it on my rooted, Fresh 1.0 Hero since so far, I haven't really seen a need for it.
But if you were to 'turn on' apps2sd and then decide later that you don't want it, there's a possibility of bricking?? Although I assume you can always reflash the RUU if something like that were to happen? Hopefully?
Think I'll stay away from the whole offloading applications thing for awhile.
mkhopper said:
At first I was interested in the whole apps2sd process, but have yet to implement it on my rooted, Fresh 1.0 Hero since so far, I haven't really seen a need for it.
But if you were to 'turn on' apps2sd and then decide later that you don't want it, there's a possibility of bricking?? Although I assume you can always reflash the RUU if something like that were to happen? Hopefully?
Think I'll stay away from the whole offloading applications thing for awhile.
Click to expand...
Click to collapse
The possibilities of bricking the phone are very slim, but they still exist. If a phone is truly a brick, not even RUU can help. RUU has to be able to detect the phone is there in Windows, so if its beyond that RUU is useless.
Nothing to worry about as long as follow the *usually* very well written step by steps across the interweb.
If it makes you feel any better I have only heard of one or two people to brick the Hero. Most things are recoverable.
Yeah, sorry, I didn't expect it would brick the phone so much as badly mess it up - like if it expects to run apps from the SD card and they aren't there I could see the phone being tough to use as a phone, but it wouldn't really be "bricked" in the sense of not responding to user input at all.
As far as why I want to do this, I haven't really seen a huge need for apps2sd yet, and when I was recently helping an app developer to debug their app it was just one more weird variable that seemed like a possible source of problems. I'm also hoping to start developing apps myself soon, so having a more vanilla phone seems like a good idea. (I also was influenced by the Fresh ROM apps2sd rant, to be honest.)
Anyhow, thanks for your replies. I'll probably repartition the card from RUU and then restore from Nandroid at that point. Will a repartition wipe the card filesystems out, or is the partitioner smart enough to preserve the existing data?
What I did is RUUed back to 1.2, OTA updated to 1.6
Flashed to the 1.5.1 image
(At this point I went to mess with the partitions and there was no ext)
Flashed to Fresh 1.0
Hey Guys,
Being a PC overclocker I felt like a fish out of water when it comes to overclocking a phone
I recently got a HTC Wildfire and found out how to root it and flashed my own ROM, Kenral etc. (with some difficulties)
So I downloaded SetCPU and started OC'ing. Being a PC overclocker I followed the logic of set speed and run stability test.
So I slowly started upping the max speed and then stress testing for 20 min odd. I just kept on upping the speed until I got to the limit of SetCPU (768Mhz). Where to from now?
I have not changed the minimum speed because I have read that it can make your phone rather unresponsive.
Is it possible to go above 768Mhz or will I damage the phone or have to up voltage?
I ran linpak and at 768Mhz I got just under 3 MFLOPS. Is that good or bad or what?
Thanks in advance guys
Mikrouwel
768 is the safe limit, you'll need to make a kernal that will allow the processor to go further, 3mflops is good on a sense ROM but on an AOSP ROM you will get over 5 easily. Why do you want to go over 768 anyway?
What is the difference between sense and AOSP ROM? If it is just the sense feture then I dont mind changing ROMS. (Dont use sensce)
Also what is Cyanogenmod 7 RC1? Is it the same os CM7? Seem alot of people talking but dont now what it is?
Thanks
Mikrouwel
AOSP -> Android Open Source Project. It is vanilla Android, without Sense. So Yes, your assessment is correct. It is just the Sense feature.
Cyanogenmod 7 = CM7. Just a short way of writing it.
Hi There
Is Cyanogenmod 7 a ROM?
Also is Android Open Source Project ROM too or a app?
Sorry kinda confussed
Also what is Clockworkmod Recovery? Does it have something to do with ROM Manager?
Thanks
Mikrouwel
1: Yes, CM7 is a ROM
2: AOSP Official Page: http://source.android.com/
3: Recovery Images are found whenever you boot into Recovery. Example: All that you see like Clear Cache, Install ZIP from SDC etc. are part of a recovery. ROM Manager is a standalone app and is not related to Recovery, although, it can help update the recovery since the developer of Clockworkmod Recovery and ROM Manager are the same.
Technical Definition of Recovery: (Sourced from Turkeys Ultimate Guide Glossary)
The recovery partition is a boot-mode for your phone that allows you to wipe your settings from the #data partition of the phone (a hard wipe), or perform an update using an update.zip file on the root of the microSD card. It is common (although not necessary) to flash a patched Recovery image, such as Amon RA's one. This allows you to run Nandroid backup from the device, and flash modifications, such as update.zip files to the device, essentially becoming a means to install sotware to the device. Recovery mode is separate from 'normal' mode, and can be entered by holding down home whilst turning the phone on.
Oh, you should probably go through Turkeys guide and glossary yourself. It should help a lot.Thread : http://forum.xda-developers.com/showthread.php?t=824396
Glossary : http://bit.ly/9HtICk
Many thanks Guys,
ATM I am using this ROM with this kernal. Were can I download CM& and will the notiable differences be between the one im using and CM7?
Also what is New Nightly? (You have #13 next to yours?)
Thanks alot guys
Mikrouwel
CM7 can be found here:
http://forum.xda-developers.com/showthread.php?t=918072
Or, the latest, i.e. RC2 can be found here:
http://forum.xda-developers.com/showthread.php?t=957140
Nightlies are automated builds created by the Build bot. If you check the first link I posted, in that post's download link, you will find new nightlies everyday. Nightlies implement minor code changes, and, are experimental releases. They may add new features (eg: Nightly #11 implemented Android 2.3.3, #13 implemented FM Radio etc.), but may also add new bugs sometime.
As for differences, one cant say for sure, since ROM preference is a personal choice. Try it, if it suits you, use it, else, switch back.
Hi There,
I am going to try CM7.
IS the RC2 stable and if so is it more or less stable than RC1?
Also if I just go into recovery and flash will I have to flash nightlys or not?
If I am not mistaken it runs 2.3 and I thought that there were many features that didnt work on 2.3? (Gingerbread)
Also what kernal do you recommend I should use on CM7 that will let me got 768+?
Many many thanks guys for all the help
Oh yes and what app do I use if I want to keep all my apps and contacts and stuff like that? I used titanium backup last time and only got like half the stuff back?
Thanks Guys
Mikrouwel
* RC2 is stable for me. No issues so far, although camera sound bug is still there - If you take some pics using flash, phone loses all sound and you have to reboot.
* After RC2, it is upto you whether you want to flash nightlies or not. There is no compulsion.
* Can you list some features that dont work on 2.3? Personally, I cant find anything amiss over 2.1 / 2.2
* CM7 comes by default with an overclocked kernel, which will allow OC to 768. Overclocking beyond 768 is not possible since that is the safe limit for the Wildfire's CPU. Because it is overclocked by default, if you get a bootloop, flash HCDR.Kernel v4.1 after flashing CM7. This will restore stock clocks, but, still allowing OC using an app like SetCPU
* Apps can be backed up using Ti backup / Mybackup Pro etc. Contacts can be backed up by going to Contacts > Export > To SD Card. Then, after flashing, again going to Contacts > Import > From SD Card, and select the VCF File. SMS'es can be backed up by using the free SMS Backup App from the market.
Hi everybody...
I know I'm not a dev, but I like to explore my android phone. So you are developing, and right after i'll be trying to do it... on my own
I believe I followed all the steps refered in x8 overclock module thread in devs section, but since I can't ask this there, i'll ask it here.
1st - Download and unzip x8oc.zip (the right version), then copy x8oc.ko to system/lib/modules (I'm sure the file is there, system is mounted rw).
2nd - Edit hw_config.sh on pc with notepad++ (my edited file is attached) and "glue it" back to system/etc after editing.
3rd - Reboot... and then what?! It reboots, but when I go to set cpu, I have same frequencies as before (122-600mhz). So, my x8 is not overclocked right?!
Beside this steps do I need to do something else?! In set cpu, do I select any device configuration or just auto detect frequencies?!
Do I need to set custom frequencies in any other files?!
I've just tried lot's of changes and nothing worked.
Please help me on this...
I'm using floyo 0.15 on my x8, rooted and with xrecovery on it...
Thank you all
the attachment is correct..and don't change the set cpu. i use the same roms like yours
Do you think that having baseband version 006 instead of the 015 could be the cause for this problem? I never updated it...
Because, I've done it again without touching set cpu and still no overclock... If you say it's correct, then I really don't know what else could it be...
Thank anyway for the reply
I think it is very influential on baseband cuz for the rom said that use xx15,...if yours non xx15 so try to change it ...what you've applied on the hw_config is same on mine so it's quitely correct.
Hi mate
So, I'll tell you what i've done.
Went to SE's site and repaired to the original 2.1 so restarted the phone, updated to baseband 015, then root, then xrecovery... and then, installed miniCM. As you know, miniCM has an update.zip to easily overclock it to 710MHz.
I tried it and it worked fine. BUT! I prefer Floyo 0.15 (the best till the moment for me) and so I tried to do something, when I restored back to Floyo.
Adding the code to the original hw_config.sh in floyo's file didn't work again. So I thougt... Let's trie to put MiniCM's hw_config (the file that comes in the update.zip) to floyo's system. And... It's working FINE!!! I'm currently running at 749(x27)Mhz and it doesn't go off... it's stable. Also handles 767(x28)Mhz but it's not so stable. Now I'm really satisfied with my overclocked x8.
But there is one reason that made me think of where was the mistake.
When I opened floyo's original hw_config and added the code, in notepad++ it was apparently correct and the visual configuration of the file was equal to miniCM's hw_config file (already with the code). But, when I opened the both in wordpad, the file I edited had the same format as in notepad++ and the file from MiniCM had all together and a different layout. So I thought that it was possible that android wasn't reading the file well, since the configuration of the code was different. And it worked so smoothly
So my question is, does notepad++ write in the language needed for this to work?! or is there anything needed to change in order to make it legible to android system?
Thanks again
Sorry for all this noob questions, but since you use the same rom as mine, it's a good chance to ask what I don't know. lol
Our rom comes out with app2sd pre installed right?
So it was suposed that I could move some programs to sd.
But, when I go to settings/apps manager There's the option to move apps to sd, but they all say "fail moving the app".
What do I have to do to make it work well?! Heard that the sd had to be partitioned. What program did you use to do that?!
That's the only thing left to make x8 perfect and full of memory lol
Thanks
I managed to OC it manually to 710 MHz in miniCM6, BUT no performance increase was detected. Quadrant score was consistently lower (~750) compared to no overclock (~850),
Any ideas?
I OCed it to 719MHZ with miniCM and i really felt an improvement. Switching menus and sliding on the home-screen (GO launcher) is really smoother.
Quadrant-Standard-Score:
@600MHz (ON DEMAND): ~520
@719MHz (PERFORMANCE): ~920
MaScXDA said:
I OCed it to 719MHZ with miniCM and i really felt an improvement. Switching menus and sliding on the home-screen (GO launcher) is really smoother.
Quadrant-Standard-Score:
@600MHz (ON DEMAND): ~520
@719MHz (PERFORMANCE): ~920
Click to expand...
Click to collapse
and about battery life, noticed any difference after OverClock your Phone?
biscoitu said:
and about battery life, noticed any difference after OverClock your Phone?
Click to expand...
Click to collapse
it drains a bit faster with the PERFORMANCE-govenor, but my phone is loaded every night anyway.
It is even less important to me, because when it reacts faster, i don't need to have it turned on as long as when it is laggy. And the display really needs most of the battery-power, so i may even save battery, when i can turn it off earlier.
Return to 600mhz
I can not use the overclock because when I reboot the phone it is on 691Mhz soon after he returns to 600mhz. I know that the CPU clock is dynamic, but he never returns to 691mhz. What did I do wrong? I used the XDA tutorial for overclocking.
Don't work yet
I just try full wipe and did not work. I think it's some parameter or file permission...
Since i had a lot of PM of people who want explanation to install this ROM
I make this little thread for you.
Notice that i don t make this rom i only test it and make the nandroid image
to know more about that you can read the Mioze7Ae thread here
And for those asking for the performance I try almost all the rom and this is for me the fastest and (with the sileshn theme include) it s also the most beautiful...
I had between 70 to 80 Mo RAM available without swap. With swap i reach the 95 100Mo!!! (I attach my boot.img files too but it s the first fjfalcons').
Here you can find a tutorial to fastboot boot.img to enable swap.
And it works in multilangage (i don t know which but in english spanish and french without a problem)
To enable app on sd and swap you must have your sd part in this way: a fat32 part for the media / a ext3 part / and a swap part
You can find a video guide here on his channel(you will have to search a little but i remember its called 8min Linux...) made by reverendkjr
I make another image and i test it 3times (from sbf to the end...) so all works !!!!!!
For the beginners i will come back to the sbf.
1. SBF
So I m using the Singapore SBF I think you don t need it to get it work but it s better for those who have problem to change it too (it seems to work in every country)
So you can find the singapore sbf here
And you install it wiht RSDlite (do a google search): first put your phone in bootloader mode (when the phone is off you hold the camera and the volume up button while powering up) then you select your sbf and flash it.
2. Recovery
Now you have a fresh new system
You have to install the recovery
First of all you will have to install a file explorer form the market (you can use the one you want it will be deleted when flashing...)
Now you have to move the two apk(universal and root and openrecovery) i attach to this post in your sd
you can now install with your file explorer the apks.
Start with universal and root. Intall it and root your device.
Install the open recovery now. (Install it and install recovery system)
Now you must install Androidiani OpenRecovery I think it will work with out but it s easy and the recovery work better with it... So you just have to extract this zip to your sd (overwriting the similar files)
Now you have a working recovery. To launch it just go to open recovery and click on recovery boot (don t forget to copy the nandroid image folder in the sd card/ nandroid/openrecovery before you go to the recovery)
3. Restoring the nandroid image
Now you have a working AOR (androidiani openrecovery) and you have extract the attach nandroid image to sd card/ nandroid/openrecovery folder
Don t forget that nandroid need a folder name with out any space and in this folder you can only have .img or .md5 files.
So in Open recovery you go to nandroid / restore /
And if you don t change the folder name you must have CyanogenTI0808allupdates in the list
You select it and launch an restore all operation.
After that you come back to the first menu and wipe dalvik cache/ cache partition and wipe data / factory reset
Now you can reboot system. And it s done. Don t forget that the first boot is very long (about 5 or 6minutes)
CyanogenTI0808allupdates (the nandroid image)
(made and posted the 08/08/2011)
With all the new update from the official post (until the 08/08)
And the Twisted Inception theme from sileshn (with the update for the white text and the new battery icon)
You have to change the hour color (in settings / Cyanogen Mod / user interface / status bar) (from black to white)
Known issues:
- Fm Radio not working
- Media Gallery button not working
- Recovery boot (from the restart menu) don t work (you have to reboot holding the volume up button)
- Led notifications from the Cyanogen mod menu don t work but Led Me Know works
- Some users have issues with installing payed apps... I never have so....
Just a reminder to new readers: do not flash the fjfalcon boot.img. You have to use fastboot boot boot.img over USB every time.
Mioze7Ae said:
Just a reminder to new readers: do not flash the fjfalcon boot.img. You have to use fastboot boot boot.img over USB every time.
Click to expand...
Click to collapse
Thanks i think i will make a step by step tutorial for fastboot too. Maybe this week
B_e_n said:
Thanks i think i will make a step by step tutorial for fastboot too. Maybe this week
Click to expand...
Click to collapse
I think this is a good idea too. There is already a thread but it is buried in here somewhere and has gaone, as they all do, away from the initial intentions.
does the rom have native support for app2ext?
islubio said:
does the rom have native support for app2ext?
Click to expand...
Click to collapse
Yes It also support the OC on boot with milestone overclock
just installed this n this is so much faster compared to steelblue rom.
N guide was easy to understand. Just awaiting ur swap guide. Thanks.
is the froyo modding in the recovery workable?
how u get so many free ram? i only get 45-50 using adv task killer..
secret_tidus said:
how u get so many free ram? i only get 45-50 using adv task killer..
Click to expand...
Click to collapse
Without my apps i have 95 100Mo of free ram (with out the app2ext I have so nearly 100 apps and it take some ram...)
But with all my apps and with the swap enable I can get between 70 to 80Mo
I don t use advtaskkiller anymore i think it use more ram that it can free
I use autokiller memory optimizer (it change the settup of the android task killer so no useless use of ram) and to kill my apps i use the Go task manager (a widget from the golauncher app)
wat u set at the autokiller memory optimizer?
secret_tidus said:
wat u set at the autokiller memory optimizer?
Click to expand...
Click to collapse
Optimum settings.
But maybe someone have others settings better?
I know some use minfreemanager (already in the rom) but it seems the same than autokiller
b4 reboot the cm6 room was pretty stable... y after i reboot thn it started to freeze?
my 1st fastboot was pretty stable.. can run asphalt6... but the next time ll freeze... bcuz i install chainfire3d have to reboot and i have to fastboot again
even with fast boot i m only getting around 50mb of ram
Here is my Autokiller settings (user set, not pre-set and no fastboot). The work for me after many days/weeks of trial, error and monitoring.
16
16
64
64
70
94
I don't do a lot of gaming but I do listen to quite a bit of online media.
I average around 65-75mb all the time and at the very least 55mb when running Tune-in or Jango radios or Poweramp (memory hog btw but really good media player).
Side note: keep you widgets to a minimum. They eat RAM.
i just encounter some prob when swaped... for the 1st time i swaped it work fine and smooth all the way and no freezing but later on i reboot and try to swaped again my xt started to freeze when run certain apps...
Woodrube said:
Side note: keep you widgets to a minimum. They eat RAM.
Click to expand...
Click to collapse
i don't know about that, I went without widgets for the longest time cause everybody always told me how they eat ram and battery. Now for the past month or so I have had 1-2 widgets on each of my home pages and I really don't see much change. I am keeping the same amount of ram available and battery seems to drain the same. Not much difference, but I could be wrong I would have to go back to no widgets for a day or 2 and monitor my ram to be positive. I do know it isn't nearly as bad as what people say that kept me from using them to begin with.
B_e_n said:
Optimum settings.
But maybe someone have others settings better?
I know some use minfreemanager (already in the rom) but it seems the same than autokiller
Click to expand...
Click to collapse
I use both minfree and autokiller and they seem to work together, I set my autokiller and minfreemanager automatically copies the settings. Don't know if it does much good but doesn't do any harm. It seems to work good
LibertyMonger said:
i don't know about that, I went without widgets for the longest time cause everybody always told me how they eat ram and battery. Now for the past month or so I have had 1-2 widgets on each of my home pages and I really don't see much change. I am keeping the same amount of ram available and battery seems to drain the same. Not much difference, but I could be wrong I would have to go back to no widgets for a day or 2 and monitor my ram to be positive. I do know it isn't nearly as bad as what people say that kept me from using them to begin with.
Click to expand...
Click to collapse
Think of it this way. Say you have a 4x2 or 4x4 widget that is oh say MSNBC or Reuters newsfeed or your Facebook/G+ feed. These not only tax you home screen memory but they are always "running" too. If you have something like Widgetlocker where you can customize your lock screen and put apps or link on it directly, I have found that it munches free RAM really bad (14-17mb). So much so that I don't use it anymore (paid app too).
All a widget is is really just a custom icon that either monitors a running app/service, in which case it itself is running. Or it is running on its own, like a clock or feed or some kind.
Something like mClock or Battstat isn't too harsh, but 3rd party Keyboards can be quite draining too (I use Better kb and it is around 11mb but I like it and have had it since day one).
Good way to check is to go to Settings->Apps->Running Services and each will have the MB on the far right. Anything in double digits is hungry for your RAM.
I know you use that Go widget. Check out how much RAM it is using by going into settings and see if it is worth having it on there. Might be. You seem to be getting good RAM so is it aint broken don't fix it.
First of all I would like to give credit where credit is due and say thank you to SamHaLeKe for all the work he put into this port and all the other Developers involved to bring ICS to the SGS
If you would like a full run down of this ROM and what is included as any new developments, please visit the ROM thread
Now off to the good bits ...
Install
I AM NOT RESPONSIBLE IF SOMETHING GOES WRONG AND YOUR PHONE CEASES TO WORK. THIS IS NOT A DETAILED WALK THROUGH BY ANY MEANS. I AM ASSUMING YOU READ ONE OF THE MANY OTHER TELUS THREADS THAT HAVE THE FULL INSTRUCTIONS INCLUDED TO PERFORM THE BELOW STEPS.
Note: I am not going to post all the links to files as I do not have the time to update them everyday when something changes. I will however post links to the ROM and Kernel threads for your reference.
I decided to start fresh (and I mean fresh) from stock FROYO with a full SD format and the works.
Step 1
Flashed back to stock with ODIN. Again I used FROYO but I am sure GB would work. If you want to start fresh as I did, go to options storage and format the internal SD (13 GB).
Step 2
Download the ROM and Glitch V13 kernel (what I used) and copy them to the SD card of the phone. I suggest removing any external SD as not to copy the files to the wrong spot (guess what I did LOL).
Step 3
Flash voodoo kernel from ODIN to root and install clockwork recovery making sure that you do not repartition in ODIN
Step 4 - Note: The older voodoo kernel gave an "assert failed" error trying to flash the ROM through recovery)
Boot into recovery and wipe cache and dalvik then flash the Glitch V13 kernel from zip and reboot. At this point you will most likely be boot looping but no worries everything is OK
Step 4
Pull the battery and then boot into recovery with volume up + volume down +power. Wipe cache and dalvik and flash the ROM from the ZIP
Let the ROM boot and then again boot to recovery and flash the essentials zip.
Voila you should be running S.U.R.F.A.C.E ICS, aint it beautiful?
I continued and flashed add on packs 1 and 2 but that is up to you
Now for my findings thus far ...
I am in no way a power user when it comes to my phone but I do play with it a lot. I have to say that this ROM seems to be the one of the smoothest to date and seems to take to our device nicely.
Battery has been nothing short of great for me. Through the week I can easily get 2 days out of it (work all day). Now I also try to minimize the drain by turning off whatever I don't need like WIFI seeing as there is none where I work.
I flashed the JL3 modem and it seems to work good for me but then I don't live where you do so you may have better luck with another.
The kernel included in the ROM (if you read the ROM post) is Glitch V14 pre which runs amazing as usual although still in the development stage. This kernel has a lot of new features that I will let you read up on yourself here
The ROM also includes supercharger and thunderbolt scripts (I admit I have little to no experience with these but I do know they help).
No FC's with this ROM other then the video camera but I have seen some posts regarding this and have not got around to working on it but will be I am sure very soon. It looks like just a file update maybe but too soon to tell.
Live overclock seems to work if I leave the voltage settings alone but that could just be a lack of experience in this area but it never hurts to try. If anyone has settings that are working for them I would love to know what they are. I have set the live overclock to 120% or 1.2ghz and it runs fine again if I do not change the voltage.
It's only been about 3 days since the install but this is what I got so far. I would recommend giving it a try for sure.
I know there are a few of us on this ROM so post up your findings here.
Thank you
Buck
Similar but running Glitch v14
Thanks for the write up Buck. I have been running this rom (Surface) for a few days also but I came from cm7 to this one. I have also been toying around with it over the last few days which has gotten me in a few tight spots lol. I have my Volt control set to 1304, no voltage changes and it runs flawlessly. The modem I put on was the JVT which also seems to work well.
What I have learn about Live OC:
First you set your clock speed in Volt control, then flip over to NStools (that is the easy part)
IMPORTANT.... If you choose to mess with this, make sure settings in NStools is NOT set to apply on boot or make sure you have a good recovery to go back to. Found this out the hard way
Click on live oc and you can make changes here... If you read the articale from Glitch on this it will help alot (found in the OP for T959D).
Live oc clocks up the cpu AND bus so it affects the gpu and memory along with the cpu (very important).
Findings... some settings work fine, 105, 106,110, 114, 116. 115 seems to have issues and provides lower performance considerably lower.
I use AnTuTu to check how things are working. That being said, if you apply set at boot and you hit a setting that first craps out the phone, causes a reboot then your going to be in a bootloop or it will start reboot start reboot. This is why you DON'T do this or like I said earlier have a good recovery handy.
Right now I am only running 1304 and 100% and everything is fine except the prior mentioned FC on video cam. Oh I should mention also I am running the Lazy governor atm which also seems to work fine (default is on demand).
Anyways
Well I think we may have broken the record for the longest 2 posts on the first page in xda history lol. Happy flash year everyone
Sent from my GT-I9000 using XDA App
Didn't notice you guys mention this, but Glitch V14 has an option in CWM to clear NSTools settings. It's right above the option to clear voltage settings under the Glitch Menu.
It works well, believe me!!
-Maniac
I'm on ICS!
Thanks bucky!!
I'm on ICS now, with Glitch v14 but I have a few questions I'm hoping you can help with:
- The screen layout / icons seem shrunken to me? As well as the notification bar. General text and keyboards are fine. Is there a fix I can apply?
- With further versions from Surface can I just flash over top of what I'm on now or do I need to go back to stock?
- Do I need to use TI to bring all my apps back up (I get "App X has stopped working"), or is there a quicker way?
Thanks again.
baino said:
Thanks bucky!!
I'm on ICS now, with Glitch v14 but I have a few questions I'm hoping you can help with:
- The screen layout / icons seem shrunken to me? As well as the notification bar. General text and keyboards are fine. Is there a fix I can apply?
- With further versions from Surface can I just flash over top of what I'm on now or do I need to go back to stock?
- Do I need to use TI to bring all my apps back up (I get "App X has stopped working"), or is there a quicker way?
Thanks again.
Click to expand...
Click to collapse
Well the shrunken icons are because of the DPI setting in the build.prop file. You can change it with a text editor (I use root explorer) to the default value of 240. It is listed as LCD Density.
To flash another version you should be fine to flash over what you have with a factory reset and wipe cache
Apps well I usually just re-download from the market. I have used TI and found I get the best result if I restore without data. Remember not all apps are compatible with ICS yet so that could cause issues as well.
Enjoy the ICS I know I do.
bucknetbucky said:
Well the shrunken icons are because of the DPI setting in the build.prop file. You can change it with a text editor (I use root explorer) to the default value of 240. It is listed as LCD Density.
To flash another version you should be fine to flash over what you have with a factory reset and wipe cache
Apps well I usually just re-download from the market. I have used TI and found I get the best result if I restore without data. Remember not all apps are compatible with ICS yet so that could cause issues as well.
Enjoy the ICS I know I do.
Click to expand...
Click to collapse
Hey Guys,
Why not just use rom toolbox? the build.prop tweaks give ya a niffty slider... no hackin involved...
Anyone got the files for stock GB?
cowvun said:
Anyone got the files for stock GB?
Click to expand...
Click to collapse
you looking for T959D?
Yes
Sent from my T959D on Darky's Rom 10.3.
Rom toolbox worked for me, it's looking beauty now. Everything seems to be working well, except I get the occasional crash on dialer / contacts. Anyone else having the same?
I'm running LauncherPro, what are you guys running?
baino said:
Rom toolbox worked for me, it's looking beauty now. Everything seems to be working well, except I get the occasional crash on dialer / contacts. Anyone else having the same?
I'm running LauncherPro, what are you guys running?
Click to expand...
Click to collapse
Nothing like that here maybe the way it was flashed I am not sure. Have you added anything?
Sent from my GT-I9000 using XDA App
Only flashed the add-ons, and the launcher pack. Changed the LCD density and that's about it. I'm thinking it might be because I didn't wipe the sd card and start clean.
baino said:
Only flashed the add-ons, and the launcher pack. Changed the LCD density and that's about it. I'm thinking it might be because I didn't wipe the sd card and start clean.
Click to expand...
Click to collapse
Depends what you did before flashing. I had issues after flashing a lot and never deleting anything lol
Sent from my GT-I9000 using XDA App
Working NSTools values for OC and UV
CPU:
Governor = Lazy
Min CPU = 100 (109 after live OC)
Max CPU = 1200 (1308 after live OC)
OC Value = 109%
Deep Idle = On
Custom Voltage
Arm:
1400 = unchanged
1304 = 1375
1200 = 1325
1000 = 1225
800 = 1150
400 = 975
200 = 875
100 = 875
Int Voltage
1400 = Unchanged
1304 = 1150
1200 = 1125
1000 = 1075
800 = 1050
400 = 1025
200 = 1025
100 = 925
Just set these values tonight and so far all is good and no crashes or reboots. See if it helps the battery as the days go by. Give it a shot or post your working values for others to try.
AND NO I NEVER SLEEP
bucknetbucky said:
Working NSTools values for OC and UV
Click to expand...
Click to collapse
Thanks for posting your OC and UV values. I'll give those a try.
I've been experiencing random crashes and reboots (woke up this morning to a dead phone). It was plugged in overnight but crashed at some point and did not charge. Battery voltage dropped down to almost nothing.
Anyone else experiencing random reboots?
I was using an OC value of 1304 (no live OC). UV values left stock. Ondemand governor, Deep idle ON, noop IO scheduler.
I did not format my sdcard prior to install. Just did a data wipe/factory reset, format cache and dalvik then installed according to the instructions. Installed Add-on Essentials and Add-on Pack One. All other apps were reinstalled from the market (after using market enabler and changing DPI back to 240 using ROM manager).
Everything works great except for the random crashes and reboots. I'll probably start from scratch again when v1.3 comes out (except I will format the SD card). Maybe even start from stock Froyo as recommended in the OP.
EDIT:
Tried the settings and my phone was not happy. It froze when setting the UV values. My phone seems to have a problem with any live OC value other than 100%. As soon as I increase it I lose all stability.
1.3 released and I am running it.
Sent from my GT-I9000 using XDA App
Settings
I'm on Glitch v14 pre5 and I just clocked it up to 1300 and added 104% live OC for a stable 1352, no undervolting battery sitting @ 68% 1 day 22hrs. I did turn off some stuff I dont use and had data running on and off for the whole time.
For the guys that are having problems with flashes, I generally wipe everything I know its a pain but I don't experience any problems either. I also wait until i have a full battery too. It seems to pay off in the long run...
Happy Flashing!!!
Phone and contacts are working well now, but I can't get app data to save. For example some apps t's&c's keep asking for approval everytime I open the app. Also beautiful widgets skins keep reverting back to default. I'm going to wipe, format the SD card and install 1.3 from stock Froyo. here's hoping.
bucknetbucky said:
1.3 released and I am running it.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Just wiped and running 1.3 now. So far seems much better and faster than my last flash. You guys know of any way to change the haptic feedback intensity in ics?