Hello all, I recently purchased a Motorola Cliq about a week ago and was new to the Android scene. I just sold my iPhone 3gs the day the nexus was announced (got 550, sweet!) and now I'm waiting for my Nexus to get here.
I rooted and flashed custom Roms onto my Cliq and everything was fine. I'm just curious if there are any differences in the process of doing things with the Nexus one than the Cliq.
I know the Cliq doesn't offer Apps2sd yet, and I'm still not sure what all the Ext2, Ext3, or Ext4 partitions are for it, so if anyone could explain some of this new basic stuff for me, or possibly direct me to a new source I would greatly appreciate it.
Thank you,
Hitorii
Rooting is much easier on the N1--Google gave us an easy way to do it. Flashing roms is the same basic process.
The N1 doesn't offer apps2sd yet, either, and it doesn't need it. It has a TON of room for apps already. ext2, 3, 4 are filesystems. Like FAT or FAT32, NTFS on Windows? Well Windows uses NTFS, Linux uses EXT. EXT2, 3, and 4 are newer, faster versions of it. (While we're on the subject, EXT journaled filesystems are one of the huge reasons Linux is so much better--that's why the filesystem doesn't get corrupted and you never need to defrag Linux).
the Nexus One development section has the tutorial to unlock your bootloader, flash your recovery, and install a rom/addon pack (yes you should do it in that order)
Wow, that's the perfect answer. Thank you! I was just curious what makes Ext4 better than Ext2.
I'm really excited! I can't wait.
On a side note, I'm super mad at the reviewers bashing the Nexus One in favor of a new unannounced iPhones. Primarily Engadget...shame
melterx12 said:
the Nexus One development section has the tutorial to unlock your bootloader, flash your recovery, and install a rom/addon pack (yes you should do it in that order)
Click to expand...
Click to collapse
Thank you, im checking it out now =)
Hitorii said:
Wow, that's the perfect answer. Thank you! I was just curious what makes Ext4 better than Ext2.
I'm really excited! I can't wait.
On a side note, I'm super mad at the reviewers bashing the Nexus One in favor of a new unannounced iPhones. Primarily Engadget...shame
Click to expand...
Click to collapse
ext3 is newer version of ext2. and ext4 is the newer version of ext3. Most people agree there is no noticable difference between EXT3 and 4, but EXT2 can cause some compatability issues between ROMs. In any case when you get your Nexus One, you should not make any EXT partitions or swap partitions. These are totally un needed on a phone with such high specifications. You will not see any speed increase and the constant activity on your microSD card will lower the lifespan of the card.
OK, first you don't need to worry about the Linux partitions as you will likely not require them. The Nexus One has quite a bit of space right now, and will likely be fine long enough for official apps to SD support to come out. Second, NTFS and EXT 4 are fantastic filesystems, but north of them fragment. When using solid state drives, this becomes less of an issue (non-issue really) since there is no mechanical movement to resolve addresses on storage. We are using solid state storage (chips and SD card) so it isn't a problem at our scale. These devices can wear out, but most of the time a repartition and format will deactivate bad blocks and let them work again. Very cool items.
Ext4 partitions can and do become fragmented. They are even working on making a defragmenter for it. However, that doesn't seem to be a very high priority to Theodore Ts'o, the developer of ext4. In any case, ext2 doesn't have journalling, whereas ext3 and 4 do. Basically, the higher versions have more data security (for example, if your computer shuts off unexpectedly, you are less likely to lose data), but involve more writing, making them less suitable for flash media, which can wear out after too many writes. (Disc-based media can also wear out, but it takes far longer to do so)
Related
Hello everybody
By now, most of us use some kind of apps to SD. We have some pros (LucidRem, MarcusMaximuss, Cyanogen, others) who paved the way and take gread deal of time to teach those who don't quite have a good grip on it. Everybody's mileage varies, and I think the way people run their roms has an impact on how Apps2SD will perform. Some people switch roms every so often and others stick with a rom for a while. I would like to see how Apps to SD perfrom in the long run. Hopefully it will be helpfull to developers as we may potentionally uncover some patterns here.
FYI: I am looking to get at least 100 votes on this before it can be considered helpfull to MarcusMaximuss or other devs so don't be shy
Feel free to post your individual experiences but PLEASE, DO NOT GO OFF-TOPIC!!! IF YOU NEED TO ASK A QUESTION- PLEASE DO SO IN THE RELATED THREAD. QUESTIONS WILL NOT BE ANSEWERED HERE!!!!
Thanks for looking and don't forget to show respect and donate to real pro's here... they are the one's that keep XDA going strong.
By the way..... for those of you who may wonder why there's no "I keep having force-closes and other problems with my Apps2SD" poll options: It is because once it's up and running you REALLY shouldn't have that kind of problems with it. If you do- you're rather an exception to the rule then a rule itself.
Good luck to everyone still trying to figure it out.
Have had my apps on the SD card since the instructions came out.....all via command line...no GUI. Was *never* able to get /data/data moved to SD without all sorts of problems. But just the apps worked fine.
It's been a mostly positive experience. I have about 120 apps installed at the moment. I've pretty much stopped using my laptop entirely and instead use my phone for a lot of stuff I do.
I also stepped up to the unionfs method about 3 weeks ago. It worked flawlessly for one week, then my phone seemed to perform a self-wipe.
At that time I reflashed to TDOL with built-in support for unionfs and have been using it ever since. Friday I upgraded to 1.2b.
Apps are a tad slower to launch, even on a class 6 SD. But that's a small price to pay for having the space to install so much.
One of these days I have to move the caches back over. Never did re-do that after moving apps to SD.
Well, I must say that lucid's version with the symlinks was by far the easiest to set up and use.
I had a very difficult time getting Apps to SD 2 working and find it harder to manage but it is going strong.
I am now using Apps to SD 2 on an ext3 partition and it seems ok so far.
I wish there was an easier way but if anything gets messed up with Apps to SD 2 it means format and start again
Hi Guys (and Girls OFC)
Long time lurker, First time poster, so first of all a big "Hello and Thankyou" to you all.
A great deal of you have helped me along the way in one means or another while I have been lurking, Whether you realized it or not so i decided it was time to step out of the Shadows and make the most of this Community, as i have my G1.
So Secondly...Props to all of you that have taken everything that is Good with open source software, and REALLY made it all worth while. Communities like this with Devoted Developers such as Cyanogen is what Android is all about and makes me realize a Medocre (IMO) Mobile can be made into something SO Unique.
Anyways, The Reason for this post (There is one, Honest)
Since Rooting my Phone I have Managed to, Touch Wood, Not totally and utterly **** it all up, Mainly because I took time to read Instructions on this site and NOT charge in two footed. But Although my G1 is as fast and as powerful as ever, I feel Im merly making the most of what I have, Not what I COULD gain. Therefore I was wondering if we could pull the Exhaustive knowledge from you all to Make a "Wiki" on Rooting? (Not Neccerily Just Cyan Mods, but it seems a Popular place to start)
I have Limited Knowledge, And am crying out to actually KNOW what "Compcache" and "Swapping" Ect. Do and why; The benefits and downfalls to it all and all other Pieces of Vital Infomation that sometimes cant always be found with a Board Search (God knows I tried).
So if everyone who Popped their Head in here just Added ONE piece of Infomation regarding Rooting, No Matter how Trivial it may sound to you, We could have a good starting point for all Newbies and Anyone stuck with a Query.
If this is all deemed worthless and I have missed a similar Thread, Please feel free to close it Mods.
Sorry for the Long Post, But I hope you Might all find it useful in the Future
See you About
KYI
This is currently something that is under development on Cyanogen's website.
** Also, this is probably not in the right sub forum.
This is probably supposed to be in the Dream subforum of the Dream... ah well i would just keep it here until there's actually something put together that would benefit n00bs... cuz i remember when i first got my G1 rooted i went around EVERYWHERE trying to find good info for updates etc, and 5 months later there's good info. but even those threads aren't the best: if we combined all of those and made it a bit simpler for people that seriously don't know what they're doing, we'd have something good on our hands. also if we answered all potential n00bish questions.. I also suggest you change the title to a Hero/Cyanogen thing cuz alot of them might have rooted not just for performance but something that looks nicer than cupcake and what donut currently is...
and now i'm wondering whether to actually post something useful... well here goes:
compcache takes a part of the cache (I THINK lol), compresses it, and uses it as RAM. adds much-needed RAM to the G1!!! then there's swap: runs with a swap partition, and now they've figured how to do that with swap files, that use the SD card, preferably a class 6, (i recommend Sandisk's newest Mobile Ultra cards) to use as RAM. best settings are 40 swappiness and 18 memlimit and 0 disksize for compcache. Cons for compcache: lags with lots of usage... unless you have backing swap enabled at 40 swappiness.
Cons for linux swap: lags more than compcache usually... same optimal settings= 40 swappiness. not really laggier than compcache, just happens to be slower and compcache seems to manage swap better... same thing, different processes when you compare backing swap (basically a linux swap backup for compcache when it overflows) to linux swap(plain old linux swap. i don't know the first thing about linux... except that it's like a page file, using a storage medium as RAM)
the swapping thing you want to know is all here if you search for it. A good linux swap thread is this one. Itll teach you alot about linux swaps.
I had the same thoughts a while back when Ion was "the big thing" HERE is what I put together about "how to root" then. Hope it is helpful.
For any noobs looking to root though I recommend doing it the long frustrating way of my last post to learn more about your device HERE is the simple way. -Hope this too is helpful.
Thank you to all the developers who spend so much time reinventing our worlds!!!
I recently moved from a nandroid HD2 to a droid x2. I was forced to switch from t-mobile after a move due to poor service and verizon was my only choice if I wanted continuous 3g. I was never a fan of the x's look/bulk but the processors were very attractive and 4g is a long way off in my little town.
I never studied any other forums activity but I knew the droid lineup was popular and I expected no less from the x2 but from what I can tell the 4g thunderbolt and charge are getting all the love. The x2 doesn't even have a forum yet and only about five guys seem to care and I feel the droid lines aftermarket is hindered by the locked boot loader. Now on the HD2 the early roms were run off of the sd card and they were actually faster since my casas 8sd card was faster then my nand memory. What if we were to use a class 10sd and write a boot loader? I would also like to see a super ram edition like they have for the hd2...
Hi,
I don't think we can "write a bootloader" that would supersede the Motorola device. I may be in error here, but Motorola processors include bootloader triggers in the hardware - this protects the processor core ROM from being messed with outside. Motorola calls it security.
If we were to write our own bootloader, I think it would require the "key" to allow the processor to redirect away from the internal starting address to the SDCard...in other words, we would need to unlock the exisiting bootloader in order to redirect to ours running in SD RAM.
hax0red said:
I recently moved from a nandroid HD2 to a droid x2. I was forced to switch from t-mobile after a move due to poor service and verizon was my only choice if I wanted continuous 3g. I was never a fan of the x's look/bulk but the processors were very attractive and 4g is a long way off in my little town.
I never studied any other forums activity but I knew the droid lineup was popular and I expected no less from the x2 but from what I can tell the 4g thunderbolt and charge are getting all the love. The x2 doesn't even have a forum yet and only about five guys seem to care and I feel the droid lines aftermarket is hindered by the locked boot loader. Now on the HD2 the early roms were run off of the sd card and they were actually faster since my casas 8sd card was faster then my nand memory. What if we were to use a class 10sd and write a boot loader? I would also like to see a super ram edition like they have for the hd2...
Click to expand...
Click to collapse
I'm referring to a more indirect boot of a custom android similar to what was used on early HD2 android builds where you would boot windows 6.5, execute an application that loaded the boot for android directly into memory so yes it's completely possible. I would love to see it intercepted before a full dalvik execution to speed up the process but I'm not familiar with programming in anything but win32 on a PC although I'm considering learning if I'm to keep this phone
There some people trying to do something like that using kexec, but I think they're still pretty far off.
hax0red said:
I'm referring to a more indirect boot of a custom android similar to what was used on early HD2 android builds where you would boot windows 6.5, execute an application that loaded the boot for android directly into memory so yes it's completely possible. I would love to see it intercepted before a full dalvik execution to speed up the process but I'm not familiar with programming in anything but win32 on a PC although I'm considering learning if I'm to keep this phone
Click to expand...
Click to collapse
So if I follow this, you mean to run Android as an application or virtual operating system on top of the bootloader.
I expect that while you might make the program run faster in fast memory, all hardware calls would still be through the ROM and I suspect this would add significant delay. It certainly is possible, but I think it would require a fast processor in order for system calls to be fast.
My opinion, I haven't tried it, but it might be worth a test....I suspect it is doable, but I don't think it will be fast enough on the DX processor.
GolfnWrx said:
So if I follow this, you mean to run Android as an application or virtual operating system on top of the bootloader.
I expect that while you might make the program run faster in fast memory, all hardware calls would still be through the ROM and I suspect this would add significant delay. It certainly is possible, but I think it would require a fast processor in order for system calls to be fast.
My opinion, I haven't tried it, but it might be worth a test....I suspect it is doable, but I don't think it will be fast enough on the DX processor.
Click to expand...
Click to collapse
Not quite... he's talking about haret, which allows you to completely kill winmo and boot a Linux kernel. The benefit is that winmo initializes all the hardware for you, so the kernel doesn't have to be perfect. Unfortunately, it means the android file systems are probably on sdcard and therefore slower than usual. It was a pretty slick setup in some of the older winmo devices (Vogue, Kaiser, Polaris, Leo, diamond, raph, rhodium, etc.) for running android.
Those were good times...
Anyway, that's basically what the kexec guys are hoping to do: let moto init the hardware, then kill android, fire up a new kernel, and start a custom rom.
mrkite38 said:
Not quite... he's talking about haret, which allows you to completely kill winmo and boot a Linux kernel...
Click to expand...
Click to collapse
I guess I was confused, I did read up on haret, thanks for the reference.
Not sure how you can bypass the bootloader in the droid-x though, it's connected to the e-fuses inside the cpu, the cpu processes will simply fail to answer calls, right? That's what causes the bootloop.
Truly wish you the best of luck on this one.
Assuming the hardware is identical for the Google edition S4/ to the ATT version, i assume once you PhoneWizards get a hold of one of them and remove the ROM or Google is a G and releases that said ROM , we could jimmy that onto an ATT bought phone and be in Google heaven?
Like wise the updates could be applied as needed via the code release or extraction?
or is there some neeto software lock they are cooking into that so it wont work on a Non "edition" phone? (at least until the smarties hack it)
Okay thanks !
i booted up CM10.1 yesterday, and thank god for you people, i donated 10 bucks to the cause
This ROM's release will show how the developers at Google and HTC are at a different level when it comes to ROM development and stability! I can't wait for the release.
Agree
Weldzor said:
Assuming the hardware is identical for the Google edition S4/ to the ATT version, i assume once you PhoneWizards get a hold of one of them and remove the ROM or Google is a G and releases that said ROM , we could jimmy that onto an ATT bought phone and be in Google heaven?
Like wise the updates could be applied as needed via the code release or extraction?
or is there some neeto software lock they are cooking into that so it wont work on a Non "edition" phone? (at least until the smarties hack it)
Okay thanks !
i booted up CM10.1 yesterday, and thank god for you people, i donated 10 bucks to the cause
Click to expand...
Click to collapse
I totally agree. I can't imagine the rom being too different. I just purchased an ATT GS4 for $1.74 from BestBuy. I couldn't give up the deal especially with the GE GS4 going for over $500, but I'm hoping to install the GE rom on it. Either that or I'll sell mine on ebay and just buy the GE outright. I hope this comes soon. Wanted to put CM on it but read that I would lose the IR and bluetooth on it. Wasn't worth it for me to lose it.
mrwifi said:
I totally agree. I can't imagine the rom being too different. I just purchased an ATT GS4 for $1.74 from BestBuy. I couldn't give up the deal especially with the GE GS4 going for over $500, but I'm hoping to install the GE rom on it. Either that or I'll sell mine on ebay and just buy the GE outright. I hope this comes soon. Wanted to put CM on it but read that I would lose the IR and bluetooth on it. Wasn't worth it for me to lose it.
Click to expand...
Click to collapse
From what I've been reading...the google edition probably won't have support for the ir blaster or other new sensors...but right now it is just speculation
Sent from my HTC PH39100 using Tapatalk 2
I think the devs will be able to get it ported over to the other GS4 variants and vice versa for any google edition S4 owners who want the Samsung ux.
itismadhan said:
This ROM's release will show how the developers at Google and HTC are at a different level when it comes to ROM development and stability! I can't wait for the release.
Click to expand...
Click to collapse
What does HTC have to do with anything? You must mean Samsung?
Sent from my SPH-L720 using xda app-developers app
Google stock will have drivers for those sensors.. just lack of package to enable features (which is Touchwiz). Probably 3rd party remote apps still can use IR blaster.
Sent from my SGH-I337 using xda premium
Does anyone know when this is expected to be released ?
LordGeek said:
Does anyone know when this is expected to be released ?
Click to expand...
Click to collapse
June 26th I think
Sent from my WICKED AT&T S4
I wonder if the Google edition S4 rom will support exFAT SDCards. If it does, I would switch from Samsung's roms. If it does not, I won't.
I most certainly will NOT use FAT32 formatting on my 64GB SDCard!!
rcklss1 said:
June 26th I think
Sent from my WICKED AT&T S4
Click to expand...
Click to collapse
I've heard June 26th as well.
So is the only true advantage of getting the google edition phone is that it will have the boot loader unlocked? Since the current loki way of getting custom roms into our phones can be later patched and prevent us from installing newer version of android OS? Sorry for the noob question and observation.. but I still have time to return this the gs4 and just wait for the google edition so I'm trying to decided what is the best choice here.. I have the 32gb version which I would be losing that extra space and I'm hoping they offer it in black
doug0365 said:
So is the only true advantage of getting the google edition phone is that it will have the boot loader unlocked? Since the current loki way of getting custom roms into our phones can be later patched and prevent us from installing newer version of android OS? Sorry for the noob question and observation.. but I still have time to return this the gs4 and just wait for the google edition so I'm trying to decided what is the best choice here.. I have the 32gb version which I would be losing that extra space and I'm hoping they offer it in black
Click to expand...
Click to collapse
Well...I wouldn't return it if you got it with a contract, from what I understand the google edition will not be sold by carriers under a contract...so no $200 subsidized price. You will have to pay the full $600+ it costs...so if your interested in it than your probably gonna want to sell your s4 on craigslist for as close to full retail you can get...you should easily be able to pull in $600 for the 32gb
As far as other benefits besides an unlocked bootloader, we are not sure. It may or it may not come with drivers for the new sensors, one user claimed a page back that it would have drivers just not programs to use them...we don't know that, there is no solid evidence I'm aware of that says drivers will be included, its all speculation right now...I'm hoping they include drivers, but I'm not going to hold my breath for it either
Sent from my HTC PH39100 using Tapatalk 2
Almost certain things like the IR blaster wont be functional in the Google Edition devices, they already stated that the HTC One GE ir blaster won't be supported.
Curious why this isn't a more hot topic right now with the phones releasing tomorrow. Is there another thread somewhere with updated info?
Samsung AND HTC have google editions now
Their is also an HTC 'pure google' phone now, like they announced for the S4
eskomo said:
What does HTC have to do with anything? You must mean Samsung?
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
I bet the Google rom will be the fastest spreading rom ever. Just a hunch.
penguinjoe said:
I wonder if the Google edition S4 rom will support exFAT SDCards. If it does, I would switch from Samsung's roms. If it does not, I won't.
I most certainly will NOT use FAT32 formatting on my 64GB SDCard!!
Click to expand...
Click to collapse
Why not? There are ways to format a 64GB card as FAT32. I did so just fine on mine.
I'm curious about this as well. I'm using Nova Launcher, so at least I don't have to deal with TouchWiz, but pure would be nice...
Christopher3712 said:
Why not? There are ways to format a 64GB card as FAT32. I did so just fine on mine.
Click to expand...
Click to collapse
Dranakin said:
I'm curious about this as well. I'm using Nova Launcher, so at least I don't have to deal with TouchWiz, but pure would be nice...
Click to expand...
Click to collapse
There are a couple of reasons.
File size
FAT32 has a 4GB file size limit. That does not exist on a exfat filesystem. If I want to drop a 5-8GB HD movie on my sdcard, I can with exfat. With fat32, I need to either transcode the movie down to fit or split it up.
Fragmentation.
While the general thought is that SDCards don't need to be defragmented due to there being no moving parts, there is a study here that shows much different results: http://www.lagom.nl/misc/flash_fragmentation.html The results are shocking! Now add in the 32K cluster sizes (32GB sdcards only need 16k clusters) and you will see that fat32 filesystems would be a really bad idea for >32GB (or any for that matter) SDCards. Microsoft won't even support it. You have to go to third party utilities to force formatting these to FAT32. If Microsoft refuses to support >32GB on a drive with FAT32, what do they know that we don't? It is their file system!
Fat32 is simply a beefed up version of the FAT filesystem that was created in the 1970s. There really is no real difference beyond the bits used in the file allocation table to support larger and larger volumes. It is absolutely archaic in how it stores files and heavily prone to fragmentation. Worse, due to the limited lifespan of an SDCard or SSD, it is not recommended to defragment these often. Exfat has had its file allocation functions totally revamped to reduce or remove fragmentation. In fact it was designed specifically with solid state storage in mind.
So yeah, I'm, not keen on formatting my 64GB SDCard with FAT32. In fact if I could get away with exfat on my 32GB sdcard I be tempted to use it there too.
Hell, I would even be happy with ext2 or ext3 on my SDCard. I have no problem accessing Linux filesystems on my Windows box.
Hi,
I plan to flash TWRP to my T580 with Odin. And then pick a custom ROM to install.
It's an old device but I hope a custom ROM can extend its life a bit. I do plan to play a bit of game but not a lot or demanding one.
Given it has only 16 GB storage, one the key element is probably the ability to use SD card to run an app.
Any recommendation? Or is there any comparison people have made?
Thanks
redhonker said:
Hi,
I plan to flash TWRP to my T580 with Odin. And then pick a custom ROM to install.
It's an old device but I hope a custom ROM can extend its life a bit. I do plan to play a bit of game but not a lot or demanding one.
Given it has only 16 GB storage, one the key element is probably the ability to use SD card to run an app.
Any recommendation? Or is there any comparison people have made?
Thanks
Click to expand...
Click to collapse
Samsung, supposedly for security reasons, has made it more and more difficult to use SD cards for apps. So the 580 isn't a good choice for games requiring a lot of storage. You might want to search for "adoptable storage" in the ROMs threads. I don't use it but I'm constantly seeing post from people having problems with it. It appears the problems increase with the latest ROMs. As to which ROMs are best, it depends upon how you use your tablet. I'd advise reading the OP page for each one. They typically give a discription of the dev's emphasis when building their ROM.
I have a T580 and I've been making the rounds trying everything currently available. I have 2 strong recommendations for you.
#1 - Stick to ROMs based on Pie (9) for the moment. Most ROMS based on 10 still have some nagging bugs to be worked out. With that said the bugs I've seen might not necessarily be deal breakers for you, but keep in mind they exist and seem to affect all 10 based ROMS.
#2 - Avoid Adoptable Storage as a storage solution. I've tried to live with it on the T580 and at least a half dozen devices before it. But, it's just too fragile. Try to use apps2sd or link2sd or some other solution that uses symlinks to move app/data to the sd card. It can make backups and restores a little trickier, but at least it is much less likely to just bork your whole system out of the the blue one day.
Jaaxx said:
I have a T580 and I've been making the rounds trying everything currently available. I have 2 strong recommendations for you.
#1 - Stick to ROMs based on Pie (9) for the moment. Most ROMS based on 10 still have some nagging bugs to be worked out. With that said the bugs I've seen might not necessarily be deal breakers for you, but keep in mind they exist and seem to affect all 10 based ROMS.
#2 - Avoid Adoptable Storage as a storage solution. I've tried to live with it on the T580 and at least a half dozen devices before it. But, it's just too fragile. Try to use apps2sd or link2sd or some other solution that uses symlinks to move app/data to the sd card. It can make backups and restores a little trickier, but at least it is much less likely to just bork your whole system out of the the blue one day.
Click to expand...
Click to collapse
Thank you for the information.
Which ROM are you using now? I will just follow.
Besides apps2sd and link2sd, which solution exists? I"ve tried both before and has limited success. The offline files (obb) was a big issue.
Thanks again.