Change Partition Layout/Size? - Nexus 7 Q&A, Help & Troubleshooting

Hello, i got the 16gb Nexus7. And i bought Tomtom Europe. When i had the officiam ROM, Tomtom could download the large (3gb) map and everything was fine.
Now i am using Cyanogenmod 10.1 and CWR. And, Tomtom says i got not enough space to download the map. I don't know where Tomtom wants to store the map, maybe on the sdcard? Is it possible to change the Partition-Layout?
Thank you!

Well, the actual sdcard space is 12.xx gigs so there's plenty of space there, resizing the partitions is possible, but risky and you have to know a lot about modifying bootloaders I don't know what other partition you would take from though,
Sent from my Nexus 7 using xda app-developers app

Yes indeed it is very strange, but with the stock ROM Tomtom does download the map and with Cyanogenmod 10.1 it complains about missing space. Is cyanogenmod using an different partition layout than the stock ROM? I would like to use Tomtom with cyanogenmod.
It is also not 10.1 related, on the Galaxy s2 with cyanogenmod 10.1 everything is ok.

-gb- said:
Yes indeed it is very strange, but with the stock ROM Tomtom does download the map and with Cyanogenmod 10.1 it complains about missing space. Is cyanogenmod using an different partition layout than the stock ROM? I would like to use Tomtom with cyanogenmod.
It is also not 10.1 related, on the Galaxy s2 with cyanogenmod 10.1 everything is ok.
Click to expand...
Click to collapse
I'm not aware of any ROMS doing re-partitioning on the N7. Somebody correct me if I am wrong, but I think that APX would need to be cracked to do this.
Check on the sizes of your CWM/TWRP backups first, and then after that just go looking for what is using your storage.
C:\ugh> adb shell
$ su
# cd /data
# du -sk *

OK i installes the official 4.2.2, then installed TomTom. TomTom got the map and then i flashed cyanogenmod, but i did not delete the userdata or so, and now i still got TomTom with the working map. Strange that downloading in cyanogenmod doesn't work. There must be enough space i know, anyways now it works for me.

I have the same issue on my Samsung Galaxy 3.
I just reinstalled CM-10.1-20130407 -NIGHTLY-i9300 and did a factory reset/wipe user data. As seen from the screenshots, I have plenty of free space (no extra SD card at the moment).
Since I have lost all my custom configuration, I am willing to test whatever is required...

I got no solution - but more CM reated problems.
My TomTom workaround was*to install the official android from google. then i installed tomtom, downloaded the map and flashed CM without wiping the map from the storage. you could also perhaps copy the map from storage to your computer and later under CM copy it back.
the new problem is google wallet. under CM 9 in used to pay apps in the play store via googe wallet and my mobile data plan from Fonic in Germany (where i live). No under CM 10.1 payment and google wallet is not working which is really bad ... but i will eventually buy a cheap phone just to buy things^^ or wait for the voucher-cards in germany.

Yesterday's Tomtom update finally fixed my issue :good:

Thanks for the info! Works for me too, now.

Related

Google Talk missing.....

OK, so I am trying to get GTalk back installed after flashing a new ROM (Cyanogen 4.2.15).
I have searched and there seems to be no direct answer, possibly some inferred ones but noone has been able to answer or point me in the right direction. Hell, I got nicely ignored on Cyanogen's IRC channel. So, unless you are some sort of developer, that' a pretty useless avenue to ask questions it seems.
Here's the scoop:
I reflashed the CM ROM after properly preparing my SD card to make use of Apps2SD option. Gmail works, GMaps works, no GTalk.
Yes I am aware that the Google Apps had to be separated from CMs ROM but that seems only partially true as the other apps are all there.
Since there is a link to the suite of GApps (http://kanged.net/mirror/download.php?file=gapps-ds-ERE36B-signed.zip) does anyone know if one can simply 'apply any zip' and get the GTalk functionality back? I don't care if I have to resign into Google/Gmail again, just want GTalk to work.
Phone Info:
HTC Dream/G1
Firmware 1.6
Radio 2.22.19.26i
CyanogenMod 4.2.15.1
Nandroid
Stock CM theme
8GB Class 4 MicroSD car (partitioned 4GB/4GB....yeah, it's goo big of an app partition, toying with resizing it instead of blowing it all away.)
JadedTech said:
OK, so I am trying to get GTalk back installed after flashing a new ROM (Cyanogen 4.2.15).
I have searched and there seems to be no direct answer, possibly some inferred ones but noone has been able to answer or point me in the right direction. Hell, I got nicely ignored on Cyanogen's IRC channel. So, unless you are some sort of developer, that' a pretty useless avenue to ask questions it seems.
Here's the scoop:
I reflashed the CM ROM after properly preparing my SD card to make use of Apps2SD option. Gmail works, GMaps works, no GTalk.
Yes I am aware that the Google Apps had to be separated from CMs ROM but that seems only partially true as the other apps are all there.
Since there is a link to the suite of GApps (http://kanged.net/mirror/download.php?file=gapps-ds-ERE36B-signed.zip) does anyone know if one can simply 'apply any zip' and get the GTalk functionality back? I don't care if I have to resign into Google/Gmail again, just want GTalk to work.
Phone Info:
HTC Dream/G1
Firmware 1.6
Radio 2.22.19.26i
CyanogenMod 4.2.15.1
Nandroid
Stock CM theme
8GB Class 4 MicroSD car (partitioned 4GB/4GB....yeah, it's goo big of an app partition, toying with resizing it instead of blowing it all away.)
Click to expand...
Click to collapse
you should be able to flash gapps and get it back but you can unzip that and grab gtalk and push it back using adb
supremeteam256 said:
you should be able to flash gapps and get it back but you can unzip that and grab gtalk and push it back using adb
Click to expand...
Click to collapse
When you say 'push' to you mean 'adb push' or 'adb install'. Just wanted to be clear as the install doesn't work.
"Failure [INSTALL_FAILED_OLDER_SDK]"
I get that when I tried to install. My understanding is that there is a mis-match in the adb I am using and the ROM that is on the phone. Is there a way to fix this?
If you are only using CM4 then you need to wipe, defanged base (all of the google apps), then flash CM4.
You shouldn't be flashing gapps. That is for CM5
-------------------------------------
Sent via the XDA Tapatalk App
Oh yeah dont flash gapps. That is for CM5.
-------------------------------------
Sent via the XDA Tapatalk App
And so my learning continues....
So, by copying the zip file to the SD card and choosing 'apply any zip', it seems that everyone is calling that 'flashing'?
Now here's the issue. I already flashed CM 4.2.15.1 and there was no GTalk included.
FYI, for people like me learning, a little more explanation goes a long way. Good thing I'm one of those types who knows how to use Google as opposed to the types who get pissed by people who just use terms and assumes everyone knows them....
So through my wanderings I found this link:
http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_G1/Dream_Firmware_to_CyanogenMod
Which led me to here
http://wiki.cyanogenmod.com/index.php/DangerSPL_and_CM_5_for_Dream
Just did a nandroid backup, about to copy stuff from SD card and then upgrade to CM 5/Gapps!
Wsh me luck!
SUCCESS! CM 5.0.7 installed!!
And GTalk works
Thanks all involved with making these things possible!

[Q] After update to CM 7 cant access market and WIFI

i have installed CyanogenMod 7 V7.1.0 from thread [forum.xda-developers.com/showthread.php?t=1297776] and installed google apps and video addon as well but now i cant see the market and cant login to google account also i cant download market through a browser as well
EDIT: i tried to download other apps through browser but failed
second issue which i am facing is that now i can not connect to my WIFI network. it get connected for a sec. and disconnects where as i was able to connect when using official froyo 2.2
please guide me as its my first time dealing with ROM's
Sorry I can't help you with ur market but to fix ur wifi get dis app "Blade wifi fix".it worked for me n its worth a try. Please let me know if it worked.
Sent from my Blade using xda premium
Reinstall CM7 & google apps & wipe data/factory reset in clockworkmod to fix your market issues. You want the version of google apps without the google talk video chat addon - that wont work on our blades - gb-20110828-signed.zip
This should fix your wifi: http://forum.xda-developers.com/showpost.php?p=21956461&postcount=88
i tried the exact method and downloaded the zip files again but i still cant see market installed also cant use wifi with the fix
Didn't the app work??
Sent from my Blade using xda premium
every thing is working except WIFI and market then i tried reverse tethering to access internet through PC and tried to download some thing from market but failed
infact i cant login to gmail account through gtalk app on the phone but i can do so with browser
Wipe data/factory reset in clockworkmod, then go into the mounts and storage menu & format /system then install cm7 then install gapps.
Formatting /system should do it (but you'll still have to wipe data & reinstall cm7).
It could be something hanging around from your old rom, I think the CM7 install script tries to keep some google apps, but if they're some old version it's no good.
Your market icon wont appear until you log in to your phone in to your google account, you can do that in the setup wizard which will appear after you wipe & reinstall.
Another possibility is that you've got a small system partition (under 145mb) & there isn't enough room for all the rom to be installed, the wifi driver is one of the last things to copy. Clockworkmod doesn't show any errors when it runs out of space.
thanks for support much appreciated but i have installed GSF mod and its working absolutely fine
sooner or later i will try again and will give the feedback accordingly
P.S. i have around 2.5GB free space so no point about space unavailability
kartikoli said:
thanks for support much appreciated but i have installed GSF mod and its working absolutely fine
sooner or later i will try again and will give the feedback accordingly
P.S. i have around 2.5GB free space so no point about space unavailability
Click to expand...
Click to collapse
Your phone only has 512mb of internal memory & that is partitioned. The rom is stored on the /system partition. If there isn't enough room on your /system partition then it doesn't matter what free space you've got elsewhere.
If you didn't change the size of your system partition then it wont be a problem, it starts off as 210mb & cyanogen just needs about 140mb. Some people change their system partition size to be 128mb or even less, to give them more room for their data, but it's no good for larger roms like Cyanogen.

[Q] Strange issues with my storage...?

Hi all, first time asking a question on Nexus 4
Days ago I decided to upgrade CM10.2 from an earlier nightly (build number JSS15Q) to a newer one (JLS36C), so I dirty flashed and everything seemed fine at first, but:
1) When I connect my N4 to the PC, it links up in MTD mode, I can read, copy, rename and delete contents from it, but I just can't put anything into it. It says something like "device is offline or has stopped responding". I thought it was a random issue so I ignored it.
2) One day later, a nightly with build number JLS36G dropped, and I want to back up my data with Titanium Backup before I do a clean flash. I knew previously that to use TiBu on 4.3, the backup folder has to be manually changed, and this worked for me before. This time, however, even after changing folders, TiBu still reported "insufficient backup space" no matter what I do.
3) Yesterday I wanted to upgrade some softwares on the phone, but many installs fail with "out of space" alert, while I confirmed that I have plenty (5GB+) internal storage left.
4) And today I am using Root Explorer to manage files. I just want to move a file to another folder. I created the folder with success, but pasting operation failed, still because of "not enough space". The same happens for CM's File Manager.
Now I'm out of ideas. The best bet is to start over from a clean flash, but since TiBu is unusable, I will lose all my SMS/call log, which I can't swallow. I'd be very grateful if anyone can tell me what's behind all these issues, or/and can teach me how to back up SMS/call log with a file manager. Thanks in advance
***EDIT***: I figured out how to manually backup/restore my SMS/call log, and went on to do a clean install, but even after a clean install, Root Explorer still reports insufficient free space. I can install softwares normally, though.
Sent from Google Nexus 4 @ CM10.2
are you sure you have 5GB storage left or available?
Sent from my Nexus 4 using Tapatalk 4
Indian9990 said:
are you sure you have 5GB storage left or available?
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
I'm pretty sure of that. I have 7.6GB files on the phone (calculated by copying all files out and checking their size using Windows), so free space should reasonably be 5GB. All softwares on the phone report this value too.
Sent from Google Nexus 4 @ CM10.2
Uhh, anyone? This sinks so fast
Sent from Google Nexus 4 @ CM10.2
Exactly what method did you use to 'clean install' ?
tarroyo said:
Exactly what method did you use to 'clean install' ?
Click to expand...
Click to collapse
Wipe cache, dalvik, data, system (yeah I'm not that noob-ish to forget this), and install the downloaded package. I didn't install any mods after that. Clean enough, I guess.
Sent from Google Nexus 4 @ CM10.2
An update to this situation: I think that using a factory image I might be able to "clear" the partitions and hoprfully revive my storage, but when I tried to back up all my contents in storage to PC using MTP connection, it got stuck at "calculating time needed for copying files" or sth like that. I have ~3GB of (unsynced, of course - I'm in China) music and some precious data I don't wanna lose, and at this size I couldn't back them up on the clouds. What to do now?

My kindle fire HDX 7" setup, for newbies!

First of all, thanks a lot to Cpasjuste for making the working gapps flashble zip, here's a link to that. I take no responsibility for doing this, all credit goes to Cpasjuste. Also I do not know a lot about deving myself but i've had two android devices before this and have been avid in modding them, just thought i'd put that out there.
So, first thing I did was get root, factory reset and get safestrap recovery. then I made a backup of my stock ROM, kept it on my kindle, and moved it to a safe spot in my computer (I recommend everyone does this, no matter if they choose to follow this setup or not.) I created a new ROM slot with default partitions, and restored my stock ROM to it (you do this in case any thing happens you have your stock ROM to fall back on). I tried flashing Cpasjuste's gapps rom, but for some reason there were multiple issues with it so instead, i restored to stock, on ROM slot 1, and flashed his gapps zip mentioned earlier. Rebooted and everything (well almost everything) worked perfectly. playstore works and only app that I have discovered to be incompatible is instagram for some reason, but i found a apk download online that installed perfectly to replace it. I installed a app from play store called recent apps quick button, which basically activates android's recent apps, then I installed a app from play store called Home2 shortcut. this lets me assign the resent apps quick button to double tapping the home button so now when i double tap the home button it brings me to recent apps. It's really nice since kindles default Rom doesn't have a recent apps button! Right now I am working on blocking updates from amazon to prevent losing root or bricking, using the tutorial found at the end of the root link. Let me know what you guys have done to make your kindle fire HDX experince better, or any questions you have.
Also, I forgot to mention that using the gapps flashable zip broke my amazon appstore and most amazon services, except video it seams like, but since we have safestrap recovery this isn't a big deal to me because i can always get it back, and im sure it will be fixed in future. Have fun and be safe while experimenting with your kindle.
I TAKE NO RESPONSIBILITY FOR DAMAGE DONE TO YOUR DEVICE, KNOW WHAT YOUR DOING BEFORE YOU DO IT!!!!!!!
Ah! Thats what I missed, I didnt realise I could use restore on a different ROM slot! Thanks for that, going to try it later!:good:
OurFriendIrony said:
Ah! Thats what I missed, I didnt realise I could use restore on a different ROM slot! Thanks for that, going to try it later!:good:
Click to expand...
Click to collapse
No problem! Also if I were you I would delete most of the user apps on your stock ROM, Idk if you did what I said and factory reset before you got safestrap (I would not try it if you already safestrap since you will lose safestrap and possible break you device!) but if you didnt I would just go back and delete most user apps and data off stock ROM and then redo the backup and restore with that. because you most likely wont be using the stock ROM (you don't want to alter it since you want to have a safe spot to restore to) you want it to take up as little storage as possible. My advice, pretend that you don't have root and don't do anything with it, like editing parts of system, or flashing mod packages, etc... (only exception is having super user and safe strap app installed.) Let me know if any part of this was to confusing. Hope this helped!
Haha, I saw your reply about 2 minutes after starting up the factory rest. I can, however, confirm that safestrap is still installed between the boot and IS load, so I'm actually in a perfect position. Have taken a new backup of pure stock rom!
Happy days!
I got a copy of my Stock ROM installed into ROM slot 1 and then added the gapps package, it worked beautifully!
I now have a tablet with all the google features on and have no issues so far.
except...
when I boot to ROM slot 1, I get a message saying "Kindle is Updating/Upgrading". It doesn't do anything and it only takes a few seconds before it gives up. I was just wondering if there was a way of getting rid of this??
As someone who hasn't had any prior experience with Android (although a fair share of experience with GNU/Linux), I appreciate a thread like this.
I also rooted the device (works well from GNU/Linux), installed SuperSU and some essential apps to make the stock OS usable (busybox and a terminal emulator, of course; and also a lightweight file browser that doesn't take much space and does exactly that, lets me browse local files). Then installed SafeStrap and backed everything up to both the Kindle and the PC (the backup is accessible via MTP, in the internal storage, so you can just connect the USB cable and copy the TWRP directory – at least in KDE).
Now I'm going to try the new AOSP ROM. Though since I'm new to the whole Android business, the partition sizes have me a bit confused. I'd want to have three slots – the stock ROM (obviously), the stock FireOS (one that I can modify) and AOSP. What partition sizes for the two slots would be the best, if it's the 16GB HDX? Also, say I download a PDF file; would both FireOS and AOSP see the file if I put it in internal storage, or would I have to manually copy it over to the other slot through my PC?
@GreatEmerald, whats AOSP? I'm thinking of playing around a bit more. I want to try out some more ROMs.
I put my first ROM slot (Stock with gapps added and amazon crap removed) on Flight Mode and now when I try and put it on wireless it restarts....
OurFriendIrony said:
@GreatEmerald, whats AOSP? I'm thinking of playing around a bit more. I want to try out some more ROMs.
I put my first ROM slot (Stock with gapps added and amazon crap removed) on Flight Mode and now when I try and put it on wireless it restarts....
Click to expand...
Click to collapse
AOSP = Android Open Source Project
Many other devices have an AOSP build and is typically a very nice build to flash if you like the core android feel with some extra very nice features.
OurFriendIrony said:
@GreatEmerald, whats AOSP? I'm thinking of playing around a bit more. I want to try out some more ROMs.
I put my first ROM slot (Stock with gapps added and amazon crap removed) on Flight Mode and now when I try and put it on wireless it restarts....
Click to expand...
Click to collapse
Yea, as mentioned, AOSP is a ROM for stock Android 4.2.2, pretty much the only big ROM available for the HDX7 right now: http://forum.xda-developers.com/showthread.php?t=2607185
It works pretty well as it is, I'm impressed it's as good already given how new the project is. Though it still has some issues for normal use. Aside from the bugs mentioned in the post, Chrome crashes as soon as it's launched (but you can use Firefox instead), as does the Kindle app (which is mainly what is stopping me from using it, because the point of a Kindle is the integration with Amazon services...). Also, the Facebook app fails to install for some reason.
Everything else I tried works fine. I installed F-Droid, a file manager, Busybox and a terminal, then the Amazon app and some of the Amazon cloud apps, and finally Skype. All of them work very nicely on AOSP. Even tested a video call on Skype and it worked without any problems (including the camera working correctly).
As someone new to Android and from a GNU/Linux background, I'm really happy that F-Droid exists. It's an app store/package manager that offers only free and open source software. For regular users that might sound as not a big deal, but actually filtering software by license is more powerful than one would think. You're guaranteed to have only apps that have no spyware and adware, because you can't hide them in open code. And those who make apps without publishing their code obviously have something to hide. So much like in GNU/Linux, the first place to check for new apps for me is F-Droid, and after that the main store of the OS (be it Google Play or Amazon Store), and only then 1Mobile market.
I still would like to know more about that partitioning, though. I figured out that the emulated SD card is shared between ROMs (I uploaded F-Droid to the Downloads directory on FireOS, and could see it on AOSP just as well), but I still don't know what exactly the two partitions you have to make to set up a ROM slot are and how much space should be allocated to them.
GreatEmerald said:
Yea, as mentioned, AOSP is a ROM for stock Android 4.2.2, pretty much the only big ROM available for the HDX7 right now: http://forum.xda-developers.com/showthread.php?t=2607185
It works pretty well as it is, I'm impressed it's as good already given how new the project is. Though it still has some issues for normal use. Aside from the bugs mentioned in the post, Chrome crashes as soon as it's launched (but you can use Firefox instead), as does the Kindle app (which is mainly what is stopping me from using it, because the point of a Kindle is the integration with Amazon services...). Also, the Facebook app fails to install for some reason.
Everything else I tried works fine. I installed F-Droid, a file manager, Busybox and a terminal, then the Amazon app and some of the Amazon cloud apps, and finally Skype. All of them work very nicely on AOSP. Even tested a video call on Skype and it worked without any problems (including the camera working correctly).
As someone new to Android and from a GNU/Linux background, I'm really happy that F-Droid exists. It's an app store/package manager that offers only free and open source software. For regular users that might sound as not a big deal, but actually filtering software by license is more powerful than one would think. You're guaranteed to have only apps that have no spyware and adware, because you can't hide them in open code. And those who make apps without publishing their code obviously have something to hide. So much like in GNU/Linux, the first place to check for new apps for me is F-Droid, and after that the main store of the OS (be it Google Play or Amazon Store), and only then 1Mobile market.
I still would like to know more about that partitioning, though. I figured out that the emulated SD card is shared between ROMs (I uploaded F-Droid to the Downloads directory on FireOS, and could see it on AOSP just as well), but I still don't know what exactly the two partitions you have to make to set up a ROM slot are and how much space should be allocated to them.
Click to expand...
Click to collapse
The system partition only needs to be as big as the Rom or backup you flash is, the data partition I typically make as big as possible (4000 mb) since this is what your Rom will consider internal storage. This is where apps and app data will be downloaded onto, where the rest of the data on your ad card is shared and is used for music, videos and lots of other custom stuff you can add. As for the cache I leave it at the default, this is where temporary data for apps is stored ( for example when you play a youtube video, it is temporarily stored on this partition.
spaghettiknight said:
The system partition only needs to be as big as the Rom or backup you flash is, the data partition I typically make as big as possible (4000 mb) since this is what your Rom will consider internal storage. This is where apps and app data will be downloaded onto, where the rest of the data on your ad card is shared and is used for music, videos and lots of other custom stuff you can add. As for the cache I leave it at the default, this is where temporary data for apps is stored ( for example when you play a youtube video, it is temporarily stored on this partition.
Click to expand...
Click to collapse
Ah, that's good to know. It makes me wonder, though – can I resize partitions in some way? Say, I created a smallish partition setup for ROM slot 1, then another one for ROM slot 2, and then have a bit spare; can I allocate the whole space to ROM slot 1 if I no longer need ROM slot 2? Or to do a backup, clear the partition setup, then restore the backup into newly sized partitions?
GreatEmerald said:
Ah, that's good to know. It makes me wonder, though – can I resize partitions in some way? Say, I created a smallish partition setup for ROM slot 1, then another one for ROM slot 2, and then have a bit spare; can I allocate the whole space to ROM slot 1 if I no longer need ROM slot 2? Or to do a backup, clear the partition setup, then restore the backup into newly sized partitions?
Click to expand...
Click to collapse
yes, what i would do is backup my current setup, delete the rom slot your using, then remake it with your newly picked partitions
Nevermind. Got it working now. Thanks for the guide!
safestrap not working on my kindle hdx 7"
Hi my kindle is already rooted and I used towelroot. I have supersu installed too. I'm currently on the step of where I should install safestrap, but it seems safestrap is not working on my tablet. I tried 3.65, 3.72, 3.75 version of safestrap but it does not work. It always restart normally. Not in recovery. Pls help. 13.3.2.8 version. Thank u in advance.
pinksummer17 said:
Hi my kindle is already rooted and I used towelroot. I have supersu installed too. I'm currently on the step of where I should install safestrap, but it seems safestrap is not working on my tablet. I tried 3.65, 3.72, 3.75 version of safestrap but it does not work. It always restart normally. Not in recovery. Pls help. 13.3.2.8 version. Thank u in advance.
Click to expand...
Click to collapse
Have you blocked OTA with HDX Toolkit? If not your device will likely brick if Amazon attempts to push an update. At present the blocker in HDX toolkit is the only one that works on 3.2.8.
Your attention should be focused on this task; can deal with safestrap once OTA block is in place.
ya I had to learn about that the hard way

[ROM] [N1] Evervolv KitKat+

I just want to share my notes and links about successful experience of the Evervolv KitKat 4.4 ROM installation on a Nexus One device.
Developer's thread is here: http://forum.xda-developers.com/showthread.php?t=2540366
1. I installed BlackRose Bootloader (see link in the first post of the dev thread) and partitioned my SD to have sd-ext Ext4 partition. Actually, I don't use it yet, because it looks like forced moving of apps to SD (or other "cheating") is not reliable, see e.g. here (about similar ROM): http://forum.xda-developers.com/showthread.php?t=2573352
2. Installed TWRP, getting info here: http://teamw.in/project/twrp2/51
"Direct download" lead me to some spam so I used "Recovery Image Method" to install the Recovery.
3. Resized System partition using BlackRose.
After several not very successful attempts to install both Evervolv ROM and GApps I ended with System partition size = 240 Mbytes, and Cache = 10 Mb (I didn't play with changing Cache...)
4. Using Recovery I installed the two zip files:
4.1. The latest Evervolv ROM from here: http://evervolv.com/devices/passion ( ev_passion-nightly-2014.07.16-squished.zip )
4.2. "GApps Minimal 4.4.4" which is 23Mbytes in size using link from this page: http://forum.xda-developers.com/google-nexus-5/themes-apps/standard-minimal-gapps-t2012857
The two ZIPs currently occupy about 231MBytes in /system (check this using "df" command in the stock "Terminal emulator" application)
5. Of course I extensively did "Wipes" before and after any changes, for a case...
6. Having "Play Store" app in the system, I was able to install several other Google apps: Calendar, GMail, Keep...
Result: I'm pretty happy to have my old Nexus One as a temporary replacement for my lost Galaxy S3. I'm even thinking of buying smaller (than Galaxy S3) phone next time
Performance is quite acceptable so far. Will report later on the experience...
The flight is normal
After two weeks of usage I would say that the new firmware is really usable in a simple "phone-email mode" and I'm happy with the move:
- The performance is mostly acceptable for these my everyday applications, which I installed: Dialer, GMail, Calendar, ColorDict, Pocket, AndStatus, Total Commander, Yandex Maps, Google Keep, Tasker, Volume locker ...
- No unexpected reboots so far. Sometimes I encountered freezes, but occasionally this occurs on my new Galaxy Tab Pro also, so I don't blame the firmware build here...
- I successfully upgraded to the newer nightly build, reflashing system + the same minimal Google apps.
Of course, old hardware cannot fully replace a new one , so:
- There was no memory to install Chrome, Dropbox and WhatsApp (I guess they require too much RAM...)
- "2048" game lags noticeably
yvolk said:
Of course, old hardware cannot fully replace a new one , so:
- There was no memory to install Chrome, Dropbox and WhatsApp (I guess they require too much RAM...)
Click to expand...
Click to collapse
Do you use memory tools like Mounts2SD or Link2SD? I use Opera, Dropbox, WhatsApp and many other apps with no problems on my N1 with KitKat :good:
Although Google Maps lags much more than the old version on Gingerbread but that's not the ROM's fault.
239 said:
Do you use memory tools like Mounts2SD or Link2SD? I use Opera, Dropbox, WhatsApp and many other apps with no problems on my N1 with KitKat :good:
Although Google Maps lags much more than the old version on Gingerbread but that's not the ROM's fault.
Click to expand...
Click to collapse
At first install of the rom, I tried Mounts2SD. The rom was slow and unstable. So I reinstalled the rom and used the builtin Apps2sd with y/y/n (apps and dalvik-cache mounted on sd-ext). Works fine as daily driver.

Categories

Resources