Somehow over the weekend, thought about disabling the Account Sync, yeah, mail, chrome, keyboard, and my Nexus 7 with Lollipop is usable again! Faster access to Chrome and Keyboard especially!
Nothing else I have tried that I have found online works.
My tablet is not my main device, so its fine to manual sync a lot of things.
Indeed. Chrome is the biggest problem. I removed every Google app that wasn't needed and flashed an OC kernel and it's "great".
ykphuah said:
Somehow over the weekend, thought about disabling the Account Sync, yeah, mail, chrome, keyboard, and my Nexus 7 with Lollipop is usable again! Faster access to Chrome and Keyboard especially!
Nothing else I have tried that I have found online works.
My tablet is not my main device, so its fine to manual sync a lot of things.
Click to expand...
Click to collapse
I just discovered this over the past couple days. I disabled only a few services from Google account sync and it definitely made my nexus 7 usable again!
Sent from my SM-N920T using Tapatalk
so using something like a CM ROM without gapps gives similar results? interesting
Yup! totally un-usable with android 5.0 I'm Using android 4.4.4 and now have a working tablet. After a week or two of usage i'm having to clear cache. Then it's back to snappy normal self. Does Google Know This?
Seems to work for me!
But it cannot prevent me for trying CM
Thanks though for sharing your discovery.
It's still a very nice tablet, but JB was for me the best Android Experience.
Since 4.3 and higher I was quite disappointed because the laggy system.
With animations turned off (don't need em) and system upgrade cache cleared, my lollipop has been running like a brand new device with no other special tweaks. Of course almost nothing affects chrome, but let's not go there. I mostly use Adblock browser these days.
dharmaburning said:
With animations turned off (don't need em) and system upgrade cache cleared, my lollipop has been running like a brand new device with no other special tweaks. Of course almost nothing affects chrome, but let's not go there. I mostly use Adblock browser these days.
Click to expand...
Click to collapse
How did you cleared the system upgrade cache?
Sent from my Nexus 7 using Tapatalk
on lollipop and marshmalow i had lot of freeze but since i flashed the new twrp 3.0 my nexus grouper run like a charm on marshmalow .
ykphuah said:
Somehow over the weekend, thought about disabling the Account Sync, yeah, mail, chrome, keyboard, and my Nexus 7 with Lollipop is usable again! Faster access to Chrome and Keyboard especially!
Nothing else I have tried that I have found online works.
My tablet is not my main device, so its fine to manual sync a lot of things.
Click to expand...
Click to collapse
Well this trick does work but it still lags sometimes even with the account syn off.I also tried a couple of performance boosting apps like root booster and trimmer and the no animation settings in devloper options but it didn't really become faster.
After being frustrated by the slowness of my Nexus 7, i rooted it with Kingroot and converted it to SuperSU through android emulator, unlocked the bootloader and flashed Slimkat 4.4.4 and boom! the smooth experience is back.It's not so up to date(Kitkat 4.4.4) but the main thing is it's fast and stable.
BryantTheDefiant said:
Yup! totally un-usable with android 5.0 I'm Using android 4.4.4 and now have a working tablet. After a week or two of usage i'm having to clear cache. Then it's back to snappy normal self. Does Google Know This?
Click to expand...
Click to collapse
So did you you find a 4.4 ROM that is not affected by the stagefright security hole? I wasn't able to find anything (at least not for the Tilapia/3G version).
I'd rather throw out an unresponsive tablet than to run it with an operating system that has seen the last security updates in 2014 and that can be hacked by simply playing back an MP3 or MP4 file!
wutzin said:
So did you you find a 4.4 ROM that is not affected by the stagefright security hole? I wasn't able to find anything (at least not for the Tilapia/3G version).
I'd rather throw out an unresponsive tablet than to run it with an operating system that has seen the last security updates in 2014 and that can be hacked by simply playing back an MP3 or MP4 file!
Click to expand...
Click to collapse
This unofficial CM11 build is great with all the latest security fixes and is being updated by the dev each month. Unfortunately no build for the tilapia ( unless you want to flash and lose 3G).
LInk:
http://forum.xda-developers.com/nexus-7/development/unofficial-build-cyanogenmod-11-0-nexus-t3174831
gsmyth said:
This unofficial CM11 build is great with all the latest security fixes and is being updated by the dev each month. Unfortunately no build for the tilapia ( unless you want to flash and lose 3G).
LInk:
http://forum.xda-developers.com/nexus-7/development/unofficial-build-cyanogenmod-11-0-nexus-t3174831
Click to expand...
Click to collapse
That's the one I found that was Grouper only - didn't realize I could just flash it and only lose 3G. Thanks for that info!
I guess I will give CM13 a quick shot, and then say goodbye to 3G
wutzin said:
That's the one I found that was Grouper only - didn't realize I could just flash it and only lose 3G. Thanks for that info!
I guess I will give CM13 a quick shot, and then say goodbye to 3G
Click to expand...
Click to collapse
I think you need to make a few changes in the updater script to flash on the tilapia as per the steps below and you should be good to go. I also recommend changing the number of background processes to 4 under developer settings. It really makes everything snappy and switching betweens apps lag free. It may restrict switching between lots and lots of apps but I generally find I only want to switch between the last 2/3 apps anyway.
I run the unofficial CM11 as my main rom on multirom, I've also downloaded GtrCraft's CM13 to try out but havent installed yet.
1. Unzip the rom
2. Go to folder META-INF/com/google/android/
3. Edit updater-script with text editor
4. Change all "grouper" with "tilapia"
5. Save it
6. Zip the rom again
gsmyth said:
I think you need to make a few changes in the updater script to flash on the tilapia as per the steps below and you should be good to go. I also recommend changing the number of background processes to 4 under developer settings. It really makes everything snappy and switching betweens apps lag free. It may restrict switching between lots and lots of apps but I generally find I only want to switch between the last 2/3 apps anyway.
I run the unofficial CM11 as my main rom on multirom, I've also downloaded GtrCraft's CM13 to try out but havent installed yet.
1. Unzip the rom
2. Go to folder META-INF/com/google/android/
3. Edit updater-script with text editor
4. Change all "grouper" with "tilapia"
5. Save it
6. Zip the rom again
Click to expand...
Click to collapse
Thanks so much for your tips!!!
To anyone following these instructions to patch the grouper rom for flashing on the tilapia, I have one little addition: in step 4, don't change ALL "grouper" to "tilapia", but only the instances at the beginning of the file. There is one statement later in the file that you should leave unchanged: set_metadata("/system/vendor/lib/hw/power.grouper.so", "uid", 0, "gid", 0, "mode", 0644, "capabilities", 0x0, "selabel", "ubject_r:system_file:s0");
wutzin said:
Thanks so much for your tips!!!
To anyone following these instructions to patch the grouper rom for flashing on the tilapia, I have one little addition: in step 4, don't change ALL "grouper" to "tilapia", but only the instances at the beginning of the file. There is one statement later in the file that you should leave unchanged: set_metadata("/system/vendor/lib/hw/power.grouper.so", "uid", 0, "gid", 0, "mode", 0644, "capabilities", 0x0, "selabel", "ubject_r:system_file:s0");
Click to expand...
Click to collapse
Thank you for the detailed instructions, I really only passed on the info that was already in the thread.
Related
I was really getting tired of my carrier name showing up twice on the lockscreen and taking up extra real estate on my notification drop-down so I figured out how to disable the SPN from showing and how to customize the PLMN to say whatever I want.
KEY FILES TO EDIT
/data/data/com.android.providers.telephony/optable.db
/system/etc/apns-conf.xml
/system/etc/spn-conf.xml
In the apns-conf.xml make sure your provider is listed with a numeric value.
Here's an example: numeric="311370" mcc="311" mnc="370"
* As you can see the numeric is the MCC plus the MNC.
In the spn-conf.xml make sure your provider is listed with an spnOverride.
Here's an example: <spnOverride numeric="311370" spn_display_rule="SPN_RULE_SHOW_PLMN" spn_override_only_on="310,311"/>
The optable.db needs to be edited with SQLite Database Browser to add your numeric and the text to display.
Here are a few pre-configured downloads:
PLMN: CyanogenMod
http://www.4shared.com/file/BawWWTpv/cm7_plmn_gsm_crespo.html
PLMN: The Ultimate Droid
http://www.4shared.com/file/jo0455rx/tud_plmn_gsm_crespo.html
PLMN: GCI Wireless
http://www.4shared.com/file/l3fZUzGu/gci-apns-plmn.html
PLMN: B*** I Got An Android (with no asterisks)
http://www.4shared.com/file/Vkz6poYC/*****_plmn_gsm_crespo.html
NSFW YouTube Video - B*** I Got An Android
Flash these files AFTER you have flashed a ROM and booted up at least once! I tested all four files on TUD 3.0.0 Beta, CM7 A3, and various CM7 Crackflasher builds.
*Screenshots are from CM7 Crackflasher build #54 with the Jungle Waterfall livewallpaper
Very cool mod. I will try this out when I have the time!
thank you
Love this, it worked great on Bionix with 1.3 kernel. For some reason running the same rom with the new 1.4b kernel it no longer works and yes I tried reflashing and wiping a few times. Any ideas?
Hey could you make me one and either PM me or post it up?
I'm on CM7 on a Nexus S, and I don't see a '/system/etc/spn-conf.xml' file. It doesn't seem to exist on mine. I'm on the latest nightly (#8) and have updated everything. Am I missing something?
How exactly did you get these files? I'm having all sorts of trouble with this. First off, the optable.db file is zero K, even when I extract it through ASTRO or Root Explorer with R/W permissions. Secondly, as I mentioned in the last post, the 3rd file is missing from the stated directory.
I'm really confused, as it seems that none of these instructions add up for a Nexus S. I'd like my T-Mobile message to instead display "Nexus S: Pure Android, Pure Google"
Did not work on Modaco R9, CM7 or The Cracker builds...
nickmv said:
I'm on CM7 on a Nexus S, and I don't see a '/system/etc/spn-conf.xml' file. It doesn't seem to exist on mine. I'm on the latest nightly (#8) and have updated everything. Am I missing something?
Click to expand...
Click to collapse
spns-conf.xml does not exist on the Nexus S originally, but if you place it in /system/etc/ the OS knows to use it.
nickmv said:
How exactly did you get these files? I'm having all sorts of trouble with this. First off, the optable.db file is zero K, even when I extract it through ASTRO or Root Explorer with R/W permissions. Secondly, as I mentioned in the last post, the 3rd file is missing from the stated directory.
Use the optable.db from my zip and just edit it as you see fit.
I'm really confused, as it seems that none of these instructions add up for a Nexus S. I'd like my T-Mobile message to instead display "Nexus S: Pure Android, Pure Google"
Click to expand...
Click to collapse
I'm not sure what the character limit is but that might be too long.
I have all the files in the proper folders but it still doesn't work. Modaco R9
for those having problems getting this to work try using clockwork and press mount/storage then mount/system. hope this works.
tsalate said:
for those having problems getting this to work try using clockwork and press mount/storage then mount/system. hope this works.
Click to expand...
Click to collapse
You might be on to something, it worked for about 3 seconds then went right back to T-Mobile.
Still doesn't work. Mounted /system and /data. Does it only work for certain carriers? I'm using a&t
Is there a way to apply this to ALL carriers, rather than selecting one manually.
thanks
removed for reconstruction
Downloading this now, will flash and report.
I want my unicorns
MarkInDaPark said:
Downloading this now, will flash and report.
I want my unicorns
Click to expand...
Click to collapse
Forgot screenshots:
Okay, played for a few minutes and these are my results so far;
AOKP settings crash easily, for example by trying to change processor speeds // Only on first boot
Annoying "Preparing USB Storage" notification, SD card works though // Only on first boot
ROM is snappy and speedy
The install procedure was confusing; I'd like to see it just as a normal flashable ZIP, this is useless rice
Wake on trackpad doesn't work (is the script included, as in the Zeu CM10?) // The script is included in /system/bin/trackballwake, and it works
ROM feels slightly bloated (don't include all these third party apps in the future!) // Removed a lot of bloat by TBP and ROM accually had some space left. It's very crowded stock.
Also, is it allowed to include gapps in this manner?
MarkInDaPark said:
Okay, played for a few minutes and these are my results so far;
AOKP settings crash easily, for example by trying to change processor speeds // Only on first boot
Annoying "Preparing USB Storage" notification, SD card works though // Only on first boot
ROM is snappy and speedy
The install procedure was confusing; I'd like to see it just as a normal flashable ZIP, this is useless rice
Wake on trackpad doesn't work (is the script included, as in the Zeu CM10?) // The script is included in /system/bin/trackballwake, and it works
ROM feels slightly bloated (don't include all these third party apps in the future!) // Removed a lot of bloat by TBP and ROM accually had some space left. It's very crowded stock.
Also, is it allowed to include gapps in this manner?
Click to expand...
Click to collapse
You have to do same trick as per original CM10, i.e set "keep Wifi on during sleep" to "always". Also after create/sign in your google account, give it a reboot.
Aroma installer, if proper configured allows you to customize your rom while flashing. You can also, after flashing rom, go back to aroma and check system info (model, name, device,storage, cpu, LCD density and other details)
Trackballwake is same as Zeu CM10
The difference on this rom is it creates /data folder during flashing and install whatever non-system apps you want in this folder, leaving more space in system folder. So you can customize the rom as you like by adding/removing apps in the zip file, "data folder", before flashing. I found it useful as every time i flash a rom i have to spend time installing market, gps fix, antutu, terminal emulator and all other stuff i need.
Also apps in the zip file "data/app" folder being user apps you can uninstall them easy after flash.
Most if not all of the supplementary apps got them from other roms posted on this site. They are free anyway and i don't sell them.
Will it work on hboot 1.00 s-on
Sent from my Legend using xda app-developers app
ic3141 said:
You have to do same trick as per original CM10, i.e set "keep Wifi on during sleep" to "always". Also after create/sign in your google account, give it a reboot.
Click to expand...
Click to collapse
I can't even connect to my WiFi network, but I can't do that in CM10 either, so I guess it's some router problem or something.
ic3141 said:
Aroma installer, if proper configured allows you to customize your rom while flashing. You can also, after flashing rom, go back to aroma and check system info (model, name, device,storage, cpu, LCD density and other details)
Click to expand...
Click to collapse
...Do people really want this? I don't get the point of an 'installer'. We have the glorious ZIP flash - the way God meant us to install ROMs.
Configuring ROM during flash? No. I think many people agree that we want a clean AOKP. You could make two zips; one clean AOKP, and one with your bloat/"useful apps" so that those who can't be arsed to download 7 apps (or restore them from earlier) can do so by flashing a zip.
ic3141 said:
Trackballwake is same as Zeu CM10
Click to expand...
Click to collapse
Yep, works fine.
ic3141 said:
The difference on this rom is it creates /data folder during flashing and install whatever non-system apps you want in this folder, leaving more space in system folder.
Click to expand...
Click to collapse
More space? I found myself with a studdering, slow system after a few reboots. Looking in TBP, I noticed that I had 45kB free in /system.
Removed some system apps and I had 3 MB left. Isn't that less than CM10?
ic3141 said:
So you can customize the rom as you like by adding/removing apps in the zip file, "data folder", before flashing. I found it useful as every time i flash a rom i have to spend time installing market, gps fix, antutu, terminal emulator and all other stuff i need.
Click to expand...
Click to collapse
Ever heard of Titanium Backup? Much simpler than fiddling with a ton of apks.
ic3141 said:
Most if not all of the supplementary apps got them from other roms posted on this site. They are free anyway and i don't sell them.
Click to expand...
Click to collapse
Uh yes, but if you read and responded to what I was typing, i said "gapps". Notice the "g", meaning "google" in this case. This is a set of proprietary google-apps, which are to be provided seperatley for all non-AOSP builds due to licensing.
ic3141 said:
removed for reconstruction
Click to expand...
Click to collapse
I have decided to wait a while for a more stable JB rom (thanks to Zeubea).
Will post the port for the last nightly built together with a small surprise: MIUI 2.10.26 (quite stable) and 2.11.23 (a lot of diff still required)
In all of the current AOSP builds, the forward facing camera video fails because the information is pulled from msm8960-common. We share almost everything in common with the other devices, but our forward facing camera is of lower resolution so the base settings do not work with ff video on the xt907.
This is a relatively simple xml edit that I have played around with. I have tested on CM10.1 rc and CM10.2 nightly with the stock camera and hangouts video (it starts ok with hangouts, but I'm not where I can have a conversation with anyone right now so ymmv). It should work on all of the aosp based builds.
To apply use a root enabled file explorer, in directory...... delete your existing media_profiles.xml (or add .bak extension). copy this file, remove the .txt extension, and set permissions to rw-r-r then reboot.
I will try and get a flashable zip up later if anyone wants it. That way, you can simply flash it after flashing your rom of choice if you are running nightlies or like to try new builds often.
Let me know if it works or if anything looks like it needs tweaking.
********Update********
it may be necessary to clear data on camera/gallery app after updating the media_profiles.xml file
also adding flashable zip file
ej1911 said:
In all of the current AOSP builds, the forward facing camera video fails because the information is pulled from msm8960-common. We share almost everything in common with the other devices, but our forward facing camera is of lower resolution so the base settings do not work with ff video on the xt907.
This is a relatively simple xml edit that I have played around with. I have tested on CM10.1 rc and CM10.2 nightly with the stock camera and hangouts video (it starts ok with hangouts, but I'm not where I can have a conversation with anyone right now so ymmv). It should work on all of the aosp based builds.
To apply use a root enabled file explorer, in directory...... delete your existing media_profiles.xml (or add .bak extension). copy this file, remove the .txt extension, and set permissions to rw-r-r then reboot.
I will try and get a flashable zip up later if anyone wants it. That way, you can simply flash it after flashing your rom of choice if you are running nightlies or like to try new builds often.
Let me know if it works or if anything looks like it needs tweaking.
Click to expand...
Click to collapse
hmm, having some troubles getting the file to download - just showing up as a text in my browser....
edit: just copied to a notepad, saved it, and e-mail it to myself. downloaded it, placed it in the "system/etc" folder, changed permissions, rebooted.... but no dice for me, still get a force close. wondering if it has to do with me being on AOKP, since you said this is for AOSP ROMs....
jco23 said:
hmm, having some troubles getting the file to download - just showing up as a text in my browser....
edit: just copied to a notepad, saved it, and e-mail it to myself. downloaded it, placed it in the "system/etc" folder, changed permissions, rebooted.... but no dice for me, still get a force close. wondering if it has to do with me being on AOKP, since you said this is for AOSP ROMs....
Click to expand...
Click to collapse
Easiest way is to right click the file and save as.
Couple of questions. Which app is force closing, is it the camera? and Which AOKP are you on? I have most of them downloaded. I will try to flash it and see if I can figure it out.
ej1911 said:
Easiest way is to right click the file and save as.
Couple of questions. Which app is force closing, is it the camera? and Which AOKP are you on? I have most of them downloaded. I will try to flash it and see if I can figure it out.
Click to expand...
Click to collapse
well, the official message is that the gallery has stop responding (same as before) - but this happens when I attempt to launch camcorder in front-facing mode - so yes, it is camera, but I think android refers to it as "gallery".
i believe that video calls for hangouts works fine though (but I'll test again tonight).
I'm on the "unofficial" AOKP ROM
jco23 said:
well, the official message is that the gallery has stop responding (same as before) - but this happens when I attempt to launch camcorder in front-facing mode - so yes, it is camera, but I think android refers to it as "gallery".
i believe that video calls for hangouts works fine though (but I'll test again tonight).
I'm on the "unofficial" AOKP ROM
Click to expand...
Click to collapse
OK, thanks. You might have to clear the data in the gallery app, I'm not sure. I got the video camera to work on the AOKP 4.3 9/11 nightly, but I flashed the update zip that I made to test it and it was a fresh install. I couldn't do much testing though because I got the AOSP keyboard is force closing problem.
I will update the OP in a little bit with the flashable zip file.
ej1911 said:
OK, thanks. You might have to clear the data in the gallery app, I'm not sure. I got the video camera to work on the AOKP 4.3 9/11 nightly, but I flashed the update zip that I made to test it and it was a fresh install. I couldn't do much testing though because I got the AOSP keyboard is force closing problem.
I will update the OP in a little bit with the flashable zip file.
Click to expand...
Click to collapse
got it working now.
i downloaded the file this time, e-mailed it to myself, copied it to the "system/etc" folder, changed permissions, renamed the org as .bak, renamed the new file as .xml, then rebooted. after reboot, I went into the camera app and once again got a force close. however, I tried playing around with the settings "record mode" from 1020 to 480, and then went back to FF camcorder, and it recorded! I then changed the "record mode" back to 1080, and FF camcorder worked just fine.
so I think you are correct, perhaps one needs to clear cache/data in the gallery prior to use.
thanks for the tip and the mod! nice work!
to resolve your AOSP keyboard force closing problem, try wiping system before installing the update. this worked for me.
Bit of thread necro, I know... But it's for a good cause.
Have you pushed this fix to CM? I am looking into what exactly needs to change in the source, I suppose we can fix this somehow from CM, and then all of the ROM's will be fixed (assuming they all update with the fix )
The flashable zip worked perfect for me. Thank you so much!
---
Sent using my Droid Razor M- THE BEST SMARTPHONE ON THE PLANET!
Heard about Kettlebells... learn more: http://synergykettlebell.com
arrrghhh said:
Bit of thread necro, I know... But it's for a good cause.
Have you pushed this fix to CM? I am looking into what exactly needs to change in the source, I suppose we can fix this somehow from CM, and then all of the ROM's will be fixed (assuming they all update with the fix )
Click to expand...
Click to collapse
Argggh merged it into cm code. All it should flow to all ROMs as they sync and build.
Sent from my XT907 using xda app-developers app
** DISCLAIMER: I AM NOT A DEVELOPER. I DO THIS AS A HOBBY AND SHARE MY FINDINGS IN CASE SOMEONE ELSE FINDS THEM USEFUL. **
** THIS WORKED ON MY DEVICE BUT IT MAY NOT WORK ON YOURS. APPLY AT YOUR OWN RISK **
This is a de-bloated version of the latest KitKat 4.4.2 Rom from T-mobile, i.e. G900TUVU1BNH5. I ported it to ATT and stripped it down to basics. Here is what you will find in this ROM:
Calculator, Calendar, Camera,Clock, Ctontacts, Email, Gallery, Google search and voice, stock browser, Google maps, Memo, Phone and SMS, Music player, My Files, Play Store,Video, Voice recorder, and Youtube.
Everything else has been removed. The zip file size is just under 700MB.
Other features:
1- Pre-rooted and deodexed.
2- Knox, security apps, and updater disabled (your phone will no longer update itself without your knowledge)
3- Call recording enabled.
4- SDcard write restrictions removed.
5- Tethering restrictions removed.
6- Download Bosoter functional on AT&T network.
Requirements:
1- Safestrap or custom recovery.
2- To begin with, you should be on ATT NCE4 rom or a variant of that. It has been reported that this is incompatible with NG3
Download link:
Mega https://mega.co.nz/#!tlcnwBJb!tqGDImZ-HOVKVi_ykMGzNG20qgEOXfS7cxMLdQCtsp0 (version 3)
Instructions:
This is a flashable zip. Boot to recovery to flash it. I strongly recommend a clean wipe before flashing a new Rom.
After reboot, leave the phone alone for 10 minutes before you use it. After the first reboot the data connection takes a while to be recognized. If it does not connect after 10 min, enable and disable airplane mode and it should be fine after that.
There are a few more megs that can be squeezes out of this still so I will update this to a version 2 in the next few days.
A Word about Debloating
There is a misconception that if the size of a ROM is smaller it leaves more usable space on the phone. That is not true. For example, in Galaxy S5, around 2.5GB is earmarked for the system rom, whether it is filled or not. So if you make a very small ROM the space you save is still earmarked for the system and will not show up as free space on your SDcard or whatnot, unless you repartition your /system (bad idea) or manually open some storage space in /system and use it (poor idea). Therefore, in debloating this ROM I mostly removed the elements that constantly run in the background and make the system slow and left a lot of what is not actively used intact, even if they were big in size.
Credits:
JustArchi for creating ArchiKitchen
Screenshots
Applications that come with the rom.
V1: Initial release
V2: Baby crying detector and Samsung Dictionary removed
V3: Removed: T-mobile boot up and power off insignia, non-essential media files, non-US-English VODB and sipdb files. non-essential libraries. Fixed a potentially fatal typo in the update script.
Okay, kind of confused here... This is V1 and your other NH5 thread is V2. Whats the difference between this and the other? More "debloated"?
joe3681 said:
Okay, kind of confused here... This is V1 and your other NH5 thread is V2. Whats the difference between this and the other? More "debloated"?
Click to expand...
Click to collapse
The rom on the other thread is not de-bloated. The file in that thread has every single file that came with the stock ROM. The knox and updater and security files are all in there and just disabled, in case someone just decides to go back to full stock.
In this thread I have removed a long list of apps and directories and libraries. That is why the file here is half the size of the one on the other thread.
I tested this on ANCE base. No FC or hangup. Smooth as butter.
Loving what you're doing here. No-frills, simple rom.
Keep up the good work. I like that the things that normally run in the background are removed, it's great
Edit: Chrome says the file is Malware when I download from MEGA. You probably didn't upload malware but that's what it's telling me. Just letting you know
skyrocketeer said:
Loving what you're doing here. No-frills, simple rom.
Keep up the good work. I like that the things that normally run in the background are removed, it's great
Edit: Chrome says the file is Malware when I download from MEGA. You probably didn't upload malware but that's what it's telling me. Just letting you know
Click to expand...
Click to collapse
Chrome is trying to be cautious here because it sees an install script and a file marked as executable inside a zip file and freaks out. Or it could be because MEGA has been associated in the past with malware download. Whatever the reason, this conservative approach results in false alarms which is known for Chrome. See for example: https://torrentfreak.com/chrome-blocks-utorrent-as-malicious-and-harmful-software-140716/
I suggest that you either ignore the chrome warning, click on "show all downloads" and locate the file and recover it, or download it with Firefox. In either case, after you are done downloading, scan it with a reputable virus scanner of your choice. I just downloaded it myself, scanned it with McAfee Enterprise Edition and it is clean.
Anybody encounter binary updater error while flashing this? Coming from DK rom
l34rn said:
Anybody encounter binary updater error while flashing this? Coming from DK rom
Click to expand...
Click to collapse
If you are not using safestrap make sure you have the latest TWRP or CWM installed. If you use safestrap please describe what kind of error you get. You can use the log utility to save the output of the install script on the SD card to see later what the error is.
I don't seem to be able to sync my contacts. The contact option is not listed under the google account. Calendar is not there either and the calendar won't sync.
Sent from my SM-G900T using XDA Free mobile app
gregthomas129 said:
I don't seem to be able to sync my contacts. The contact option is not listed under the google account. Calendar is not there either and the calendar won't sync.
Sent from my SM-G900T using XDA Free mobile app
Click to expand...
Click to collapse
That is because the sync functions are removed. Use the not-debloated version if you need this feature.
najoor said:
That is because the sync functions are removed. Use the not-debloated version if you need this feature.
Click to expand...
Click to collapse
Any chance you can give a location to just this apk? I really like the ROM but need Google Contact Sync.
pixeldrew said:
Any chance you can give a location to just this apk? I really like the ROM but need Google Contact Sync.
Click to expand...
Click to collapse
Alright. Download the non-debloated version from here:
http://forum.xda-developers.com/att...-g900tuvu1bnh5-ported-tmobile-rooted-t2900780
Unzip it and and look under system/app and system/priv-app. All the apks are there. Pick and choose whatever you want.
Please find at the URL below my copy of the stock ROM (Version C) for the D415, with my modifications included.
The D415 is a great phone for the price, and it came with many cool features. However, the phone still has an amateur streak running the stock ROM. Some of LG's apps are great on this phone, but some of them are downright useless for most of us. T-Mobile added their own pushy bloatware to the mix as well. The end result, as we all know, is a usually fluid, but at times clunky and awkward experience using the device. I was impressed the first day I had it, but I wanted to make it better that first day as well. I wanted to get rid of all the useless stuff, and polish it into something I wouldn't be embarrassed to pull out in front of a client. I liked a lot of what LG did here, and wanted to hold on to that, but I also wanted a few changes:
Root:
FOTAkill
SuperSU installed on first boot
Polish:
Small UI sounds changes
Boot Animation
Replaced Flashlight App (thanks to xbmi, consider a donation in the app)
Added Heads Up
Removed foo foo themes
Added Bookmarks Sync
Replaced Stock Messenger with AOSP MMS
Debloat:
LG Memo & Widget moved to user apps
LG Music & Widget moved to user apps
Visual Voicemail moved to user apps
Weather widget moved to user apps
Apps removed completely:
LG Contacts widget
TMobile TV
Lookout
CarrierIQ
Maps
Mobile Life
Streetview
Talkback
T-Mobile My Account
T-Mobile Name ID
Voice Dialer
Youtube
Amazon
Chrome
Cloud Print
Drive
Easy Home
Gmail
Google Plus
Google Calendar
Play News Stand
Play Books
Play Game
Play Movies & TV
Play Music
Google Search
Google TTS
Hangouts
Stock Calendar
To do:
AOSP Keyboard (IDK what I'm doing here yet. It's crashing when I put it in now).
Version E (need to learn how to extract KDZ)
Instructions:
Download zip to SD
Reboot to Recovery
Wipe Dalvik, cache, data, system.
Install zip
Reboot and enjoy
Thanks to @Daisuke1988 for the original flashable stock rom.
Feedback welcome in replies!
I just got this phone today. I hate it but this should make it much better. Thanks guys!!
Sent from my SGH-M919 using XDA Free mobile app
Keep poking around with it. There are a lot of hidden gems sprinkled in by lg that will really cause you to like this phone. I came off of a nexus 5 to this. I chose it for the price tag, you can't beat $7 a month and get the build quality and battery life. I would buy again. The only thing I miss is a decent camera. But the stock camera app helps with auto focus mode.
Will it work on d405?
catbro said:
Will it work on d405?
Click to expand...
Click to collapse
Good question, it would be nice
Sent from my LG-D405 using XDA Free mobile app
I guess I have to try this evening, if nobody's trying till then I will report back
If the pure stock ROM works in the 405, this one should as well. I'm not sure myself without looking it up.
I have a D41510c and when I tried to install this rom, it failed. I'm restoring a backup, but I will try again in a while.
Sorry to hear that, I tried very hard to make the cuts fine in this. Without further info I'm gonna guess the download got corrupted. The zip itself is really straightforward (simple script, boot and system imgs.) The only part I would have thought would have failed the installer was that I repacked the system IMG (saved a few hundred MBs) instead of simply unmounting it after my changes. Otherwise, if its going to break, it should be upon first boot. Let me know what happened if it doesn't work again.
jb3p76 said:
Sorry to hear that, I tried very hard to make the cuts fine in this. Without further info I'm gonna guess the download got corrupted. The zip itself is really straightforward (simple script, boot and system imgs.) The only part I would have thought would have failed the installer was that I repacked the system IMG (saved a few hundred MBs) instead of simply unmounting it after my changes. Otherwise, if its going to break, it should be upon first boot. Let me know what happened if it doesn't work again.
Click to expand...
Click to collapse
I'm re-downloading, hopefully this will work!
I can deodex this but you will have to wait till Tuesday for me to upload it. or is it already deodexed?
I had thought about it but honestly haven't learned how to yet. Was I mistaken to think the payoff would not have been that great? Either way, I can wait til Tue, I know others will want it deodexed. Thanks!
I tried again, but it failed...
E:Error executing updater binary in zip
E:Unable to mount '/system'
EDIT: I was able to boot into the rom, but it's extremely slow
Wondering if it has to do with first botched install now that it went. Were you able to format /system again? My other thought was repairing permissions. When it failed the first time, was it before "Setting permissions for root" was displayed? If so it was in the middle of flashing /system. I flashed this on mine using twrp. IDK that I will be much help but I think if we can figure out the variables Google should at least point us in the right direction...
Before I get too far down the rabbit hole can anyone confirm they have successfully flashed this and its working out for them?
jb3p76 said:
Wondering if it has to do with first botched install now that it went. Were you able to format /system again? My other thought was repairing permissions. When it failed the first time, was it before "Setting permissions for root" was displayed? If so it was in the middle of flashing /system. I flashed this on mine using twrp. IDK that I will be much help but I think if we can figure out the variables Google should at least point us in the right direction...
Click to expand...
Click to collapse
Well, I rebooted and it's faster now. I used towelroot to get root. Nohing appeared about the permissions. I was able to update the binaries using TWRP.
It's should have already had root and SuperSU installs on first boot. Did that not happen? I'm glad your phone is doing better! So many weird things going on there!
jb3p76 said:
It's should have already had root and SuperSU installs on first boot. Did that not happen? I'm glad your phone is doing better! So many weird things going on there!
Click to expand...
Click to collapse
I use ROM Toolbox Pro, and when I went to start it the first time, it said root check had failed. That's why I used towelroot. I'll continue to test things and report back to you. So far, it's pretty smooth.
Weird. Can you tell me if the SuperSU apk is to be found in /system/apps/bootup?
I'm doing a backup so i can wipe and install fresh again. I'd like to mess around with the root stuff and see if I can figure that out. Did you happen to get a listing of which files are missing?