Related
Please Read Everything Carefully as some info is crucial to getting your old phone functioning well!
Update:::: August 16, 2015 ::::::::::
STAGEFRIGHT BUG:
This bug has been blown way out of proportion and it is not something anyone should be extremely worried about. There are no patches for gingerbread as of yet, and I cannot patch it since I do not have the CM source. However, you can copy from /system/build.prop and open the file in Notepad++ and then search for "stage" and change the "true" to "false" -without quotes. While this is not a fix, it will still offer some protection. Do not download apk files from places you do not trust and you should be ok. For now you can also do the following :
1) In MMS App, Turn off Auto-Retrieve. If your Carrier converts your voice mails to text, you will no longer be getting those. The app will then provide a download button for you to download the message instead. You can simply call your voice mail and listen to the message and download it if you think its important.
2) Remove the stock browser - do not use it to sign into anything.
3) Use Firefox as your default browser. It will be slower but safer. Type about:config > Search for Stagefright > Set stagefright.disabled to True
4) FIREWALL : Use AFWall+ to block Apps making unneeded connections to places you don't trust. It starts in Whitelist mode. Change it Blacklist mode. Be careful, and understand how to use this. LINK https://play.google.com/store/apps/details?id=dev.ukanth.ufirewall&hl=en
6) In an effort to save RAM and unnecessary background Operation, I have included ForceStop Prevent Running. Do not update this past version 0.15. Updates after this do not work well on Gingerbread. Preventing Google Play Store is ok, Play Services is optional (You will lose all sync except Contacts and Calendar but no unnecessary background syncing.[/I]
7) GApps package now Included. It is Stock Gingerbread Gapps with Google Play Store updated to version 5.1.11. Please note that the latest Google Play Store works Fine but it is slower. If you want to block it from Updating, BEFORE connecting to Wifi, IF the APK is called com.android.vending.apk THEN create a new directory in /data/app called com.android.vending-1.apk, so it is always 1 number higher than what is installed. Also, if you do Update, MOVE the update to System parition or you will have 2 copies of it. Then delete its Dalvik cache and reboot
Update :::: June 18, 2015 ::::::::::::::New Goody : Added Modded K9-Email for Gingerbread to list of Software - It is open source, and a good way to check "Hotmail/Outlook" using Imap. Imap functions in Outlook are limited but the program works. I have removed the Ugly K9 dog Icon and replaced it with a real Email icon to make it look more appealing
Updated ::: June 12, 2015 ::::::::::::: New Goody : Attached Adaway for Gingerbread - Disclaimer: I support ads in some apps that do so reasonably, but some apps are out of control with Permissions and blowing up your screen with constant Ads, this behavior is unacceptable so I have included AdAway here. It is the user's Right and choice to do as they please on a carrier/contract free ROM, however it is not my responsibility what you may do with this ROM. This ROM still contains most of the original components of the Original ROM and I may remove outdated functions or add new functions in the future
This is MIUI 2.3.30 Gingerbread version 2.3.7 U.S. English Rom
I have now added various changes to this ROM. No more Security Certificate issues. No more Email / IMAP issues -K9 Mail, Exchange and Google accounts should sync without issues now
Xposed For Gingerbread + Prevent Running + Security Fixes are now attached below for convenience
Partitioning your SDCard is absolutely recommended or you will not have enough Internal Space to have Google Apps - Internal Space should only store Dalvik Cache - Please see details
1) 30 Step Headset Volume Configuration - works great with Volume Limiter
2) Security Certificates updated. Bad and Outdated ones Removed. see GuardianProject. This ROM is more secure. I also highly recommend using Firefox and OperaMini. I have also attached CACERTS.BKS - Remove the .TXT Extension - Already included in the ROM but can be used in other Gingerbread devices!
3) Nexus Pie boot animation
4) Misc changes - Gps locks fast when using GPS apps like Mapfactor Navigator, CPU Sleep works during trackball wake/notify feature, country codes in dialer corrected, Correct APN and Carrier name will show.
Recommended Software
I recommend you download this: Volume Limiter by Captain Neoguri - March 26, 2014
Caution: Nexus One hardware has a bug where upon using this app when adjusting volume outputs in max volume which can be dangerous for your ears, Please do not wear your headset when doing volume adjustments. I recommend a volume of upto 16 in this app for headset max volume.
Recommended : Xposed Framework for Gingerbread :::::: Download Below
Once you install it, Update it, and Install the Following :
1) Fake ID Fix
2) Master Key Multi Fix
3) MasterKeyFix GB
These are all Security Patches for Gingerbread. I have taken the Courtesy to attach them in this thread.
I recommend Google Play Store no later than 5.1.11 as the latest versions seem to have some kind of DPI related bug and will Force close constantly. Google Play Services can however be updated to 7.5.73-034 - I have tested it and it is working perfectly fine
Launcher : I am now recommending Holo Launcher from the Playstore. It saves RAM and it is much more Functional than the Stock launcher. When I have time, I will entirely remove the Stock Launcher and put Holo Launcher in the ROM or until I get permission from its author
Call Blocking Call blocking feature is built into the ROM, however it is like most call blockers which simply hide the blocked call but it still goes through. A solution to this is to use this app. Root Call Blocker : https://play.google.com/store/apps/details?id=fahrbot.apps.rootcallblocker.beta&hl=en
It will take about 5 minutes to set up and will allow you to kill a call after 1 ring and it will not go into your voice mail. So the Spam caller will have no idea whether its a dead number or to even bother calling back. Usually "Dead Rings" make the automated telemarketing calls stop because the computer dialer that is making the call keeps getting dead air and it keeps showing in their call logs. So it becomes their problem, you will simply never see the call coming until 1 day you decide to go in your blocker's call log. So if you have a pesky caller, use this app.
Radio / Baseband Software
http://wiki.cyanogenmod.org/w/Passion_Info
If your 3G does not work, Please check your 3G Network's supported Frequency with your Nexus One 3G Supported Frequency. There were 2 models of this phone released in Canada. This is not due to MIUI and downloading any Radio software will NOT fix this because it is by design.
You need version 5.08.00.04 if you are not using a Korean Nexus One. Download it, then Extract the Radio.img file from the zip.
1) You need to have ADB Fastboot and ADB Enabled on your phone. You can download a small ADB Version here.
http://forum.xda-developers.com/showthread.php?t=2588979
There are also other places to get ADB, But just know there is no need to download Gigantic SDK Kit from Google. You only need the basic ADB with Fastboot.
2) Press Volume Down, Then Press Power and Start your phone in Bootloader Mode. Then select Fastboot. Make sure your phone is now in Fastboot mode, it should say it at the top of all the choices.
3) Go to where you ADB folder is and hit Shift + Right Click = Open Command Window Here.
4) Now Plug your USB cable into your phone and type in Command Prompt this - fastboot devices. You should see your Phone listed. If you do not, go back and check everything.
5) Copy that Radio.img file from the Zip you extracted into your ADB Folder and then type
fastboot flash radio radio.img
It should take about 30 seconds.
Use the instructions here http://forum.xda-developers.com/showthread.php?t=698721 to push it to your phone.
Now you are done.
How To Increase Internal Storage using Data2SD. This puts Apps(apk) AND Data onto your SD EXT Partition so you have more free Internal memory on the internal /Data partition
MIUI comes with something called A2SD+ which is turned off by Default.
1) Go into TWRP Recovery. Create EXT-4 Partition. You will lose all data, so before doing this, its a good idea to backup.
Create an EXT partition size you are comfortable with and depending on your needs.
2) SWAP SPACE 0. You do not need it.
When it is done. Your SD Card now has a FAT partition and an EXT Partition. You can reformat your FAT to FAT32 in Windows if you would like and give it a name.
Then get this Script. MAKE SURE YOU READ EVERYTHING in the Following Threads.
This is Ungaze Data2SD Script. Script is now Attached at the bottom of this post
http://forum.xda-developers.com/showthread.php?t=1378568
http://forum.xda-developers.com/showthread.php?t=1661892
Get the Data2SD Script and copy it to your SDCard FAT32 partition. Reboot your phone a couple times after flashing MIUI. Wipe Dalvik, Wipe Cache, Then Flash Ungaze D2SD from Recovery.
Follow directions in those threads and you should see an increase in Internal Storage Space in MIUI
You can delete the Contents of /mnt/asec/d2sd/data/app/* and /mnt/asec/d2sd/data/data/* from your Device Root which is "/" after this otherwise you will have 2 copies of the same app. You should only have Dalvik-Cache in this location as it links to your Internal Memory Data partition. Make a backup first to your SD Card incase something goes wrong by copying those APKs, then simply Delete them. Your Device System Partition will have System Apps, Data partition will have Dalvik Cache and your SD Card's EXT Partition will have the rest of the Apps and their Data.
ETC INFO
You will Need ROOT Access for almost everything if you want to make changes so make sure you have SuperUser Access Turned ON in MIUI.
Search for ADAWAY which creates a HOSTS file in your /System/etc Directory, which helps to block ads. I prefer using only open source apps or apps with Ads that do not Annoy.
Use ES File Explorer
And now you can install (or Uninstall) all the Pesky large size Google Apps. I personally stay away from ANY Google App I do not absolutely Need. I remove apps like
Google Search
Google Talk (Hangouts)
and Other Google crap.
MIUI has the basics of what you need. But you can Remove the MIUI Accounts etc because you won't be needing it.
And Anything Pesky that I cannot trust. Make sure you Backup in Recovery first before Uninstalling System Apps.
You can use an app called Disable Service from the PlayStore to disable Individual Services in an app incase you don't want certain services loading up. This should help conserve memory and cpu cycles if needed and also to disable functionalities in Apps that are otherwise impossible to disable. Link Below
https://play.google.com/store/apps/details?id=cn.wq.disableservice&hl=en
The idea is to keep it SIMPLE and functional.
Last but not least, Thanks to everyone at XDA for making things like this possible. Without this community, we would not be able to do the things we can to bring enjoyment and functionality to our devices. Thanks to everyone who finds a solution and posts it with details for everyone to understand. I hope this culture keeps growing stronger.
Don't forget to say Thanks
That's it Folks! Bring out your old Nexus One. It will be fast, and serve its purpose as a phone first. And YES, Even your mom will now be able to use it. Enjoy!
ROM DOWNLOAD:
Download MIUI-Android-2.3.30-Gingerbread-NexusOne
Thanks for your time and for sharing this with us... Maybe some of us knows these stuff but in the KK 4.4.4 era, there always is someone who want to use the Sexy Nexy as a fully functional phone and use an eye candy ROM and more user friendly than CM 7.2.
For recovery I recommend 4Ext Recovery
Regards!
Obsy said:
Thanks for your time and for sharing this with us... Maybe some of us knows these stuff but in the KK 4.4.4 era, there always is someone who want to use the Sexy Nexy as a fully functional phone and use an eye candy ROM and more user friendly than CM 7.2.
For recovery I recommend 4Ext Recovery
Regards!
Click to expand...
Click to collapse
Hey, no problem! Yes 4Ext is a good recovery if you are on Blackrose and change your hboot partitions etc. My Guide is for those who don't want to mess with that and the TWRP Recovery is working flawless. I will mess around with Blackrose to increase internal Memory because one thing I find after bootloader unlock is the initial boot process is what takes the longest! MIUI Itself boots in less than half the time it takes for the intial boot. (Nexus X multi colored Logo with gray colored open lock at the bottom)
I am still not quite sure if the trouble of using Blackrose just to cut down my Cache partition to 50mb is worth the time and trouble because the phone is running fine. And I am also not sure if Blackrose will work with twrp. I will need to read more on this.
Thanks.
I completely agree with this OP. This is best rom you can use on the nexus one, I've played around with all sorts of roms and versions including the most recent KitKat iterations and non of them are smooth in comparison with a solid gingerbread rom. But this rom is particularly good because it still makes the Nexus One feel fresh.
daaac said:
I completely agree with this OP. This is best rom you can use on the nexus one, I've played around with all sorts of roms and versions including the most recent KitKat iterations and non of them are smooth in comparison with a solid gingerbread rom. But this rom is particularly good because it still makes the Nexus One feel fresh.
Click to expand...
Click to collapse
Thanks Daaac, you are right. When I pull out this old Phone, people ask me where did I get it? And how nice it looks. When I tell them its over 4 years old, they seem surprised. What google still does not seem to realize is that when it comes to Phones, people look at both the Phone hardware AND its Software that's running on it. Android is terribly ugly and MIUI is the closest you can get to getting some kind of Organized option structure even though it lacks some power user features, it is still better than scrolling through endless Cyanogenmod Gingerbread options. Not the fault of Cyanogenmod, but I blame Google for the terrible User Interface of Android. Google seems to hire Amateurs to design their User Interface and then market it as Simplicity. In my opinion, Apple runs circles around Android when it comes to Fluidity but ofcourse we know why we stick to Android, for things an iOs user can only dream of, specially on older devices. This MIUI ROM comes closest to make your Nexus One a daily usable phone with very few annoyances, however it is stable, never crashes, and looks good.
Thanks for your guide, very nice to read your step by step, good as I didn't update nexus one since 1 year ago and I don't remember all steps.
Thanks!!
You are most certainly welcomed Sir! If you ever have any questions, feel free to ask me.
danibus said:
Thanks for your guide, very nice to read your step by step, good as I didn't update nexus one since 1 year ago and I don't remember all steps.
Thanks!!
Click to expand...
Click to collapse
Thank you very much for taking the time to cook such a nice ROM for Nexus one. I hadn't installed any custom ROM on my device until some days ago. It is really awesome. Considering that Nexus one is an old device I do not expect to be any update for this ROM, but in case there was one I would appreciate it if you could post the link.
You need to see the first post for that to happen.
miui_nexus1 said:
Thank you very much for taking the time to cook such a nice ROM for Nexus one. I hadn't installed any custom ROM on my device until some days ago. It is really awesome. Considering that Nexus one is an old device I do not expect to be any update for this ROM, but in case there was one I would appreciate it if you could post the link.
Click to expand...
Click to collapse
Thanks for your quick reply. I am well aware of your updates to the ROM. I especially love the Nexus pie and appreciate the security updates.
ocd_amp said:
You need to see the first post for that to happen.
Click to expand...
Click to collapse
More security fixes!! I can't believe my eyes. Thanks a ton!
Hola launcher
I have tried Hola launcher (e.g. with chromatic theme), and its icons are similar to MIUI icons in contrast with Hola launcher (which is similar to latest Android versions).
P.s. I am just testing . I don't know if this launcher will drain the battery fast or not.
That launcher will slow down your system, and constantly try to download ads. It also takes up a LOT of RAM. The idea here to make the device run FAST consuming as little resources as possible. On a fresh boot, my N1 RAM usage is at 95MB, and after 28 Hours, it is 144MB. With other processes that are important Cached. My Dialer starts and makes calls upto 3 seconds faster than my Galaxy 3 on Lollipop.
All this can be achieved by disabling Google Play Services and Google Play Store from starting on boot (unless you have apps that you are always using and depend constantly on them) - I don't use apps that heavily depend on Google Play Services, and if I do, I start the service and the app, then I press the "back" key and exit Google Play Services. - Xposed Framework module attached to prevent Apps from running helps.
Battery life is great, easily lasts 2-3 days with minor screen time / talk time - Heavy usage can last a full day. This is all on a 2010 phone with an old battery. My Nexus One puts most people's dual core modern phones to shame when it comes to speed
miui_nexus1 said:
I have tried Hola launcher (e.g. with chromatic theme), and its icons are similar to MIUI icons in contrast with Hola launcher (which is similar to latest Android versions).
P.s. I am just testing . I don't know if this launcher will drain the battery fast or not.
Click to expand...
Click to collapse
That is fantastic battery life and speed you have!
I have got some questions and appreciate your help (Please forgive my newbie questions and such a long post)
1) When I want to run PHONE and MESSAGING applications on “Holo launcher” it gives this error message: "This activity cannot be launched". Although stock MIUI icons for these applications work fine.
2) I partitioned my memory card using ClockworkMod recovery and I dedicated 2 Gb’s of my 16 Gb class 10 microSD card (I haven’t had any problem with this recovery so far but if you think it may be incompatible with your ROM or cause issues please let me know and I will replace it). After flashing Ungaze Data2SD I see an increase in the internal memory . To be honest I didn’t completely understand the rest of the instructions so I do not know whether I have done it right or not.
"You can delete the Contents of /mnt/asec/d2sd/data/app/* and /mnt/asec/d2sd/data/data/* from your Device Root which is "/" after this otherwise you will have 2 copies of the same app. You should only have Dalvik-Cache in this location as it links to your Internal Memory Data partition. Make a backup first to your SD Card in case something goes wrong by copying those APKs, then simply Delete them. Your Device System Partition will have System Apps, Data partition will have Dalvik Cache and your SD Card's EXT Partition will have the rest of the Apps and their Data."
This is what I did:
I used “adb shell” to access the contents of those two locations and deleted their contents. As I said before I didn’t understand the rest of the instructions and I assumed it has been done correctly!! Then I installed my apps normally but I do not know whether they have been copied to the internal memory or the memory card. (I have downloaded apk’s of all apps I use from "apps.evozi. /apk-downloader/" or "apk4fun" and I have installed them using package manager).
My main question is what do I do after cleaning up those two locations and how do I install the apps so they will be copied to the memory Card’s Ext partition.
You should only have Dalvik-Cache in this location (What location exactly?)
Your Device System Partition will have System Apps (/system?)
Data partition will have Dalvik Cache (/data?)
SD Card's EXT Partition (/sd-ext?) If I am right as I have “adb” installed on my windows, it doesn’t show me the contents of this folder naturally. I have Ubuntu Linux too but “adb” is not installed on it.
Thanks a lot for your time!
1) Remove Holo Launcher icons and drag and drop Phone and Messaging icon from Drawer into the Dock at the bottom.
2) Use TWRP recovery.
3) /Data partition is EXT2 partition on your SDCard. Apps+Data (app data) will be there.
4) /mnt/asec/d2sd will be the "other" data partition (the original data partition) which is where your Dalvik cache will be.
5) Apps will be installed where their manifest suggests - Most apps will be installed to /Data on your EXT and their Dalvik Cache will be on the Internal parition /mnt/asec/d2sd/Dalvik-Cache
6) Use ES File Explorer - give it Root permissions - make sure Superuser permissions is set to On and inside ES Explorer you give Root access R/W - you can view all partions there
7) Use DiskInfo to see all your partitions
miui_nexus1 said:
That is fantastic battery life and speed you have!
I have got some questions and appreciate your help (Please forgive my newbie questions and such a long post)
1) When I want to run PHONE and MESSAGING applications on “Holo launcher” it gives this error message: "This activity cannot be launched". Although stock MIUI icons for these applications work fine.
2) I partitioned my memory card using ClockworkMod recovery and I dedicated 2 Gb’s of my 16 Gb class 10 microSD card (I haven’t had any problem with this recovery so far but if you think it may be incompatible with your ROM or cause issues please let me know and I will replace it). After flashing Ungaze Data2SD I see an increase in the internal memory . To be honest I didn’t completely understand the rest of the instructions so I do not know whether I have done it right or not.
"You can delete the Contents of /mnt/asec/d2sd/data/app/* and /mnt/asec/d2sd/data/data/* from your Device Root which is "/" after this otherwise you will have 2 copies of the same app. You should only have Dalvik-Cache in this location as it links to your Internal Memory Data partition. Make a backup first to your SD Card in case something goes wrong by copying those APKs, then simply Delete them. Your Device System Partition will have System Apps, Data partition will have Dalvik Cache and your SD Card's EXT Partition will have the rest of the Apps and their Data."
This is what I did:
I used “adb shell” to access the contents of those two locations and deleted their contents. As I said before I didn’t understand the rest of the instructions and I assumed it has been done correctly!! Then I installed my apps normally but I do not know whether they have been copied to the internal memory or the memory card. (I have downloaded apk’s of all apps I use from "apps.evozi. /apk-downloader/" or "apk4fun" and I have installed them using package manager).
My main question is what do I do after cleaning up those two locations and how do I install the apps so they will be copied to the memory Card’s Ext partition.
You should only have Dalvik-Cache in this location (What location exactly?)
Your Device System Partition will have System Apps (/system?)
Data partition will have Dalvik Cache (/data?)
SD Card's EXT Partition (/sd-ext?) If I am right as I have “adb” installed on my windows, it doesn’t show me the contents of this folder naturally. I have Ubuntu Linux too but “adb” is not installed on it.
Thanks a lot for your time!
Click to expand...
Click to collapse
Thanks a lot for the complete information. Holo launcher and Prevent running are really great. Now only 94 Mb of RAM is used . I expect to have better battery life too. I will report that after some days of using this configuration.
miui_nexus1 said:
Thanks a lot for the complete information. Holo launcher and Prevent running are really great. Now only 94 Mb of RAM is used . I expect to have better battery life too. I will report that after some days of using this configuration.
Click to expand...
Click to collapse
Oh lord, might be joining the N1 family due to recent corrupt internal data/EMMC failures on the Sensation and One Mini. Hoping to get a daily ROM and stable service from AT&T. Any critical updates/preventions prior to dusting off 2 years of being shelved and lending to 3 people (aka TANK N1).
Excited to see activity and will give this a shot when I get home. Thanks for posting!
Thanks for posting about Stagefright bug. It seems to be a hell of a bug. I have done all of them except the first one. Could you elaborate on how to edit build.prop?
By the way just a small thing: there is an extra "r" in
3) Use Firefox. Type about:config > Search for Stragefright > Set stagefright.disabled to True
Thanks again.
You're welcome. Enjoy!
lfe.zaius said:
Oh lord, might be joining the N1 family due to recent corrupt internal data/EMMC failures on the Sensation and One Mini. Hoping to get a daily ROM and stable service from AT&T. Any critical updates/preventions prior to dusting off 2 years of being shelved and lending to 3 people (aka TANK N1).
Excited to see activity and will give this a shot when I get home. Thanks for posting!
Click to expand...
Click to collapse
You edit build.prop either right on the phone using a text editor, or if you're like me, do it on the computer with Notepad++. It's a text based file. Oh yes, that was a spelling error. Fixed.
miui_nexus1 said:
Thanks for posting about Stagefright bug. It seems to be a hell of a bug. I have done all of them except the first one. Could you elaborate on how to edit build.prop?
By the way just a small thing: there is an extra "r" in
3) Use Firefox. Type about:config > Search for Stragefright > Set stagefright.disabled to True
Thanks again.
Click to expand...
Click to collapse
I have opened it using ES file explorer (ES Note editor) on my device but when I want to save it it shows an error:"Error occurred when trying to save the file. It will not be saved.". I have granted Superuser access to ES file explorer but I cannot find a way to give the specified permissions you have mentioned in the post. I would appreciate your help.
Hi all,
I updated my Nexus 7 to lollipop using the factory image (just to have a fresh start ..), but I noticed the available free space on /system partition is just a few Mb's.
After rooting (just superSu, no busybox) available space is 1.7 Mb and after editing the hosts file it is just 700 kb. I deleted the ringer tones (quite useless on a wifi only tablet) and that gave me 2.5 Mb of extra room. Any other tip to increase the /system free space ? The partition is typically read-only, but is it dangerous to be so low on free space ?
I'm afraid that could pose an issue on future upgrade, do you think google might consider re-partitioning the internal flash ?
thanks
bye
The above are reasonable questions.
Not being an expert, I wonder how much file system manipulation may be accomplished with an "in place" update.
I don't think the lack of file system headroom is a problem.
For upgrades down the road, cross that bridge when and if you get there. This device is not likely to receive another major update such as this.
I too deleted all my ringtone files save one. Also, I froze certain Google apps I'm unlikely to use. No ill effects that I can see.
With only 670 Mb of /system partition google has to decide what is in and what is out: as an example the launcher is still the old basic one because it has a smaller footprint. My Nexus 5 has googleNow launcher by default because its /system partition is 1 GB (and only 40Mb free). There will be a moment when the system files will not fit in 670 Mb and the nexus 7 will be abandoned ...
Sure the tablet is 2 years old and lollipop is very likely the last update, but I hope it will still be eligible for a 5.1 update (if any).
bye
Enrico
maybe something related with
http://forum.xda-developers.com/nexus-4/general/how-to-fix-internal-storage-16gb-8gb-t2033692
No, that is a different issue (which I also had and fixed with a factory reset). The /system partition is 670 Mb by google design and it is filled with system files.
For Google, 3 Mb of free space is more than enough, but if you have to root and/or do other changes, that might be a problem.
bye
i deleted all the programs in system that could be installed from the play store. even launcher since i installed the Now launcher.
Freed up a lot of system space and seems to have stopped most of the system lag.
I deleted the Maps and Chrome APKs, it looks like the updated versions of those google apps went into /data anyway so it wasn't needed in /system
I deleted some gapps with titanium (chrome, documents, "edicola" i don't know english name) but at reboot I have a lot of system UI error, so I return back to 4.4.4.
How I have to use for delete unwanted system apps?
Thanks!
When it comes to perceived or measured performance, it is inconsequential for a read-only filesystem to be nearly full. And /system is designed to be mounted read only - so there are no processes trying to write things there anyway.
It only matters to folks who might want to add additional content to the /system partition - and even then only at the moment of that operation; even if they fill it to 100% capacity, that will not cause a single performance issue.
Move along folks - nothing to see here.
Performed a full clean install last night, there was some lag. I rebooted a few times left it idle for a while but no difference. I'm doing this as I want to install Phantom kernel and move to F2FS which apparently needs a little more space free. So I moved some apps out of system to data and the difference was instant and noticeable.
bftb0 said:
When it comes to perceived or measured performance, it is inconsequential for a read-only filesystem to be nearly full. And /system is designed to be mounted read only - so there are no processes trying to write things there anyway.
It only matters to folks who might want to add additional content to the /system partition - and even then only at the moment of that operation; even if they fill it to 100% capacity, that will not cause a single performance issue.
Click to expand...
Click to collapse
That is exactly my feelings, I do not care if currently I have left only few Mb AFTER rooting and other tweaks, the partition is read-only and nobody is writing there during normal operation. After the initial adjustments, the tablet is smooth and runs fine even if the partition is nearly full.
I'm worried about future upgrades (if any): if an OTA fails because there is not enough space to update the /system partition (due to customised extra files) and/or after the OTA upgrade there is no room to add the superSu app to root ... then we are in trouble.
bye
Enrico
enryfox said:
I'm worried about future upgrades (if any): if an OTA fails because there is not enough space to update the /system partition (due to customised extra files) and/or after the OTA upgrade there is no room to add the superSu app to root ... then we are in trouble.
Click to expand...
Click to collapse
If the current OTA update is how future OTA updates will be installed (and there's no reason to suggest it's not) then any change you make to System will cause the OTA to fail, even if you change back everything. Meaning it will fail, not because it ran out of space because of the customized files you mentioned, but because it was tinkered with even the slightest bit.
So if the OTA behavior is like the current one, then do whatever you want to System, delete stuff, fill it up to the brim, doesn't matter because come next OTA time you'll have to flash the stock system image file anyway, if you wanna keep your data, or flash the then new stock firmware entirely, like you did this time.
dtg7 said:
If the current OTA update is how future OTA updates will be installed (and there's no reason to suggest it's not) then any change you make to System will cause the OTA to fail, even if you change back everything. Meaning it will fail, not because it ran out of space because of the customized files you mentioned, but because it was tinkered with even the slightest bit.
Click to expand...
Click to collapse
Actually I started with a rooted 4.4.4 and sideloaded the 5.0 OTA: it worked and the the update was applied successfully. My problem was that /system was really full to the brim, with 0 bytes left and that is way I applied the factory image. With current grouper 5.0 official image there is simply not enough space to root, install busybox and change the hosts file, we need to make some room to get all three tweak's.
I'm surprised future OTA's will not work simply because we tinkered with system files; until now I always applied new OTA's over rooted system files and they always worked (from 4.3 all the way up to 4.4.4).
bye
Enrico
enryfox said:
Hi all,
I updated my Nexus 7 to lollipop using the
factory image (just to have a fresh start ..)
Click to expand...
Click to collapse
enryfox said:
Actually I started with a rooted 4.4.4 and sideloaded the 5.0 OTA: it worked and the the update was applied successfully.
Click to expand...
Click to collapse
Kind of conflicting statements there...
Anyway here's what I understood about Lollipop OTAs: http://www.androidpolice.com/2014/1...e-means-update-will-fail-system-modified-way/
So in conclusion I'm just gonna do whatever to system and flash stock system when next OTA comes around.
dtg7 said:
Kind of conflicting statements there...
Click to expand...
Click to collapse
no Conflicts here :
enryfox said:
Actually I started with a rooted 4.4.4 and sideloaded the 5.0 OTA: it worked and the the update was applied successfully. My problem was that /system was really full to the brim, with 0 bytes left and that is way I applied the factory image.
Click to expand...
Click to collapse
the OTA + root process left me with a /system partition full and there was no way to free space (I do not know why) so I had to restore the factory image.
The new OTA policy, as for my experience, does not apply to the our Nexus 7: the android 5.0 OTA applied to my rooted nexus7 flawlessly; if it wasn't for the rooting process filling up the /system partition, I would have kept it as it was.
bye
Enrico
i think same Problems in my moto g 5.0.2 LP stock 20mb free space in /Sys.
Someone should make a deodexed stock ROM, so there'd be more free space? I'd do it myself but my PC isn't powerful enough to run the deodex tool and my upload speed is 350kb/s so I wouldn't be able to upload it anywhere (400-500MB)
Inviato dal mio XT1032 utilizzando Tapatalk
It's all the apps that the ROM flashed into the system partition. I found myself with 1MB free. I needed that space for root apps so I installed Titanium Backup and uninstalled several apps that you can grab from the Play Store. I got to 103MB free in /system.
I wasn't sure if uninstalling the foreign language keyboards would cause problems, so I left those alone. If anyone know if they can be safely removed please let me know.
Anywho, I'll list what I removed.
Chrome
YouTube
Drive
Maps
Street View
Google+
Wallet
Play Music
Sound Search
Don't forget to reboot after uninstalling. Then install from the Play Store.
LuvMyDroid said:
It's all the apps that the ROM flashed into the system partition. I found myself with 1MB free. I needed that space for root apps so I installed Titanium Backup and uninstalled several apps that you can grab from the Play Store. I got to 103MB free in /system.
I wasn't sure if uninstalling the foreign language keyboards would cause problems, so I left those alone. If anyone know if they can be safely removed please let me know.
Click to expand...
Click to collapse
The foreign languade keyboards (as well as the ASUS keyboard) are among the things I've uninstalled to free up some space in the system partition. I've seen no ill effects. My system partition has about 65 MB free. Here's what I've uninstalled:
ASUS Keyboard
Docs
Google Hindi Input
Google Korean keyboard
Google Pinyin Input
Google Play Games
Hangouts
Sheets
Slides
Talkback
I confirm that, also, N7 3G is smoother than before with lollipop 5.0.2 with more space in system partition
As far as I know one can't re-size the partitions of a I9509... But there is a huge amount of lost space in system partition specially when on a debloated custom ROM.
Therefore I thought isn't there a way to simply install apps to system partition and keep them (automatically) updated there either... Is there a solution for that?
Or any other idea how to use that senseless wasted space?
Thx a lot!
You could use Titanium Backup to make apps into system apps. But it could make them malfunction.
I'm using Link2SD. It has a free option to integrate system app updates into system or turn a user app into a system app.
TB needs the paid version for that.
- Deleted -
Interesting, means when I change a user app into system app it will updatr normally through play store in normal storage but then link2sd can integrate it into that system app...
Is that done in a batch procedure or do I have to do it for every app by myself?
Yeah, I would do that with ES file explorer but still one would have to update the apps manually what means a lot of work because the updates would be installed in normal storage for normal system apps...
Titanium Backup has an "Integrate update into app" option that moves the update to the app folder
link2sd is single apps, even plus Beware of google play services and/or services Framework, integrating their updates can cause annoying failure loops sometimes leading to pulling the battery to reboot. I tend to do them last or solo as a result. Tasker might be able to do the job for bulk or automatic, I haven't used it much, so idk.
Have no problem integrating GPServices or PlayStore into system on stock firmware. Doing it on GPE for example makes the playstore unusable.
As for the batch option there isn't one but the system updates are not that frequent to need this option
This guide involves UNLOCKING and re-locking boot-loader! Know, what you do, before you do it!
Supported phones:
Personally tried on Xperia X Compact, but should work on any firmware that uses OEM partition.
Background:
Recently, when playing with my new Xperia X Compact, I have found, that provider customisation like custom boot-animation, bloatware and overlays (enabling or disabling certain functionality), have been moved from /system/vendor to new /oem partition. Moreover, I have found, that as opposite to the /system the /oem partition is unprotected. It means, it can be modified, without triggering system unbootable because of dm-verity.
Process overview:
I don't go into specific detail, because I expect users to have sufficient knowledge/skills before trying.
1. BACKUP YOUR TA partition. BACKUP your TA partition.
2. Unlock boot-loader
3. Root your phone (install patched kernel+supersu or superuser)
4. Feel free to modify the OEM partition (/oem) the way you want. You may delete apps and overlay, delete or change boot-animation and many other things I did not found out yet, including custom build.prop etc.
5. Re-lock your boot-loader by flashing your TA backup back to TA partition
6. Flash back the stock firmware, or minimally just stock kernel. If you use Flashtool EXCLUDE OEM
After reboot, you will have back locked boot-loader, with stock firmware, but without bloat from your provider and with any modification you may want. It includes also apps you may add to /oem/app and /oem/priv-app. By my understanding, these apps will run like system apps, not user apps.
Perhaps somebody can find a way, we can use OEM partition to obtain root on locked bootloaders?
@tobias.waldvogel @shoey63 @AndroPlus or othe kernel / system gurus, any idea?
ondrejvaroscak said:
these apps will run like system apps, not user apps
Click to expand...
Click to collapse
That's what makes a trouble! To understand things better, apps have 4 diferent signing methods, one is signed with system key, one with app key, one with shared key...etc, SO to get custom app with "system level" you need to sign app with private system key, and only one problem trought we do not have private sony key to make any app with system level on fully stock non hacked rom
munjeni said:
That's what makes a trouble! To understand things better, apps have 4 diferent signing methods, one is signed with system key, one with app key, one with shared key...etc, SO to get custom app with "system level" you need to sign app with private system key, and only one problem trought we do not have private sony key to make any app with system level on fully stock non hacked rom
Click to expand...
Click to collapse
Ok, clear. However, to integrate apps into OEM partition is just one example of possible uses. Maybe there is something more that can be achieved, since OEM partition is not protected and can be maybe in some way used to modify running system...
Project Mainline consists of modularising system components in updatable packages, APEX files. Updating uses a versioning system where new APEX files are presented to the user as "Google Play System Updates". These files are updated in much the same way as APKs. That also means that when there is an update these get stored in /data (userdata partition), as per the explanation in the official Android documentation:
The new APEX is stored in /data and, similar to APKs, the newly installed version shadows the version already present in the built-in partition. But unlike APKs, the newly installed version of the APEX is only activated after reboot.
Click to expand...
Click to collapse
As a consequence, these updates do not survive a factory reset and serve more as a stopgap in-between full OTA system updates (which of course do persist after reset).
Another consequence is that all these APEX file updates in /data take a lot of space. In addition to system apps (APKs) being updated and taking space on /data, now whole parts of the OS are being modularised and its updates replicated in /data, leaving increasingly lower space in the userdata partition, the further Project Mainline gets. For newer devices with plenty of space that's not a problem, but on XDA we also like to extend the usable life of older devices, which may therefore not benefit from having their system components "APEXed".
In sum, what I would like to know from anyone interested in this discussion, and especially experienced Android users or developers is this:
"For older or low end devices with lower storage capacity, are you going to discourage users from using Google Play Services or at least from updating the system using the APEX updating scheme?"