Related
Hi, I am a relative newbie to ROM flashing and the like. Additionally I dont have a very deep computer knowledge base. I have rooted my Samsung Captivate and have flashed a ROM (which flashed properly, but didn't quite work). I have three questions about ROM usage and such:
1. I know kernels basically add aspects to the ROM you are running, but when should you flash these? How do you flash them (same process as with ROMs? do you just do it over-top of the Rom you currently have loaded? etc...)
2. If a newer version of the ROM you have running comes out, do you have to start over and completely wipe the device over again and do the whole process from start, or can you load a newer version of your current ROM over the one you have?
3. I have been hearing/reading about some problems with the Android Market disappearing on certain ROMs when the market updates, how can i avoid this/fix this?
Thanks. Sorry the basic/stupid questions.
1. Yes
2. There are WIPE versions and NO WIPE version. Usually you can use the NO WIPE version and keep everything. But sometimes if the roms are too different you get problems and errors, then it is recommended to flash a WIPE version.
3. Hm did not experience this yet, but there are fixes somewhere .
Whats up... No question is a stupid one buddy.... (Sometimes )
To answer your first question about kernels. Flashing kernels aren't a must. You don't have to flash them really, unless there is a need. Kernels for the most part can often change the way Android handles stuff like memory management, battery resources and even multitasking. They change (tweak) the way the Android OS itself interacts with the phones hardware. That's all a kernel is really. So read up on them before flashing them because each has their advantages and disadvantages. For example, the kernel I use gives me a good RAM boost and much better battery life but it suffers on the multitasking side and I have to do other stuff to compensate for that. That's how it is. As far as flashing them is concerned. That depends. Usually, you just flash them through recovery (Like a ROM) but I would suggest you follow the instructions they give you (if it exists).
Your second question is simple. Just follow the instructions they give you for installation. Some ROMS require a full wipe and others don't. It just depends on the ROM. When in doubt, follow the instructions (again if it exists).
Your third question is a weird one, I've never heard about that really. BUT.... Some ROMS may or may not include the GAPPS applications (Google Apps).
If the ROM you flash doesn't have Google Apps built in, it would literally be missing. You would have to flash it separately. Usually in those cases though, at the download location for that ROM, they would also provide links for GAPPS zip files to flash separately so you can have the option to go with Android Market, Gmail and such OR you can use an alternative. Short of that..... never heard of that issue before..... If the issue is happening after the Market app updates, in that case it might be some type of ROM issue, you'll probably have to somehow get the updated Vending.apk (Android Market) remove/backup the original and reinstall it manually (the way you would a regular apk). I'm guessing though....
Don't you just love research........
Thanks. And now, inevitably, answers lead to more questions.
With regards to kernels, how do I know which one's do what, are compatible with which ROMs etc. I feel like its the kinda thing that needs a giant database for them, but i know there isn't.
Also, is the process for flashing other .zip files the same (though either Rom manager or a built in Recovery option). For example, a bootanimation.zip?
Ultimately I hate the idea of asking overly simply questions, but I just don't know what I dont know, nor what is supposedly implied. Thanks.
Don't sweat it...... I'm in the same boat so I have no hangups....
I think I know what you mean when it comes to kernels. Ultimately, learning about kernels requires a lot of reading in many forums (Just like this one)... Why?.... Because in many instances the persons posting the kernels might not always give you an exact breakdown on exactly what it does..... so I understand. Your best bet would be scanning XDA. I've found all sorts of really excellent kernels lying around and the devs here love documentation so there is a good chance you'll know what it does...
You could also try DroidBasement: http://droidbasement.com/db-blog/
They actually have just what you wanted, a database....kind of. They have a very large variety of kernels for different devices so its a good place to start as well.
They also tend to do a breakdown of what each kernel is capable of, the device it should be used on and so on.
About flashing zip files. Generally speaking, most zip files are flashed through recovery but its not written in stone. Following the instructions concerning said zip files are always very important. Always look for instructions before you do so at least at first. In the case of bootanimation.zip.... They are not always flashable. But if it is flashable, you can flash it through recovery which would be the best method....
If you want though, you can replace the original bootanimation.zip file with the new one manually, once you have root and some type of root explorer (for example RootExplorer for Android).
Generally, the boot animation directory is usually, /System/Media so you can check to see if its there and if it is, just backup the original and replace it with the new one.... That should work... Always nandroid before doing so though.... before doing anything really....
Thanks. I actually had a question about nandroid but forgot. Basically, what is it. I realize contextually that it's a backup program and apparently works through the recovery menus. I read a ROM flashing step-by-step that mentioned it but couldnt figure out where to get it (not in the market unlike Ti-bu which i use currently).
Nandroid is a backup program that basically creates a flash image of your phone... If you've ever heard of "Ghosting" or "Imaging" a Hard Drive, its exactly the same thing.
Its really as good as it gets as far as data backup is concerned. Its also a low level backup, so even file structures would be recorded.. In other words, you can completely screw up your phone (file partitions everything!!!!) but once you can boot to recovery, your phone can be restored. That's why its so important because its your safety net....
Its not something that you can install like an apk, so its not in the market.
You would have to flash a custom recovery. If you have one already, it should be located in one of the menus (It changes depending on the type (brand) of recovery).
If you don't see the option in your recovery then its probably not custom and you're going to have to do some digging on these forums and maybe a bit of googling for instructions on exactly how to do so. Because it could change from device to device.
Nandroid also allows you to backup your sd-ext partition as well, so if you switch cards, you can restore to another card.... Its really incredibly handy and I wouldn't suggest you do anything until you can create nandroid backups....
Now, I'm having an interesting problem I posted this same thing in general Captivate forums but maybe someone who is looking at this/answering me knows. here's what i posted there:
have a Captivate that I recently flashed Di11i's 7.1.1 to, before that I had flashed my first ROM which was Serendipity 6.2. Both times I have found that I don't get incoming calls. People calling me get 2-3 rings, and then a traditional "busy signal" sound. On my end, either the phone vibrates once but the screen doesnt change from whatever screen I'm on. Or, The screen goes black like its going to the incoming call screen, but the black screens only flashes and goes away, as does a force close message box that goes away quickly without me clicking it.
Everything else on my phone works as far as I can tell, I've been running my current ROM for about 5 days without issues other than this one. This same exact problem also happened when I flashed Serendipity 6.2 (which I only kept for like a day because of this problem)
Ok....I currently use a G1 and most of my experience has been on HTC Devices. I'm not sure of how to reply to this as I have never really modded Samsung devices before. So I'm not really familiar with software and hardware differences (Like Bootloader, Recoveries, Radios and such). But based on what you're describing.... It sounds like a ROM or maybe a radio issue. Maybe its an issue with the phone app itself. If the app is somehow buggy then thats exactly what would happen. When the phone rings the phone app would try to run but then force close....
I'm guessing here, but it could also be a radio issue because you're getting a busy tone as well which is not good. Maybe the ROM requires a specific Radio version BEFORE its flashed.... Check the source of the download and determine if it requires a specific Radio version.
In my experience though, if the correct radio version isn't used for a ROM that requires it, the phone just won't boot..... but then again, I don't know what would happen on a Samsung Captivate.... Not sure if I can help on this one because I don't have any info on that type of hardware. I don't own one you see.....
What about if you found out a new kernel isn't as good as the old kernel, how would you go on to take away the new kernel to replace it with the old kernel? Is it the same process or even harder?
vlen22 said:
What about if you found out a new kernel isn't as good as the old kernel, how would you go on to take away the new kernel to replace it with the old kernel? Is it the same process or even harder?
Click to expand...
Click to collapse
NOW THIS IS ANNOYING..
u have to flash ur rom again..
but fortunately u dont need to do and wiping data or partitioning sd card.. jus flash rom..
Its not something that you can install like an apk, so its not in the market.
zeemar007 said:
NOW THIS IS ANNOYING..
u have to flash ur rom again..
but fortunately u dont need to do and wiping data or partitioning sd card.. jus flash rom..
Click to expand...
Click to collapse
The rom kernel that I downloaded, or flashing clockwork recovery mod? Like adrenylyne's kernel for the thunderbolt.
EDIT: Never mind, I found out. I didn't mean any harm if MY POST was annoying.
If you have two kernels, in a flashable zip, you can just flash them over each other to exchange them (turn off any modification the kernel did befor though, like lagfix).
New question, I had an app (quick office) that came on my captivate. Now that I've flashed di11i's 7.1 I don't have it anymore. This is particularly peculiar because all the other native apps are still here:samsungs media player from example. How do I go about getting this missing app back on my phone. I have all the backup files on my computer so I should have the .apk (although I'm not entirely sure how to install those properly) thanks
Sent from my SAMSUNG-SGH-I897 using XDA App
So we are all flashing and re flashing new excellent ROMS that are being developed by the great devoted guys in here. I looked around and beside this I didn't find any TODO list before flashing.
So here is my little contribution,of the tasks I do before every flash to verify that I don't loose any data,but only upgrade my beloved device:
CONTACTS:
Since I'm not using my google account to sync my contacts(I'm a little bit envy of my privacy regarding the people I'm in contact with) - backup contacts using the import function in the contacts section
SMS/MMS:
Backup my sms/mms using any of the much too many apps in the market
APPS(Here is a section that I know will cause a lot of discussion):
I don't use titanium - I tried to use it during my first months with this phone I just didn't like it.I know it could be great to just save everything using it but I found it..hmmm...not suiting my needs and wants so I don't use it.
Instead recently I found a great feature in File expert which lets you backup your APKs(without the data,i.e. scores in games) - I find it very convenient because when I flash I want a clean start where I know exactly what I put back into the phone.
LAUNCHER:
I'm putting not a little effort to make my phone look as awsome as possible(and I'm sure you are too) so in order to save the trouble of configuring your preferred launcher after every flash - just back its settings. most of the used launchers have this option in their settings.
BATTERY:
Be sure you have enough battery life - best practice(which I admit that I'm not always follow)is to fully charge your phone before flashing.
FILES:
I personally always put my current rom zip and the one I'm about to flash on the sdcard to be on the safe side(boot loop for example that can be caused from bad download of the zip)-that way you always have a backup plan.
Also I'm trying to always backup all the content of my sdcard to my computer while I can, who knows what will happen during the flash - maybe you'll have to format your sdcard without any access to the data on it
UTILS:
even if you are just flashing using the CWM be sure to have a setup environment for ODIN:drivers,odin,tars etc.
And last but most important - NANDROID BACKUP:
Always and I repeat Always make a nandroid backup(if you are on the GB kernels I think there is a problem with backup/restore so I heard a solution is to flash the Bali kernel and make a restore with it - search the forum for more details.
That's it - I hope I didn't forget anything.
Please if you have any suggestions/comments don't hesitate to bring them up and I'll update this post if needed.
Enjoy
Thumbs up, bro.
I'm a big fan of Titanium backup though..
I will definately look at file expert to be using up to date supplemental apks when building a ROM.
Sent from me
For apks I just copy the install file from data/app or system/app to my sd card/app. This probably takes a little longer than batch functions. The only problem i encounter with this method is the need to push some apks back to system/app when they won't install properly. I like to reset my launcher after a flash but all of this is just personal preference
Post logs not complaints
Good stuff. Stuff that should be in the wiki Note the issue with CWM & GB is fixed in the later releases (version 5, I think) fixes that problem. I know it's available in bhndven's KJ6 kernels but I'm not sure about elsewhere.
Smells sticky...
Sent from my SGH-T959V using Tapatalk
stephen_w said:
Good stuff. Stuff that should be in the wiki Note the issue with CWM & GB is fixed in the later releases (version 5, I think) fixes that problem. I know it's available in bhndven's KJ6 kernels but I'm not sure about elsewhere.
Click to expand...
Click to collapse
Yes I heard about this but I haven't tried it yet and also I think most (if not all) the ROMs here still use the old CWM so...
alon2 said:
Yes I heard about this but I haven't tried it yet and also I think most (if not all) the ROMs here still use the old CWM so...
Click to expand...
Click to collapse
The ROMs themselves can be flashed from either. It's the Nandroid backups/restores that have an issue
stephen_w said:
The ROMs themselves can be flashed from either. It's the Nandroid backups/restores that have an issue
Click to expand...
Click to collapse
exactly what I meant
OK...Let's get something out of the way before anyone start getting irate with me and saying things they shouldn't be about this thread does not belong here...
THIS IS NOT A ROM...does it have to do with Development? I believe so....
We have always been instructed by every ROM Devs that we have to WIPE Everything in order to get our ROMs stable and running as it should...well this post goes counter to what you've been told by almost any post on XDA-Dev
I am addicted to flashing ROMs to see which best suits my needs, however the pain of having to install my apps (I have more than 150...don't ask) usually kept me from trying as many as I would like to....started thinking about how DT APP2SD work...since it is a partition that is completely separated from where the ROM is flashed...WHY DO WE HAVE TO WIPE IT??? So, I started flashing different ROMs, from ICS, Gingerbread to even Froyo to test my theory. Low and behold...more than 95% of my apps held intact (albeit no DATA - you can use Titanium or MyBackup Root to restore the Apps Data) with no hiccups when running from one ROM to another. I have flashed from AOSP to SENSE to MIUI...same result, my apps remain intact as long as I wipe EVERYTHING EXCEPT the SD-EXT...DALVIK CACHE HAS TO WIPE...even though part of it is on the Extension!!!
The reason why is simple. Any DEVs that baked DT APP2SD into their ROMs essentially call for this partition at boot...and once the ROM call for this partition...all the apps that are located in there still remain and the ROM uses it as if it was part of the ROM.
Also, I have even tested it so extensively that I flashed a Sense, an AOSP and ICS independently - after making sure my ROM was stable, reboot to RECOVERY and plug my phone to my PC running Linux....automatically the SD EXT pops up and I dropped all my apps (again, more than 150) to it...and KABOOM!!! Upon reboot...all my apps started showing up.
Again, I have no intent to take space from the DEVs who are doing a GREAT job supporting our phones....
I am posting this in the hope of helping those who flash often and also the Devs themselves from having to reinstall all their apps everytime they flash a new ROM.
If the MODs feels like this does not belong here...please feel free to move it. I think that it could play an integral role in development to all the Devs out there, hence why I am posting it here.
PS: I am not here every day, I have two little ones and a beautiful wife that I try spend as much time with...so please be patient with me if you PM me for more details on how to do this.
If this helps you in any way, please hit the thanks button...
Again, thanks to all the great works the Devs are doing!!!!
I have done this before and it does work. The only thing that keeps me from doing this is the lack of the ability to do a batch data only restore with titanium. Am I missing something? How do u quickly restore the data to your apps?
do a batch, and at the top, select data only.
lawsonmh15 said:
do a batch, and at the top, select data only.
Click to expand...
Click to collapse
Ooooohhhh......how did I not put 2 and 2 together. Thanks.
Would it not depend on the ROM your flashing?
i've been doing this for awhile, jus thought it was common knowledge. there have been some apps that FC, but i'm a FLASH chronic, and reinstall apps wud suck. ROOT UNINSTALLER is also a great app to do BU's.
I've done the same thing a couple times in the past (between CM and Sense) but always had nagging doubts that I was screwing something up somehow... Good to know that someone has taken the time to confirm that this is actually a reasonably safe process! I just had to do a nightmare manual one-by-one app restore on a ROM I flashed but I'm glad that now I can comfortably use this trick in the future.
Thanks man.
The reason for a full wipe is that most people don't have their sd card partitioned.I myself have partitioned mine and do exactly what you suggested and it does work,i figured this out after wiping the sd-exta few times,1 time i decided not to,i noticed my apps were still there after i installed another rom.Of course if you have a google account,google keeps your apps and contacts backed up.
Would this also apply for those that have partitioned sd and have a Sense 3.0~3.5 ROM installed? Question is because some devs, if not all, set the rom to save part of the rom on sd-ext partition.
I have been doing this all the time for sense and asop roms, works great. Off topic - wiping more than once is BS unless you have bad nand or using bad wiping program.
Happy to see that some of you find this information useful. I just didn't want to get screamed at for posting it here.
It's a little I can help with in contrast to the great work the devs are doing
Sent from my PC36100 using XDA App
dragon_rckr said:
Would this also apply for those that have partitioned sd and have a Sense 3.0~3.5 ROM installed? Question is because some devs, if not all, set the rom to save part of the rom on sd-ext partition.
Click to expand...
Click to collapse
It should have no impact because essentially your app folder is where everything is kept. If the Dev add some system info to the Ext it won't mess with your apps.
Sent from my PC36100 using XDA App
I am looking to try different rims for my HOX. I was wanting to know if I could download the roms I want to try and install each one then make a nandroid back up. So when I wanna switch I don't have to install each rom then I could just use the backup.
I'm currently running CleanRom 4.5. I am no expert at this. I have only rooted one other phone besides this, it was the Inspire.
Some roms I was planning on looking at were:
Viper
CM10
Nocturnal
CleanRom 5.0
Sorry if the grammar is bad. Sending this from my phone.
Yes, you can do that. Keep in mind you should wipe data before flashing different ROMs. So you need to re-setup each time. But you can still do what you stated in the OP.
NeverToLate said:
I am looking to try different rims for my HOX. I was wanting to know if I could download the roms I want to try and install each one then make a nandroid back up. So when I wanna switch I don't have to install each rom then I could just use the backup.
I'm currently running CleanRom 4.5. I am no expert at this. I have only rooted one other phone besides this, it was the Inspire.
Some roms I was planning on looking at were:
Viper
CM10
Nocturnal
CleanRom 5.0
Sorry if the grammar is bad. Sending this from my phone.
Click to expand...
Click to collapse
By all means go for it! I have a few tips for you, as one flasher to another
As redpoint said, each time you flash a new ROM you are starting from scratch. This only refers to your personal data and ROM settings, though. There are a few ways to guarantee that you won't be spending a long time configuring each ROM:
Cloud Storage is your friend! I personally use Dropbox to save anything important to my daily use since I can easily pull up documents stored there from anything connected to the internet. There are much more secure options to store files on the cloud, but you have to pay for the more secure options, and security is not of top importance to me (since I just store homework assignments and basic documents).
Use Google Backup! When you flash new android ROMs, there is a prompt that asks you if you would like to backup your phone to Google's servers. I usually hit yes to this prompt. After you have done this once, when you flash a new ROM and enter your Google account, any Play store apps you had installed will be redownloaded (including any personal data associated with the app, IF it's developer has enabled this feature). It's not a perfect way of restoring your apps, but it sure beats re-entering all of your data each time you want to try a new ROM.
Use services to store your contacts! I took a few days to enter ALL of my contacts into my Gmail account, and it was one of the best decisions I have ever made. Each time I restore my phone, I have all of my contacts available. People who complain about losing all of their contacts along with their phone need to learn about this point.
Remember that your SD card partition stays intact between ROMs! Just because you install a new OS doesn't mean you lose everything. Any music, movies, documents, or even app data that is stored on your SD card is unaffected by flashing something new. This is because your SD card is a completely separate partition of your phone's memory. The One XL may not have a real SD card slot, but you can still treat this partition as separate from the rest of your phone. Personal Tip: I store my backups and ROM zip files in a "Recovery" folder on my SD card partition. Having all of those files in one place simplifies flashing in TWRP.
Avoid using tools like Titanium Backup to restore apps! For a while I decided to use Titanium to restore apps. After a while I realized that all of the errors I was experiencing was the result of mismatched phone IDs, cache errors, and a bunch of other small glitches caused by Titanium backup. It is not the fault of TB and it is still a useful tool, but using Google backup to restore your apps is much cleaner and will result in fewer errors.
Save your text messages! Titanium Backup has the option of saving your text messages as a .xml file, but this is more complex than just using play store applications like SMS Backup & Restore. If you don't back up your SMS, you will look totally unpopular when you keep flashing your phone (and have no text messages at all)!
I hope this list helps you out in your flashing journey. Don't be afraid to try new things, and remember that if you can get into recovery mode, you will be fine (ESPECIALLY if you back up your data in the ways I described).
Thanks for tips
As far as saving everything as you posted. I don't have really that many documents I need and I am a big fan of dropbox haha. As far as my contacts any contacts I put in my phone automatically go to my google account so they always transfer over for me.
I usually delete most text messages at night and that's when I will flash these ROMS as I will not be texting anyone later in the night so, no worries there.
I really only have a few apps that I use, so even if they don't reinstall it doesn't take long to find em.
My main focus of now is just downloaded the roms I want and putting them all on my sd card. Whenever I have time to flash em all I will set them up kind of the way I want em with my apps, then set up the next ROM.
When that process is complete I'll just test each one for a few days/weeks till I find the perfect one for me haha.
I was planning on doing full wipe/reset between each one so I am glad yall confirmed that for me haha. Anything else I should keep an eye out for?
redpoint73 said:
Yes, you can do that. Keep in mind you should wipe data before flashing different ROMs. So you need to re-setup each time. But you can still do what you stated in the OP.
Click to expand...
Click to collapse
I don't have to do reset between nandroid backups do I?
NeverToLate said:
I was planning on doing full wipe/reset between each one so I am glad yall confirmed that for me haha. Anything else I should keep an eye out for?
Click to expand...
Click to collapse
Just two things - Most ROMs (especially AOSP) are constantly updating to newer versions, and if you are trying to make ONE snapshot of a ROM and flash back to it whenever you want, be sure that it is a stable version. CM10 and AOKP builds all have bugs, features tend to break each nightly/weekly build, and then get fixed later. Be sure you grab one of the stable builds or at least one that has all of the features you need (NOT necessarily the latest one), otherwise you will be relying on a (potentially) unstable ROM as your backup.
The other thing is, if you were potentially going to flash radio or kernel files, be sure to choose the correct one and flash it each time you install a new ROM or update. Each time you flash a ROM zip, the data for the kernel and radio are overwritten. Especially with radio files, you can break your phone or just cause general errors if you flash the wrong thing (example: flashing a radio+RIL zip on an AOSP ROM can cause serious errors, but the same file is actually preferred on Sense based ROMs). You don't have to worry about these files at all, but if you do end up flashing them, be careful!
NeverToLate said:
I don't have to do reset between nandroid backups do I?
Click to expand...
Click to collapse
Going between nandroids? No, recovery is going to overwrite the user data with the user data from the nandroid, so I don't think you need to worry about it.
---------- Post added at 04:25 PM ---------- Previous post was at 04:21 PM ----------
gridlock489 said:
Remember that your SD card partition stays intact between ROMs![/B] Just because you install a new OS doesn't mean you lose everything. Any music, movies, documents, or even app data that is stored on your SD card is unaffected by flashing something new. This is because your SD card is a completely separate partition of your phone's memory. The One XL may not have a real SD card slot, but you can still treat this partition as separate from the rest of your phone. Personal Tip: I store my backups and ROM zip files in a "Recovery" folder on my SD card partition. Having all of those files in one place simplifies flashing in TWRP.
Click to expand...
Click to collapse
In theory, that is supposed to be true. But many people (including myself) have had instances of some or all of the SD contents erased or corrupted. The exact cause has still not been found, but possibly just a bug of the phone. I've had it happen several times now. If you have anything irreplaceable on the SD, I would suggest backing it up to your computer, Dropbox, or whatever, before flashing anything. This includes photos of videos that you took, and anything else not easily replaced. Backing up one known good nandroid is not a bad idea, either, just in case.
gridlock489 said:
Just two things - Most ROMs (especially AOSP) are constantly updating to newer versions, and if you are trying to make ONE snapshot of a ROM and flash back to it whenever you want, be sure that it is a stable version. CM10 and AOKP builds all have bugs, features tend to break each nightly/weekly build, and then get fixed later. Be sure you grab one of the stable builds or at least one that has all of the features you need (NOT necessarily the latest one), otherwise you will be relying on a (potentially) unstable ROM as your backup.
The other thing is, if you were potentially going to flash radio or kernel files, be sure to choose the correct one and flash it each time you install a new ROM or update. Each time you flash a ROM zip, the data for the kernel and radio are overwritten. Especially with radio files, you can break your phone or just cause general errors if you flash the wrong thing (example: flashing a radio+RIL zip on an AOSP ROM can cause serious errors, but the same file is actually preferred on Sense based ROMs). You don't have to worry about these files at all, but if you do end up flashing them, be careful!
Click to expand...
Click to collapse
I don't plan on flashing any radios. As I did with the inspire, and it messed up my service bad and I didn't know how to fix it again. I didn't now too much about it then. Which I still don't but I know more now than I did then.
NeverToLate said:
Anything else I should keep an eye out for?
Click to expand...
Click to collapse
Be sure you are using TWRP, and not Clockworkmod. CWM has known problems, as our device is not really supported (its just a port) and also USB mount is not working (which may be relevant if you run into problems such as the SD corruption I've mentioned).
I will be using TWRP. If I'm not mistaken I did a nandroid back up of stock rooted. I plan on copying my sd card to my computer external hd just for safety. I have a HTC One X Folder that I will put my roms in stuff in as well.
I will try to take screenshots of battery life for each day I use a certain rom. The battery probably won't go below 30% but screenshots would give a good idea to other people. And I will try to update my thoughts on each rom. Not promising I will get to but I will try.
I am going to download and check md5s today.
Idk if I will flash one tonight or not.
Also I may try to have a nandroid back up of the same rom if it has Sense and a non-Sense version. I have never tried a non Sense rom so I am really trying to figure out what I like best.
NeverToLate said:
Also I may try to have a nandroid back up of the same rom if it has Sense and a non-Sense version. I have never tried a non Sense rom so I am really trying to figure out what I like best.
Click to expand...
Click to collapse
I hope you like blue If not, take a look at this thread for some CM10 themes.
Any ROM based on Sense will still have remnants of HTC's UI somewhere. When there are deSensed versions (such as CleanROM V), usually the dev is trying to get closer to the stock Android look. I personally either go all the way and flash an AOSP ROM, or stay with stock Sense, because anywhere inbetween usually lacks polish and continuity. I'm exceptionally picky though
gridlock489 said:
I hope you like blue If not, take a look at this thread for some CM10 themes.
Any ROM based on Sense will still have remnants of HTC's UI somewhere. When there are deSensed versions (such as CleanROM V), usually the dev is trying to get closer to the stock Android look. I personally either go all the way and flash an AOSP ROM, or stay with stock Sense, because anywhere inbetween usually lacks polish and continuity. I'm exceptionally picky though
Click to expand...
Click to collapse
Blue is actually my favorite color lol. Could you point me to the CM10 rom?
Here are the roms I am downloading as of now:
KingCobra
Nocturnal Special Edition
Viper
Clean Rom 5.0
Any other ideas on maybe one or two more roms?
I bookmarked that link you posted. I prob won't do much with themes until I find the right ROM. Even then the most I usually do is wallpapers lol. But will look more into after finding a ROM.
What rom would you suggest on CM or AOKP? What build? I don't know much about those. Never really looked in the original development forum lol.
NeverToLate said:
What rom would you suggest on CM or AOKP? What build? I don't know much about those. Never really looked in the original development forum lol.
Click to expand...
Click to collapse
I just flashed the latest build (cm-10-20121001-EXPERIMENTAL-evita.zip) a few hours ago and it has been just fine with me, very smooth with no crashes so far. You can download the nightly builds here, but like I said earlier not all of them are stable. CM10 is developed for multiple devices with different hardware. Our One XL is code named "evita", so before you flash ANYTHING be sure that it has "evita" in the file name. Be sure to look at the development thread, or at least the OP, if you want to get more information.
As for AOKP, it seems like build 4 (the latest) may be having some issues. I don't use that ROM so check out the dev thread if you need help.
gridlock489 said:
I just flashed the latest build (cm-10-20121001-EXPERIMENTAL-evita.zip) a few hours ago and it has been just fine with me, very smooth with no crashes so far. You can download the nightly builds here, but like I said earlier not all of them are stable. CM10 is developed for multiple devices with different hardware. Our One XL is code named "evita", so before you flash ANYTHING be sure that it has "evita" in the file name. Be sure to look at the development thread, or at least the OP, if you want to get more information.
As for AOKP, it seems like build 4 (the latest) may be having some issues. I don't use that ROM so check out the dev thread if you need help.
Click to expand...
Click to collapse
What's the different in the Nightly and Experimental? I would like to try a CM since I never have before. Probably will be the last one I download
Also on the CM10 forum it says something about find Gapps? Is that something I search for and download and flash?
Update
Downloaded Roms with md5 checked and now on my sim card:
Clean Rom 5.0
CM10
King Cobra
Nocturnal Special Edition
Viper
Just need help on what I need to download for Gapps to install CM10
What Rom should I test first?
King Cobra
Viper
Nocturnal
I'm on nocturnal and loving it.
Sent from my HTC One X using xda premium
I used the ROM from here. (LG Optimus T (P509): January 8: Build 7/Final)
I have no Google Play store icon anywhere. I see the Google Play process running in the background.
but have no way to get it to show up. This on a fresh ROM, all User data, Cache, and all that cleared.
Any help on this would be nice.
Would of asked on that post where I got the ROM. but I don't have the patience to or any thoughts about other post to make to meet the requirements to even post there.
Tried without flashing the Google Apps and with the google apps they list there.
Flashing Google Apps just crashes things like the browser. it wont even open.
Not flashing Google Apps I can use the browser just fine. but I still see "Google Play Services" Running. So that tells me google play is installed.
So don't have to flash it. but cant open it even if i did or not. no Icon anywhere no matter what I try. I been wanting to use CM10. but this issue keeps me going back to CM7.
Thanks in advance to the person with the answer.
TroyFoxxin said:
I used the ROM from here. (LG Optimus T (P509): January 8: Build 7/Final)
I have no Google Play store icon anywhere. I see the Google Play process running in the background.
but have no way to get it to show up. This on a fresh ROM, all User data, Cache, and all that cleared.
Any help on this would be nice.
Would of asked on that post where I got the ROM. but I don't have the patience to or any thoughts about other post to make to meet the requirements to even post there.
Tried without flashing the Google Apps and with the google apps they list there.
Flashing Google Apps just crashes things like the browser. it wont even open.
Not flashing Google Apps I can use the browser just fine. but I still see "Google Play Services" Running. So that tells me google play is installed.
So don't have to flash it. but cant open it even if i did or not. no Icon anywhere no matter what I try. I been wanting to use CM10. but this issue keeps me going back to CM7.
Thanks in advance to the person with the answer.
Click to expand...
Click to collapse
Are you sure you are using the right GApps package? That's Rasheds ROM you're referring to using. Build 7 is Android 4.1.2. Check this link here. And some of the problems you may be experiencing could be due to a faulty installation because of limited system space. You may want to review the LG Optimus One FAQ too.
shinobisoft said:
Are you sure you are using the right GApps package? That's Rasheds ROM you're referring to using. Build 7 is Android 4.1.2. Check this link here. And some of the problems you may be experiencing could be due to a faulty installation because of limited system space. You may want to review the LG Optimus One FAQ too.
Click to expand...
Click to collapse
There is more then enough internal space. (150MB Free after Gapps Flashed).
I tried again with the Gapps for 4.1.2. At the time my post I re flashed the ROM but left it out. I didn't flash it.
When I tried again. I got the Updating Android. but still no Play Store Icon. However it did not break my home or other buttons.
and browser still working. but again. no Play Store icon.
I checked the FAQ. Currently i see nothing there to give hints. I got more then enough free space. I've flashed ROMs on this phone dozens of times so I know the whole wiping of cache and data and all that between each ROM.
TroyFoxxin said:
There is more then enough internal space. (150MB Free after Gapps Flashed).
I tried again with the Gapps for 4.1.2. At the time my post I re flashed the ROM but left it out. I didn't flash it.
When I tried again. I got the Updating Android. but still no Play Store Icon. However it did not break my home or other buttons.
and browser still working. but again. no Play Store icon.
I checked the FAQ. Currently i see nothing there to give hints. I got more then enough free space. I've flashed ROMs on this phone dozens of times so I know the whole wiping of cache and data and all that between each ROM.
Click to expand...
Click to collapse
You have to trim the Rom, there's not enough SYSTEM space for the Rom and Gapps..this has been discussed time and time again on rashed thread(cm10)..There's a tool ( Oone Rom editor that will help you do this) This is why you have the bugs that your facing.
3ncrypt3d_Droid said:
You have to trim the Rom, there's not enough SYSTEM space for the Rom and Gapps..this has been discussed time and time again on rashed thread(cm10)..There's a tool ( Oone Rom editor that will help you do this) This is why you have the bugs that your facing.
Click to expand...
Click to collapse
I used that program already. looking at all that it would only show.
the math dont even come to half of what the phone memory is.
TroyFoxxin said:
I used that program already. looking at all that it would only show.
the math dont even come to half of what the phone memory is.
Click to expand...
Click to collapse
The system partition has nothing to do with the devices memory. These devices have a 190 MB system partition, this is where Android gets installed. What you are referring to is the user data partition which is 200 MB, while the device has 415 MB+- RAM ( memory ). Unless you are using Android 4.2.2, the only way to see how much space is on the system partition is with a third party app, with ADB, or with a Terminal Emulator app on the device. The math isn't adding up because you don't understand it, that's why I pointed you to the FAQ thread.
I wrote OOne ROM Editor. I haven't put hundreds, yes hundreds, of hours in to it's development just for general pleasure. It was written for a specific purpose, to trim ICS and newer ROMs for devices with small or limited system partitions.
shinobisoft said:
The system partition has nothing to do with the devices memory. These devices have a 190 MB system partition, this is where Android gets installed. What you are referring to is the user data partition which is 200 MB, while the device has 415 MB+- RAM ( memory ). Unless you are using Android 4.2.2, the only way to see how much space is on the system partition is with a third party app, with ADB, or with a Terminal Emulator app on the device. The math isn't adding up because you don't understand it, that's why I pointed you to the FAQ thread.
I wrote OOne ROM Editor. I haven't put hundreds, yes hundreds, of hours in to it's development just for general pleasure. It was written for a specific purpose, to trim ICS and newer ROMs for devices with small or limited system partitions.
Click to expand...
Click to collapse
I dont know what to try to trim with that program. i dont know what half them apps do.
Like Exchange2.apk. I don't know what that is. Which are some of the key things i can trim?
Also, Telling me how many hours you put into a program and that i dont understand something not going to be on my good side. So i missed something, big deal. I just got off a anxiety attack. and i was needing was a simple answer. doing a search for "LG P509 No Playstore Icon" was getting me no where and i didnt want to have to search page by page of the 487 pages of the ROMs post to find clues.
TroyFoxxin said:
I dont know what to try to trim with that program. i dont know what half them apps do.
Like Exchange2.apk. I don't know what that is. Which are some of the key things i can trim?
Click to expand...
Click to collapse
The help docs in OOne ROM Editor's thread list some of the known files that can be removed from and or moved around, ie; converted to user app, in the ROM.
shinobisoft said:
The help docs in OOne ROM Editor's thread list some of the known files that can be removed from and or moved around, ie; converted to user app, in the ROM.
Click to expand...
Click to collapse
just never mind. i dont need the stress right now, ill just stay with CM7.
Every time i try to Build the ROM and put it on the phone CWM just says its bad.
TroyFoxxin said:
just never mind. i dont need the stress right now, ill just stay with CM7.
Every time i try to Build the ROM and put it on the phone CWM just says its bad.
Click to expand...
Click to collapse
Are you getting an "assert() failed" message? If you are using CWM 5.0.2.7 Touch, it will only allow you to install P500 ROMs. OOne ROM Editor has the ability to remove the "assert()" statement from the ROM's updater-script to prevent that particular error from happening. Before building the ROM, go to the Tools->Build submenu and select the Build Options command. Check the checkbox for "Remove updater-script 'assert()' statement". Then build the ROM.
And stress... You call editing a ROM stress? Try writing the code for OOne ROM Editor Or better yet, play with live electricity :silly: - oh wait I do that already since I am an electrician... DOn't get frustrated by it. Sit back relax and soak in some of the knowledge around here.
shinobisoft said:
Are you getting an "assert() failed" message? If you are using CWM 5.0.2.7 Touch, it will only allow you to install P500 ROMs. OOne ROM Editor has the ability to remove the "assert()" statement from the ROM's updater-script to prevent that particular error from happening. Before building the ROM, go to the Tools->Build submenu and select the Build Options command. Check the checkbox for "Remove updater-script 'assert()' statement". Then build the ROM.
And stress... You call editing a ROM stress? Try writing the code for OOne ROM Editor Or better yet, play with live electricity :silly: - oh wait I do that already since I am an electrician... DOn't get frustrated by it. Sit back relax and soak in some of the knowledge around here.
Click to expand...
Click to collapse
Again bad, day. had a Anxiety attack. haven't slept. I havent played with Android as often as other things. I am also a Electronic person. Soldering Caps and so on on motherboards all the time. So please dont talk like that to people you dont know. they may have plenty of knowledge. but maybe having whats called a short fuse kinda day.
Also I did do "Remove updater-script 'assert()' statement". And i get no error from OOne ROM Editor it was in CWM it would just say it was bad, or say nothing at it would just restart CWM. Ill try again when Im better. Right now my phone has CWM 5.0.2.0, So ill change that as well when i try again.
but right im turning in for the night.
TroyFoxxin said:
Again bad, day. had a Anxiety attack. haven't slept. I havent played with Android as often as other things. I am also a Electronic person. Soldering Caps and so on on motherboards all the time. So please dont talk like that to people you dont know. they may have plenty of knowledge. but maybe having whats called a short fuse kinda day.
Also I did do "Remove updater-script 'assert()' statement". And i get no error from OOne ROM Editor it was in CWM it would just say it was bad, or say nothing at it would just restart CWM. Ill try again when Im better. Right now my phone has CWM 5.0.2.0, So ill change that as well when i try again.
but right im turning in for the night.
Click to expand...
Click to collapse
Sorry you're having a bad day. Rest assured, if I was talking down to you, there wouldn't be any smilies. I was just expressing that you weren't the only one out there with stress in their life, and some of us have loads of it. On that note, I'm not one of the many teenagers around here. So I'm not talking down to you, but out of experience. My teenage years were gone 23 years ago. Apparently it was take outta context, Sorry.
I think the issue I mentioned for CWM 5.0.2.7 is a shared issue with CWM 5.0.2.0, but I can't say for sure as I don't recall ever using CWM 5.0.2.0. I wasn't suggesting changing to the CWM I mentioned, was asking if that was the one you were/are using, which you've now stated you aren't. There error I was referring to would have been from CWM after flashing or trying to flash a ROM.
shinobisoft said:
Sorry you're having a bad day. Rest assured, if I was talking down to you, there wouldn't be any smilies. I was just expressing that you weren't the only one out there with stress in their life, and some of us have loads of it. On that note, I'm not one of the many teenagers around here. So I'm not talking down to you, but out of experience. My teenage years were gone 23 years ago. Apparently it was take outta context, Sorry.
I think the issue I mentioned for CWM 5.0.2.7 is a shared issue with CWM 5.0.2.0, but I can't say for sure as I don't recall ever using CWM 5.0.2.0. I wasn't suggesting changing to the CWM I mentioned, was asking if that was the one you were/are using, which you've now stated you aren't. There error I was referring to would have been from CWM after flashing or trying to flash a ROM.
Click to expand...
Click to collapse
Can that program add apps? If so or not. maybe I can edit the zip directly. but is it possible to port the old music player in Gingerbread to JB. I don't like Apollo. or would it just be better to remove Apollo and find something I like in Play store when i make this work?
And should i try to use CWM 5.0.2.7 instead, and try again?
EDIT: Says I have the latest according to this.
EDIT 2: just ROM Manger being a butt. going to the site directly. I see CWM 5.0.2.7 as the latest.
TroyFoxxin said:
Can that program add apps? If so or not. maybe I can edit the zip directly. but is it possible to port the old music player in Gingerbread to JB. I don't like Apollo. or would it just be better to remove Apollo and find something I like in Play store when i make this work?
And should i try to use CWM 5.0.2.7 instead, and try again?
EDIT: Says I have the latest according to this.
EDIT 2: just ROM Manger being a butt. going to the site directly. I see CWM 5.0.2.7 as the latest.
Click to expand...
Click to collapse
Yes apps can be added, but only as User Apps. Select "User Apps" in the treeview on the left. Then right click on the listview on the right and select the "Add apps" command item. A file dialog will appear. Multiple file selection is allowed.
You can remove Apollo. I prefer Google Play Music myself.
For your recovery. CWM 5.0.2.7 will only allow installing P500 ROMs. I do prefer the touch version of CWM, and since P509 is identical to P500, it's really not an issue other than baseband which is solved with a flashable patch. I really cannot recommend a recovery as we all have different likes/dislikes/usage patterns. I would recommend not using ROM Manager to install a recovery. It's been known to be faulty with our devices. Theres always ADB and fastboot or another one of my tools, Android Flash Recovery. There are several other apps around XDA that can do this also.
shinobisoft said:
Yes apps can be added, but only as User Apps. Select "User Apps" in the treeview on the left. Then right click on the listview on the right and select the "Add apps" command item. A file dialog will appear. Multiple file selection is allowed.
You can remove Apollo. I prefer Google Play Music myself.
For your recovery. CWM 5.0.2.7 will only allow installing P500 ROMs. I do prefer the touch version of CWM, and since P509 is identical to P500, it's really not an issue other than baseband which is solved with a flashable patch. I really cannot recommend a recovery as we all have different likes/dislikes/usage patterns. I would recommend not using ROM Manager to install a recovery. It's been known to be faulty with our devices. Theres always ADB and fastboot or another one of my tools, Android Flash Recovery. There are several other apps around XDA that can do this also.
Click to expand...
Click to collapse
Ill just leave it be then. Its always worked for me. if there was a problem it was with the ROM.
I haven't tried Google Play music before. but is it possible to port the music player from Gingerbread to JB?
but I'm getting the jiffs of that program. I just need to play with it. some things I converted to User apps never loaded at all.
So I need to play with what I can put in User data that will still work. but none the less i been getting the builds to install.
And even show Play Store again.
Just need to mess with what works and dont in User data.
-Edit-
I tried to Make LatinIME Smaller and convert it to Userdata in the build options but every build has no keyboard support.
TroyFoxxin said:
Ill just leave it be then. Its always worked for me. if there was a problem it was with the ROM.
I haven't tried Google Play music before. but is it possible to port the music player from Gingerbread to JB?
but I'm getting the jiffs of that program. I just need to play with it. some things I converted to User apps never loaded at all.
So I need to play with what I can put in User data that will still work. but none the less i been getting the builds to install.
And even show Play Store again.
Just need to mess with what works and dont in User data.
-Edit-
I tried to Make LatinIME Smaller and convert it to Userdata in the build options but every build has no keyboard support.
Click to expand...
Click to collapse
Is there anyway you can post the updater-scipt from one of the builds you've made with OOne ROM Editor where you've modified the LatinIME.apk and specified to install as a User App? The updater-script is located in the /META-INF/com/google/android folder in the output/build ROM.
One thing to note tho, build options are reset after every build.
shinobisoft said:
Is there anyway you can post the updater-scipt from one of the builds you've made with OOne ROM Editor where you've modified the LatinIME.apk and specified to install as a User App? The updater-script is located in the /META-INF/com/google/android folder in the output/build ROM.
One thing to note tho, build options are reset after every build.
Click to expand...
Click to collapse
I noticed that it resets everytime. so i been ontop of that. I check both boxes in the build options before I build them.
I did read also not to delete LatinME.apk. and use the editor. But i know the LatinME is a nice chunk of Memory.
So to make it smaller and usable in User apps is plus to make the important things I need working.
-Edit-
I haven't been saving the bad builds. that attachment was for a new build I haven't tried yet.
and I just did. now keyboard working. But I think that build I didn't tell it to put Latin in User apps that time.
But I did use the editor. So I don't know.
TroyFoxxin said:
I noticed that it resets everytime. so i been ontop of that. I check both boxes in the build options before I build them.
I did read also not to delete LatinME.apk. and use the editor. But i know the LatinME is a nice chunk of Memory.
So to make it smaller and usable in User apps is plus to make the important things I need working.
-Edit-
I haven't been saving the bad builds. that attachment was for a new build I haven't tried yet.
and I just did. now keyboard working. But I think that build I didn't tell it to put Latin in User apps that time.
But I did use the editor. So I don't know.
Click to expand...
Click to collapse
I can't tell what you installed as user apps from the updater-script, but there were apps installed to the user ( data ) partition. And the assert() statement is missing from the script, so I know that option was checked in the Build Options.
The reason I say not to manually move it is because the LatinIME Keyboard Editor should be used to edit it's dictionaries. Once you press the "Apply" button in the LatinIME Keyboard Editor, it removes the LatinIME.apk from System Apps and actually puts it in the apps Recycle Bin. I use the list of files in the Recycle Bin as a filter of files not to include when building the ROM. LatinIME Keyboard Editor also looks in the Recycle Bin for the LatinIME.apk if it can't find it in System Apps but it assumes that it's deleted so it won't do anything.
I am actually working on OOne ROM Editor right now. So you can be on the lookout for an update
shinobisoft said:
I can't tell what you installed as user apps from the updater-script, but there were apps installed to the user ( data ) partition. And the assert() statement is missing from the script, so I know that option was checked in the Build Options.
The reason I say not to manually move it is because the LatinIME Keyboard Editor should be used to edit it's dictionaries. Once you press the "Apply" button in the LatinIME Keyboard Editor, it removes the LatinIME.apk from System Apps and actually puts it in the apps Recycle Bin. I use the list of files in the Recycle Bin as a filter of files not to include when building the ROM. LatinIME Keyboard Editor also looks in the Recycle Bin for the LatinIME.apk if it can't find it in System Apps but it assumes that it's deleted so it won't do anything.
I am actually working on OOne ROM Editor right now. So you can be on the lookout for an update
Click to expand...
Click to collapse
Well I got everything to work. Keyboard, Play Store, etc. But not sure ill stick with trying to put JB on the phone.
Its really slow. Unless more free space on the system partition would allow it to run faster.
Would your OOne ROOM Editor work on Any rom Like a CM7 Rom? or just JB ones? if not would you consider support for other roms?
I haven't tried, but figure I would ask.
TroyFoxxin said:
Well I got everything to work. Keyboard, Play Store, etc. But not sure ill stick with trying to put JB on the phone.
Its really slow. Unless more free space on the system partition would allow it to run faster.
Would your OOne ROOM Editor work on Any rom Like a CM7 Rom? or just JB ones? if not would you consider support for other roms?
I haven't tried, but figure I would ask.
Click to expand...
Click to collapse
OOne ROM Editor is just for ICS and JB ROMs. It's really not needed for Android versions prior to 4.0.