Database Develop

my phone is running too slow

well i was running cyanogen 4.2.6 with a theme and advanced launcher, stericson lockscreen..etc and my phone was blazing fast..then i decided i wanted to change the size of my partition and i forgot to back up and i lost everything..so i wiped repaired ext and flashed 4.2.7.1 and now my phone is slowww if i go to the browser and then home it takes about 8 seonds to apppear
so my question is what could i do to reverse this?

El Cipitio said:
well i was running cyanogen 4.2.6 with a theme and advanced launcher, stericson lockscreen..etc and my phone was blazing fast..then i decided i wanted to change the size of my partition and i forgot to back up and i lost everything..so i wiped repaired ext and flashed 4.2.7.1 and now my phone is slowww if i go to the browser and then home it takes about 8 seonds to apppear
so my question is what could i do to reverse this?
Click to expand...
Click to collapse
You may have to wipe your phone.

blacknightavalon hit it right on the nose. You have to wipe, you already mentioned you didnt backup your phone anyways. The wipe and reinstall of the Rom and advanced launcher should fix your problem. Think of it like a reformat of an operating system of windows. linux or apple on your desktop/laptop.

legend221 said:
blacknightavalon hit it right on the nose. You have to wipe, you already mentioned you didnt backup your phone anyways. The wipe and reinstall of the Rom and advanced launcher should fix your problem. Think of it like a reformat of an operating system of windows. linux or apple on your desktop/laptop.
Click to expand...
Click to collapse
I did wipe and reinstalled cyan 4.2.7.1 and I my phone is still slow...this is why I'm asking for help, maybe it is something I need to do...what a bout linux swap? Mine is 32 but I hears that's good for a donut rom :s

El Cipitio said:
I did wipe and reinstalled cyan 4.2.7.1 and I my phone is still slow...this is why I'm asking for help, maybe it is something I need to do...what a bout linux swap? Mine is 32 but I hears that's good for a donut rom :s
Click to expand...
Click to collapse
Increase SWAP to 128. You will see a major difference there but it seems like you had something else configured that you don't recall. Ensure that you wipe the device, dalvik, and ext this time just to get it right.
If you are really wanting to see some speed use THIS ROM. It has everything good about Cyanogen's but is MUCH faster and for me more stable. (Hope that is helpful)

Perhaps its just my phone, but I think 4.2.6 was faster than 4.2.7.1. I'm still running the latest from Cyan, but I do believe it's not as fast. I have a slight delay from Browser to home, but not 8 seconds.... maybe 3?

10mb hack
This should help http://fhl09.wordpress.com/2009/12/07/speed-cyanogen-up-2/

6dipset6 said:
This should help http://fhl09.wordpress.com/2009/12/07/speed-cyanogen-up-2/
Click to expand...
Click to collapse
Great reply... I'm about to try this as well to see how the speed differs from what I have now. My ROM is running well but if I can see improvements I'm willing to try it out.

I don't know if it makes a difference in Cyanogenmod, but a higher class sd card may help. It certainly did for me when I ran a hero ROM using a class 6 sd card, but then again, i don't know if cyanogenmod really needs a fast sd card

RodrigoKim said:
I don't know if it makes a difference in Cyanogenmod, but a higher class sd card may help. It certainly did for me when I ran a hero ROM using a class 6 sd card, but then again, i don't know if cyanogenmod really needs a fast sd card
Click to expand...
Click to collapse
yup, that should be another factor

RodrigoKim said:
I don't know if it makes a difference in Cyanogenmod, but a higher class sd card may help. It certainly did for me when I ran a hero ROM using a class 6 sd card, but then again, i don't know if cyanogenmod really needs a fast sd card
Click to expand...
Click to collapse
Interesting.... can anyone if Increase SWAP to 128 has made Cyanogen faster or not?

Optimizing android performance

Hello, I would like to know what steps that I can take to increase the performance of android on my vogue. I am using myn's warm donut rom, with the system installed on the nand and the data installed on my ext2 partition on my sd card. I have heard that Its a good ideal to enable swapping, but I do not know how to enable it. I already have my 8GB class 6 sd card partitioned with one fat partition, one 256MB ext2 partition, and one 1GB ext2 partition (for Data). If anyone has any suggestions or tips, please let me know. Thanks!
PS: is there a way to overclock my vogue while using android? I have tried using the clock.sh file from mssmison's legendary build, but that didn't work.
EDIT: Can i use an ext3 or ext4 instead of ext2 for the partitions on the sd card?

Soon there will be an app for overclocking. Myn is currently working on it.
Other that that, make sure you're always on the latest nbh and Myn release.
Get yourself a task manager and be mindful of what processes you actually need.

Use clearcache often.

go into dev tools/development settings and set the window and transition animation to OFF. i noticed that not only does everything open super quick but it did increase the overal performance

you can't use ext3 or 4 no. First thing is to make sure if you are running data on your sdcard that you are using a fast sd card (not a cheap one).
That's what is giving you the biggest performance hit right now.
There is an OC app coming but to be honest it really should be running quite snappy for you.

Thanks guys for all of the info. I have just one more question. should I enable swapping on my android? Advanced task manager usually reports that I have around 46-40MB of free ram.

If you have a lot of free memory already, there is no reason to use swap.

Ok, I have one last question (I apologize if I'm being a bit annoying). I tried installing and using Adfree on my vogue, but when I run it, it says "Cannot locate the 'cat' util on your system". Does anyone know how I can fix this? also, when my phone is connected to my charger, my phone's 3g speeds are really good, but when It's not on the charger, the 3g slows down. Normally I'm ok with it, but it may make playing some games online a bit more difficult when off the charger. Is there some way I can fix this? Thanks!

slow88lx said:
Soon there will be an app for overclocking. Myn is currently working on it.
Other that that, make sure you're always on the latest nbh and Myn release.
Get yourself a task manager and be mindful of what processes you actually need.
Click to expand...
Click to collapse
Can you install a new .nbh without updating the release you are running, or do you need to wipe the phone every time?

conanford said:
Can you install a new .nbh without updating the release you are running, or do you need to wipe the phone every time?
Click to expand...
Click to collapse
you can flash nbh without wiping system or data

[Q/Dev suggestion] Space for another big ROM slot in internal storage?

Taken from CM12 thread as this started to become off-topic. The issue I'm trying to address is how to stuff a huge Lollipop ROM directly into internal storage, without creating a virtual slot, to increase system performance and have overall cleaner solution. Original inspiration: @Mentor.37's custom Safestrap for unused partitions, which has way too small /data for me unfortunately. (explanation)
sd_shadow said:
Septfox said:
This in mind, is there any way to repartition the internal (stock) storage to decrease the size of /cache/ and create a larger /data/ partition, or is it not possible without modifying the bootloader?
Click to expand...
Click to collapse
Code for mounting the unused preinstall and webtop partitions to SD storage http://forum.xda-developers.com/showthread.php?p=59253593
Click to expand...
Click to collapse
This allows you to mount the partitions either as a new storage or to a specific directory only, in other words it does not merge the storages, just adds a mount point next to (or possibly if modified a bit on the top of) other storage. While this may be useful for taking some inherent load off /storage/sdcard0/ (i.e. mounting /dev/block/webtop to /storage/sdcard0/Downloads) for people not swapping their sdcards, it doesn't help in Septfox's intention of enlarging /data/.
I face the same problem as Septfox: I'd love to use the storage intended for running system for it, not virtually mounted storages created in the storage intended for storing media and support data. However, the outline of the storage is intended for way older and less robust system so even the /system/ is not quite enough (667 MB, which tightly fits CM12 with a small GApps package) and /data/ is also not enough for heavier use (3.22 GB). Therefore I would like to merge it with currently unused partitions: maybe join preinstall to system and webtop to data, making both big enough.
One alternative would be to mount the 1.4 GB webtop as /data/app, which currently makes about 2/5 of occupied space of my /data. Is this possible? At which point of system startup is the script in /system/etc/init.d executed (is it done by Safestrap or the ROM itself?), and at which point might the system first need to access /data/app that contains the APKs of user-installed apps? All the really needed stuff (compiled executables) is in the /data/dalvik-cache, right? Here I'm on a really thin ice, don't know much about Android's architecture, so sorry if this is a major bullsh*t - just throwing my idea in Technically what I'm talking about is such modification of the script:
Code:
#!/system/bin/sh
mount -o rw,remount /data # Not too sure about this
# - depending on whether /data is already rw or not.
# For that I would need to know when is the script
# executed. I'm almost sure this is not necessary
# though. In original script this was done to allow
# writing into /storage/.
mkdir /data/app
#mount -o ro,remount / - unnecessary, see above
#mount -t ext3 /dev/block/preinstall /storage/preinstall
# I don't see any use for small preinstall partition.
mount -t ext4 /dev/block/webtop /data/app
chmod 777 /data/app # not sure about this either,
# probably should be 771
Clean version:
Code:
#!/system/bin/sh
mount -o rw,remount /data # Unnecessary?
mkdir /data/app
mount -t ext4 /dev/block/webtop /data/app
chmod 777 /data/app # Possibly 771 instead.
Is that possible to run, or will it bootloop, what do you think?
Even better IMO would be to delete preinstall and webtop and shrink the Stock data down to maybe 200 MB so the original Stock system is still present, preventing the phone from bricking and accommodating Safestrap. The remaining space could be divided between Safe system (say 800 MB) and Safe data (over 4 GB). Are we able to do this somehow, maybe by customizing Safestrap a bit more? Or are partitions in /dev/block locked by bootloader? Also are all these and Internal storage located on the same physical chip, or are there two separate memories in the D4? Attached proposal of repartitioned layout Sizes taken from here and here.
Developers and experienced users, I would love to hear your opinion, mainly on whether repartitioning internal storage or at least mounting webtop to /data/app could work on D4. Thanks!
Addition to the original post:
I have a spare D4 with shattered screen and not working SIM slot that I bought for spare parts. Apart from GSM (or telephony altogether? I didn't try, as only option would be emergency call which I don't want to abuse, and we don't have CDMA networks here) it works fine though. I can try meddling with formatting/partitioning - it won't be too big deal if it gets bricked beyond possibility of SBF restore.

Replies so far, taken from the original CM12 thread:
sd_shadow said:
I don't think repartitioning is possible without high risk of hard bricking the device, and yes the locked bootloader does limit what can be done.
This is quite off topic, and you should start a new thread if you are going to continue.
Click to expand...
Click to collapse
Good call, started new thread
lucize said:
tried to change the type of preinstall partition and the device would boot into fastboot: (invalid cg hab (cg: ebr, status: 0x0056)
so a recovery is needed, I'll try a resize if I can compile the tools in safestrap. but I think it would not work
later edit: used fdisk to resize in safestrap and it broke again so it can't be done
Click to expand...
Click to collapse
Thanks for trying! What do you mean by changing type?
As I added here in the first post, I have a spare shattered but mostly working D4 I wouldn't be too sad to see bricked - I can try out more dangerous stuff if you point me in the right direction. I'd like to help testing different approaches to repartitioning if you have some potentially harmful ideas that you wouldn't try on your own phone.
Curious question aside: where is bootloader (and fastboot) stored? Is it sitting on some other small partition? Can we mount it to be read, or even to write there? What/where is that protection that keeps us from unlocking the bootloader?
Also, concerning mounting the free partitions to other system partitions: do you think it's possible to mount them as a folder in /data (whichever we use)? Does it matter what filesystem the partitions use? What part of boot-up runs the /system/etc/init.d/ scripts? Do you think attached proposals 2 or 3 are feasible? It would still have the stock system untouched for an emergency use and Safestrap storage, but its data would be shared with the safe system, with webtop mounted as /data/app or /data/data (1.4 GB should suffice I hope) which would leave us with nice 3.2 GB for the rest. Of course, preinstall's 600 MB for /system is hardly enough for CM12 with Pico version of PA GApps so the rest of used Google apps would inflate /data a bit - but still this is probably the best option we have now.

Actually, I find the stock /system/ to be adequate. Yea, it's a tight fit, but CM12+PA Micro Gapps slots in with 30-someodd megabytes to spare, and there shouldn't be any real need for additional space on top of that. Though, I suppose there could be trouble if CM starts including larger apps.
Init.d is done by the ROM itself, and has to be enabled at build time; CM12 actually has it shut off for whatever reason (Slimkat did as well, I would imagine CM11 also did). There's an app called "Universal Init.d" in the Store, but by the time it can get around to executing the scripts, it's obviously way too late to be screwing with vital partitions : \
Worth pointing out that Safestrap appears to have proper ADB access, you might be able to do something with partitions thataway. I don't know enough about partitions and mounting in Linux to take a jab at it. Woop, looks like that's already a no-go. Maybe the bootloader does a check or three to make sure the partitions are all in order, and throws a critical error if not.
If absolutely all else fails, there's still symlinking large apps into the newly-accessible partitions that can be done, either manually or with Link2SD/similar apps. It's a bit of a hassle, but an option nonetheless.

Well, stock /system is fine but I want to keep it untouched - mainly because I don't want to install CM12 as an update over stock JB, and also to keep myself from SBFing (at least in the long run) because of trivial issues. When this option is off the plate, the remaining partitions don't seem to offer enough space to run CM11 in a non-virtual slot (as Mentor.37 offers with his modified Safestrap with a "Safe" slot with 600M system and 1.4G for data).
Symlinking is an ugly solution - used it for a while, never liked it, mainly because symlinks broke once SD got unmounted or mounted as Mass Storage, with problems remounting afterwards.
Since we can modify the system freely, I'm sure that if necessary, we could make a neater solution than using an app to create symlinks after boot. Question how early in the boot process can we add some scripts (by flashing some zipped patch over the ROM) goes to more knowledgeable devs though...

first time I just used t option in fdisk to change partition type to whatever without changing size, the second time I resized some of them and every time after 1st reboot the M logo would appear for 1 second and from now on it would go straight into fastboot without M logo, so it seems that something in bootloader is verifying the layout or something and if is not good it would stop.
I don't think that it's possible to brick it for good, use rsd to recover
Regards

Thanks to @lucize for his trying, sadly it seems we can't repartition at all
@Mentor.37, is there a source to your customized SS 3.75 available? I'd like to try and mess around with it to put the Proposal 3 from my second post's attachment to work.
Could mounting and symlinking be done from Safestrap, or does the ROM do it itself? I have ideas of various cross-linking of folders on the partitions to kind of emulate repartitioning - but I'd have to try if it works and it would need to be done either before the system boot or shortly in the process. See attachment - that's a first draft I presume for this that the user keeps stock system only for keeping the phone bootable no matter what happens in other than stock slots, so stock data would be utilized only for root and safestrap, leaving most of its 3.2 GB free.

LuH said:
Thanks to @lucize for his trying, sadly it seems we can't repartition at all
@Mentor.37, is there a source to your customized SS 3.75 available? I'd like to try and mess around with it to put the Proposal 3 from my second post's attachment to work.
Could mounting and symlinking be done from Safestrap, or does the ROM do it itself? I have ideas of various cross-linking of folders on the partitions to kind of emulate repartitioning - but I'd have to try if it works and it would need to be done either before the system boot or shortly in the process. See attachment - that's a first draft I presume for this that the user keeps stock system only for keeping the phone bootable no matter what happens in other than stock slots, so stock data would be utilized only for root and safestrap, leaving most of its 3.2 GB free.
Click to expand...
Click to collapse
I believe that it's impossible because symlinking "works" after kernel is loaded and safetrap take place (is loaded) before a kernel is loaded....

If I'm not mistaken, symbolic linking is a filesystem thing, something like a shortcut only more complex (after all, it's completely transparent to anything accessing it). ADB probably has commands to make links, terminal emulators in Android definitely can. I think the problem you face is making sure the mountpoint, path, etc are exactly the same both in SS and Android.
Probably better to just do both the mounting and symlinking under Android, so you can be 100% sure that everything matches. We already know /cache/ is unused most of the time under LP, and can (probably) even be unmounted while booted if needbe; why not experiment with it, rather than going straight for the other more important partitions, until you're sure what you're thinking will work?
Edit: Wikipedia has a big ol' writeup on symlinks under various systems, looks like a fun read.

rblanca said:
I believe that it's impossible because symlinking "works" after kernel is loaded and safetrap take place (is loaded) before a kernel is loaded....
Click to expand...
Click to collapse
I guess then this could be implemented in some early booting stage of the system by some custom .zip being patched over, kind of the way Mentor.37's ramdisks are. Unfortunately I don't have nearly enough knowledge to do it.
What I hope could be done more easily is altering SS to maybe use not only shared cache but shared data as well - then webtop could be used for safe system, leaving more then enough space for it, and we still would have fairly usable 3.2 GB data for it. Maybe we could even assign preinstall as stock data? @Mentor.37, I'd really love to hear your opinion on this, or maybe even get your alternated safestrap's source so I could try it myself

Sorry guys, I'm dropping this. I tried CM12 in stock slot and it doesn't help the system as much as I hoped for, so there's no need for this from my side.
I also mistook the process of installing ROM in Stock. I thought I have to upgrade the stock system to the new ROM in order to keep Safestrap in it, but it turns out it's independent and when "wiping" stock /system it leaves the Safestrap there, so I can easily do a clean install of a new ROM in the stock slot

LuH said:
I tried CM12 in stock slot and it doesn't help the system as much as I hoped for, so there's no need for this from my side.
Click to expand...
Click to collapse
About that, could you compare the difference regarding performance between CM12 on the safe slot and CM12 on the stock slot?
I currently got it running on safe slot but I'm thinking about trying to install it to stock slot, now that I sold my Lapdock and don't need Weptop mode anymore.
But I only would do it if it increases the performance of the D4.

Shani Ace said:
About that, could you compare the difference regarding performance between CM12 on the safe slot and CM12 on the stock slot?
I currently got it running on safe slot but I'm thinking about trying to install it to stock slot, now that I sold my Lapdock and don't need Weptop mode anymore.
But I only would do it if it increases the performance of the D4.
Click to expand...
Click to collapse
I don't really remember unfortunately, been running it from stock slot for a while now. Before it definitely was way more laggy than now, but that's also when CM12 for D4 was in a VERY early phase.
It definitely increases the performance, I'm just not sure how much. I don't see any reason why leave original system in stock slot though, so no reason to run CM from the safe slot. I don't like the idea of mounting the ext fs with system running from it from fat storage, it's bound to generate some unnecessary overhead.
In case of any major screw-up, sbf is your friend and AFAIK can't get messed up itself It's a good idea to have the factory cable available though, just in case it for whatever reason dies on you with low battery.

Ok, still good to know, thanks! What's sbf?
Well when I got my D4 a few months ago, I thought installing on the stock slot would be dangerous (in terms of bricking) and since I had the Lapdock, I wanted to keep the stock ROM.
But since then I've read that many users have CM12 running on stock slot, so now I want to do that, too. It's just so annoying when the whole phone freezes for half a minute or so and I think that's mostly due to the limited memory (although I have 170-300 MB free most of the time).
Do I have to consider anything special or different while installing than on an install on safe slot?

Shani Ace said:
Ok, still good to know, thanks! What's sbf?
Click to expand...
Click to collapse
see
Q12: What is a SBF?

Shani Ace said:
It's just so annoying when the whole phone freezes for half a minute or so and I think that's mostly due to the limited memory (although I have 170-300 MB free most of the time).
Click to expand...
Click to collapse
Same here, I suspect it's also connected with throttled data transfer requests of multiple apps at once, but the RAM is IMO the biggest factor. In Linux RAM is almost always full and the "free" space is occupied by cache (filesystem cache or whatever else app's cache) ready to be deleted - maybe the phone is stuttering when freeing the "free" space for other use.
Weird is that my brother with almost vanilla L 5.1 on Nexus 4 has system consuming about 100M less RAM than my CM12 - device-specific drivers maybe?
Shani Ace said:
Do I have to consider anything special or different while installing than on an install on safe slot?
Click to expand...
Click to collapse
If you mean on stock slot, just remember that you need to have some system installed there even in order to boot into safestrap - delete old, install new and ONLY then reboot, otherwise you're facing sbf Learned the hard way It doesn't brick your phone (meaning you can unbrick it), but it's lengthy and annoying...

@sd_shadow: Thanks, now I know. Feels kinda stupid having asked one of the FAQ's - can't remember when that happened before.
LuH said:
Same here, I suspect it's also connected with throttled data transfer requests of multiple apps at once, but the RAM is IMO the biggest factor. In Linux RAM is almost always full and the "free" space is occupied by cache (filesystem cache or whatever else app's cache) ready to be deleted - maybe the phone is stuttering when freeing the "free" space for other use.
Weird is that my brother with almost vanilla L 5.1 on Nexus 4 has system consuming about 100M less RAM than my CM12 - device-specific drivers maybe?
Click to expand...
Click to collapse
Ah that's interesting, didn't know that about Linux before. Well I always imagined that when there's little memory left, the drive somehow gets slowed down because there would'nt be enough space for some temp files or executions. But I don't really have a clue.
On the other hand, different devices showing different and inconclusive results like that is something I already experienced many years ago. ^^
LuH said:
If you mean on stock slot, just remember that you need to have some system installed there even in order to boot into safestrap - delete old, install new and ONLY then reboot, otherwise you're facing sbf Learned the hard way It doesn't brick your phone (meaning you can unbrick it), but it's lengthy and annoying...
Click to expand...
Click to collapse
Yeah I know, I had read about it before. But you can't really miss all those hints everywhere, so I think the community takes good care of spreading that time-saving information.
Actually thanks for encouraging me, because last night I flashed CM12.1 and everything onto the stock slot! Today I installed and configured most of the things I needed (including int/ext storage swap) and I have to say, it really runs better! It might not be as smooth as with a more recent smartphone, but it's definitely snappier than CM12 on the safe slot was (now it's gone and will rest in peace^^). It may sometimes take a few seconds, but most of the time it's very fluid, a great, noticeable improvement.
Additionally, now that I don't have to household with the memory anymore, I installed all the apps that I had left out on the safe slot install and even installed a couple of huge games from the Play Store (NFS:MW, NBA Jam, Batman Dark Knight, Injustice) onto my microSD card and it still runs almost without any hick-ups! I haven't tested the games yet, though.
EDIT: It really seems to have something to do with the amount of memory left on /system. After all that installing I was down to ~ 200MB (which would've been normal on the safe slot) and the phone started lagging a little bit more. But after moving some games and apps to the SD I have more than 500MB 600MB - okay after deleting the cache it's 1,26GB - free on /system and the phone runs smoothly again.

Shani Ace said:
EDIT: It really seems to have something to do with the amount of memory left on /system. After all that installing I was down to ~ 200MB (which would've been normal on the safe slot) and the phone started lagging a little bit more. But after moving some games and apps to the SD I have more than 500MB 600MB - okay after deleting the cache it's 1,26GB - free on /system and the phone runs smoothly again.
Click to expand...
Click to collapse
I guess you're talking about /data, not /system (different partitions, /system is usually read-only and system is installed there with stuff you flash from safestrap, everything else goes to /data or /sdcard). Yup, when /data is becoming full, you're gonna experience some strange behavior.
/data is the first "Internal storage" in Storage settings, /system is not shown there, /sdcard is the second "Internal storage" and /sdcard-ext, or "SD card", is the actual microSD in default CM12 setup. I guess you have the last two switched though.

Desire 510 on FreedomPop ... Out of Storage ... Help ... Kernel? Custom ROM?

FreedomPop now sells the HTC Desire 510. I bought it for my daughter thinking that 4GB would be enough storage for her, but when I ran my first round of app updates, the phone's storage filled up! I checked it out and there is so much bloat on the phone, that it can't be usable for a little girl who might want to install an app or game or two.
I have rooted it and tried Link2SD, but it won't auto mount an ext3 or ext4 partition on boot and therefore, the apps moved to the SD card can't be found when the phone boots.
I'm assuming the problem is with the kernel.
Ordinarily I would just put a custom ROM on a phone and be done with it, but FreedomPop uses some unique network settings that make it difficult to just replace a ROM.
My question is whether anyone has this phone on FreedomPop and what you are doing to make it into a usable phone?
Are you using a custom kernel?
If you are using a custom ROM, how did you configure the FreedomPop settings?

jeffmikels said:
FreedomPop now sells the HTC Desire 510. I bought it for my daughter thinking that 4GB would be enough storage for her, but when I ran my first round of app updates, the phone's storage filled up! I checked it out and there is so much bloat on the phone, that it can't be usable for a little girl who might want to install an app or game or two.
I have rooted it and tried Link2SD, but it won't auto mount an ext3 or ext4 partition on boot and therefore, the apps moved to the SD card can't be found when the phone boots.
I'm assuming the problem is with the kernel.
Ordinarily I would just put a custom ROM on a phone and be done with it, but FreedomPop uses some unique network settings that make it difficult to just replace a ROM.
My question is whether anyone has this phone on FreedomPop and what you are doing to make it into a usable phone?
Are you using a custom kernel?
If you are using a custom ROM, how did you configure the FreedomPop settings?
Click to expand...
Click to collapse
I'm trying to do the same thing myself. I've tried a couple of kernels. I can get the Link2SD to work but then the front camera won't work.
There are several recommendations to use Rhinestone. So I tried the latest version of that but it breaks the WIFI for me and that won't due for freedompop.
I'll keep trying but nothing works the way I would like so far.

Custom Rom
any updates?

Odin Wynd said:
any updates?
Click to expand...
Click to collapse
No. Apparently, no one has figured this out.

RaptorSense 7
From testing, RaptorSense 7 seems to be the most stable ROM
Link2SD is mostly functional. The only issue, is with the 2nd partition mount script, and thus, the linking features. This is an s-on related issue.
Move to SD works GREAT. but, there is much potential here.
The only other issue, is you must change your wireless settings to global as the preferred network, by holding down the mobile data setting until it's advanced settings pop up, and selecting global as preferred network. This is what I have read from the only other person I have found to post about testing this rom on this device. My HTC Desire 510 is not activated. So I could not test the connectivity and data first hand beyond wifi.
Everything else seems to work.
We need to figure out s-off for this device, or we are kinda stuck with just the simple features of Link2SD, and still stuck with some bloatwear, some of which are discontinued HTC Research products. At least on the Raptor Sense 7 rom..

Solution ~ It Worked for Me
First, I am very new to rooting, so I really have no idea what I'm talking about, but I had this problem yesterday, and I no longer have it.
With that in mind, I was having the same issue, and tried a ton of different random things that didn't work. I basically came to the conclusion that the issue had something to do with the kernel. Anyways, I still don't really know what a kernel is, but I read somewhere that in order to mess with settings like these, you had to flash a sprint kernel with the write protection removed.
I did this by following the instructions from the following forum:
http://forum.xda-developers.com/des...print-virgin-mobile-stock-desire-510-t2958969
At any rate, I'm pretty sure this is what did it for me (although I may have done some other things that I didn't understand / can't remember) and I hope it works for you too!
Best of luck
Edit:
By "it worked for me", I mean that Link2SD is now able to mount the ext2 partition that I created on my microSD at boot.

I'm in the same boat - does anyone have any ideas on how to make this freedompop 510 a little more useful? I don't have room to do anything. Thank you!

Is there a way to get more space in the data partition without having to use Link2SD? The big problem with this phone is the overwhelming amount of bloatware.
smuggskier99 said:
I did this by following the instructions from the following forum:
http://forum.xda-developers.com/des...print-virgin-mobile-stock-desire-510-t2958969
Click to expand...
Click to collapse
Well, I added that kernel to my phone and I noticed the phone got super hot and the wifi stopped working. After rebooting, it got stuck in an unsolvable bootloop, bricking it without being able to fix it.

Raptor Sense 1.2
I have the Sprint variant of the HTC Desire 510 and everything is working plus the phone is for the first time usable and stable. Link2SD is able to mount ext2 partitions on this phone with no problem. No success with ext3 or ext4 partitions. I used the steps found here on xda to partition the microSD Card. Have tried many ROMs with varying results. Some things would work and others would not. Have settled on Raptor Sense 1.2 until something better comes out.

That's odd. I've tried 1.2 but I can't seem to get link2sd to work, but it works fine in version 1.0

wkLeon said:
Is there a way to get more space in the data partition without having to use Link2SD? The big problem with this phone is the overwhelming amount of bloatware.
Click to expand...
Click to collapse
I've rooted the phone only to find that the data partition is too small.
Some stuff to get rid of, but it's not on the data partition so what good does it do you?
list of bloatware
http://forum.xda-developers.com/desire-510/general/bloatware-removal-list-compilation-t2960011
You can tell market apps to download on you sdcard.
http://addictiveblogs.com/how-to-move-all-android-apps-to-sd-card-without-rooting-device/
adb shell pm get-install-location
After Android Tools Update command
adb shell pm setInstallLocation 2
It does appear that you have to have enough space on your data partition before market will download app. It will then end up on your sdcard.
But the data partition still fills up. Don't know who is doing the filling.
I've been playing around with the linux redirect command to try to move some stuff to the sdcard.
see
ln -s <where to go in the future> <old place your are replacing>
work in progress for me.
& I haven't figured out how to do a backup of my system yet. Titanium backup want to backup to the data partition. Guess they want you to buy the pro version. Should just say it's a demo version.

rccharles said:
I've rooted the phone only to find that the data partition is too small.
Click to expand...
Click to collapse
phone: freedompop htc desire 510.
Actually, found out my /storage/emulated/legacy partition is giving me out of storage too. lnk2sd showed:
/data
total 1.11gb used 0.99gb free 119mg
/storage/emulated/legacy
total 1.01gb used 0.99gb free 17.88mg
/storage/ext_sd
total 3.63gbused 74.19mb free 3.56gb
The location /storage/emulated/legacy
is what I see in setting > storage [ the first instance ]
17.89mg
seems this is the problem. Seems this is contains app profile information. This storage space increases when you go into the app and clear settings or ditch the app.
Robert

How to encrypt the storage of the Nexus 6 - but not all of it?

I used encryption once, when my N6 was running LOS 14/15. But then the navigation app became very, very slooooow in loading its maps, and my podcast app also was a bit lagging sometimes. So, when I flashed LOS 16, I decided not to encrypt the storage any more.
Now I am running LOS 17.1, and I am reconsidering encryption, because 17.1 is a much newer version, it might be that encryption works faster then before. Does anyone have experience with the this and can anyone tell me, how great the loss of loading speed will be on LOS 17.1 compared to previous LOS versions?
Alternatively, can there be a non-encrypted part of the storage, for things that don't need to be encrypted anyway, like maps and music, and one encrypted part for personal data? If the N6 had a memory card slot, it would be trivial to encrypt the internal storage and leave the external card unencrypted. But given the limited and non-expendable built in storage, a partitioning could get tricky. I guess, for a start root will be needed for this. And then: how will apps behave? Not every app can be told where to save its data.
If any one can tell me any thing about this, and hint or clue or help will be most welcome!

you ever find good info on this? I have a really old LOS, (I think 14.1) and I stopped flashing updates b/c i liked it and it was pretty stable. But I have been getting a lot of crashes and poweroffs and lag recently. I'm currently also using encrypted storage which is probably slowing everything down.
But i want to keep my storage encrypted if possible, but if not I'll at least beupdated to LOS 16 or 17 soon.

birnard said:
you ever find good info on this? I have a really old LOS, (I think 14.1) and I stopped flashing updates b/c i liked it and it was pretty stable. But I have been getting a lot of crashes and poweroffs and lag recently. I'm currently also using encrypted storage which is probably slowing everything down.
But i want to keep my storage encrypted if possible, but if not I'll at least beupdated to LOS 16 or 17 soon.
Click to expand...
Click to collapse
Sudden power-off is a sign that you need a new battery.
Lag and crashes could be many things, but first thing to try is doing a complete backup, then format the data partition. That will fix possible corruption of the file system or system data.
For typical use, encryption is only marginally slower. I doubt that is your problem.
If you upgrade, then remember that encryption was changed at some point (I think it was going from Nougat to Oreo, but not totally sure). That makes it necessary to format the data partition (again, backup first) and then reencrypting. Please note the difference between wiping and formatting, wipe is not enough.
Unfortunately, TWRP hasn't been updated, so if you encrypt with a recent rom, TWRP will no longer be able to access your files.