Chances of Sprint LG getting a custom ROM

Chances of Sprint LG getting a custom ROM - Sprint LG G4

are probably slim to none. I've been following for quite some time and considering making a switch to Nexus. Anyone else on the same boat?

chirayu said:
are probably slim to none. I've been following for quite some time and considering making a switch to Nexus. Anyone else on the same boat?
Click to expand...
Click to collapse
was gonna upgrade my note 2 to this... guess i'll be holding on to it for a while. got a nexus 6 on verizon so i don't want another, not that i don't love it, cause i do!

I've been between AOSP, AOKP, Cyanogen, Omni, PA, various unicorns, so on and so forth, on several different phones, including the original G... It's a shame that we may never get a bootloader unlock and TWRP, but honestly, I'm perfectly OK with the (rooted) stock ROM. In my experience, the phone is liquid smooth, fast, has decent battery and the UI doesn't look bad. Root fixed almost every issue I've had with this phone (bloat, low headphone volume, ads...)

I am regretting everything about this purchase. If people don't give up on the sprint variant there will probably be ROMs eventually but it is going to be 6 months at least I bet and by then people start to lose interest and move on to something better.
I will just say to use this as a lesson to prepare yourself. I am guessing it will be harder and harder to root and ROM phones in the future. I see the same path that happened with gaming consoles. Lots of different ways to exploit them. Then a next gen comes on and more difficult ways. Then updated versions come out that make it extremely hard. Then a next gen comes out and it is impossible.
The same thing is happening with phones.

When i get time, i will be putting out a customized Stock ROM, like i did for the G2. I still need to make a final version for the G2, then i will concentrate on the G4. There will be several versions, but i would like to wait till we get an updated system to fix the vulnerabilities present. (As long as they don't kill our root method).
The bad part, is since we don't have a recovery option, we will have to flash via the command tool (that we used for root).

Agimax said:
When i get time, i will be putting out a customized Stock ROM, like i did for the G2. I still need to make a final version for the G2, then i will concentrate on the G4. There will be several versions, but i would like to wait till we get an updated system to fix the vulnerabilities present. (As long as they don't kill our root method).
The bad part, is since we don't have a recovery option, we will have to flash via the command tool (that we used for root).
Click to expand...
Click to collapse
It might be able to be done with FlashFire.

Agimax said:
When i get time, i will be putting out a customized Stock ROM, like i did for the G2. I still need to make a final version for the G2, then i will concentrate on the G4. There will be several versions, but i would like to wait till we get an updated system to fix the vulnerabilities present. (As long as they don't kill our root method).
The bad part, is since we don't have a recovery option, we will have to flash via the command tool (that we used for root).
Click to expand...
Click to collapse
Looking forward to the ROM. Thanks for the work.

please explain headphone volume fix. and what bloat software you have removed successfully..thanks so much

Related

Rooting NIGHTMARES!

Hi all,
So my Nexus 4 arrived today and I'm umming and ahhing as to root or not.
I've heard all the good things about doing it but I'm interested in peoples rooting nightmares. What's gone wrong? When have you wanted to throw your phone out the window?
Look forward to reading!

noahdev said:
Hi all,
So my Nexus 4 arrived today and I'm umming and ahhing as to root or not.
I've heard all the good things about doing it but I'm interested in peoples rooting nightmares. What's gone wrong? When have you wanted to throw your phone out the window?
Look forward to reading!
Click to expand...
Click to collapse
It really takes a tremendous effort to screw it up, it really does.
Cliff's Notes/summary, not an actual guide:
1. Learn to do it the old fashioned (and easiest way) by installing the drivers and using fastboot.
2. fastboot oem unlock
3. fastboot flash recovery recovery.img
4. flash your SU binaries zip
5. b00m!

CMNein said:
It really takes a tremendous effort to screw it up, it really does.
Cliff's Notes/summary, not an actual guide:
1. Learn to do it the old fashioned (and easiest way) by installing the drivers and using fastboot.
2. fastboot oem unlock
3. fastboot flash recovery recovery.img
4. flash your SU binaries zip
5. b00m!
Click to expand...
Click to collapse
In that case I'll lower my requirements. Anyone done it and thought 'You know what, I prefer the stock experience.'?

noahdev said:
In that case I'll lower my requirements. Anyone done it and thought 'You know what, I prefer the stock experience.'?
Click to expand...
Click to collapse
Yes actually. I thought rooting it was great and all, even went for custom kernels. The thing is, when you get all the updates that Google provides on a near instant basis, there is no need to root and rom your phone. Also, I feel like it doesn't provide too much extra for the experience. On a side note, when I had an HTC Sensation, I would root and rom just to get the newest and greatest from Google.
Your choice, but I like getting OTA's and don't run any SU apps.

Drebin 894 said:
Yes actually. I thought rooting it was great and all, even went for custom kernels. The thing is, when you get all the updates that Google provides on a near instant basis, there is no need to root and rom your phone. Also, I feel like it doesn't provide too much extra for the experience. On a side note, when I had an HTC Sensation, I would root and rom just to get the newest and greatest from Google.
Your choice, but I like getting OTA's and don't run any SU apps.
Click to expand...
Click to collapse
Rooting means you are:
- able to make nandroid and Titanium Backups
- run a good custom kernel for color and sound control, better batterylife and performance and lower cpu temperatures
- install adblockers and other usefull apps.
If these aren`t improvements i don`t know what is and you might as well buy an iPhone for stock xperience, just my 2 cents.
BTW: @OP: rooting nightmares only occur with mis and badly informed users.

gee2012 said:
Rooting means you are:
- able to make nandroid and Titanium Backups
- run a good custom kernel for color and sound control, better batterylife and performance and lower cpu temperatures
- install adblockers and other usefull apps.
If these aren`t improvements i don`t know what is and you might as well buy an iPhone for stock xperience, just my 2 cents.
BTW: @OP: rooting nightmares only occur with mis and badly informed users.
Click to expand...
Click to collapse
Yes, but I feel like I don't need them on my phone. I don't need to back up apps as I am not switching roms, I like getting the OTA updates, and I don't care about ads on mobile because I never see them anyway, either through paid apps or little browsing.

Drebin 894 said:
Yes, but I feel like I don't need them on my phone. I don't need to back up apps as I am not switching roms, I like getting the OTA updates, and I don't care about ads on mobile because I never see them anyway, either through paid apps or little browsing.
Click to expand...
Click to collapse
Too each his own bro

I fully agree to each his own but if you do not see the advantages and personalization rooti g gives you then most likelyyou are the type tthat is satisfied with what you get. For me T9 calling alone is worth it, adjusting scree colors, raising the sound level,showing actual dBm signal strength, removal of all apps I don't want that were preloaded, darker ui experience. Now if you never try this then you wont miss it but its not lime you can't root it then unroot if you are not happy.
Bottom line updates will come the same day here whether rooted or not and these updates can also come with goodies...
Edit: Also lets be honest in a forum of 100.000's of members and rooter you will find maybe a few hundred or so that may have an issue and most of them I guarantee you was because of them not following directions properly. Thats what makes for rooting nightmares. Remember even non rooters from time to time have to restore their phones for one crazy reason or another. Now you have to restore back to 1 year ago when you first got the phone...SMH

I am having some trouble rooting and puting a custom recovery on my new Nexus 4, I unlocked the bootloader, and flashed the custom recovery through fastboot, but its not sticking, I don't know whats wrong.

UNless youir getting deadlocks letting your phone charge overnight, I would stay on stock.
CM is great, but there are just always broken things and bugs that will eventaully piss you off when you want to do something.

noahdev said:
Hi all,
What's gone wrong?
Click to expand...
Click to collapse
Absolutely nothing, except for the very slight inconvenience of having to re-root or re-install TWRP after doing an Android operating system OTA update. Not only that, but I now have several "root only" apps that I needed, I have full access to the Linux command line programs which I use, and I am learning a lot about the Android OS lower level stuff. For me anyway, I really have no desire to install custom ROMS, as stock rooted Android does everything I want it to do.

There are stock based custom roms with CM type customization's... Again unless you have tried a stock customized rom with advancements you should not be judging. Also you don't have to use each cutsomization you can actually leave it stock and only use 1 or 2 custom items. Check out PSX 4.1 bone stock with a handful of customizations

There is really only one thing that annoys me about stock and that is the oversized Nav bottons. I just wished they made them smaller or gave us the otion to change the size. This is available on custom Roms and gives you more screen real-estate which definitley makes a difference.
That is one thing that keeps pulling me to custom Roms. I was running AOKP which seemed to run pretty good. I restored my phone back to stock because I thought I was having an issue with the notification light but then saw it just needed an app to make it work the way I was expecting it to.
So I have my phone rooted on stock 4.3 right now and I just wish I can make those Nav bars smaller! There are definitley cool features on some of the custom Roms though and it most certaintly can enhance your experience.

If ur not using the toolkit, then you should be.. If ur using and still manage to screw things, you should leave ur phone stock... The toolkits are already noob proof..
Connect phone to PC
Unlock boot loader
Root
Install recovery
Install ROM....
Its all 1 click each or some toolkits does it all in 1 click...
Rooted and running Paranoid Android + franco.kernel

my nightmare came from me going to fast... i missed a step and screwed up my phone...
i was able to get a stock image and reflash it, but it was a grueling 2 hours with a soft-bricked phone.
read all the stuff you can, and don't rush it.

Lucke said:
my nightmare came from me going to fast... i missed a step and screwed up my phone...
i was able to get a stock image and reflash it, but it was a grueling 2 hours with a soft-bricked phone.
read all the stuff you can, and don't rush it.
Click to expand...
Click to collapse
Please don't take this the wrong way... but you being the only person with a real horror story is quite comforting!

noahdev said:
Please don't take this the wrong way... but you being the only person with a real horror story is quite comforting!
Click to expand...
Click to collapse
no offense taken thats what i get for trying to root it while at work dealing with an Exchange upgrade

You can't really screw up a nexus device. It's not like Samsung where you hard flash the wrong version for the wrong phone and end up with a paperweight. If you mess up with nexus you can always return back
Sent from my Nexus 4 using Tapatalk 4

My last nightmare with rooting was from htc desire hd, lots of bullcrap to be done, lots of s**t pre requisite..goldcard, emmc etc., ugh gives me headaches for days :/

Just use wugfresh toolkit and its a breeze
Sent from my Nexus 4 using Tapatalk 4

I purchased the HTC one from a sprint store. It is the M7_wls hboot 1.44.00. I promptly rooted it by unlocking the bootloader with fastboot and installed TWRP and cyanogenmod 10, since I used and loved cyanogenmod7 for 3 years on my EVO before physical damage and processing inferiority finally made me throw in the towel. It was perfect. beautiful. best device and ROM combo I ever saw. The HTC one and cyanogen 10: a match made in heaven. But then, quite unexpectedly, after allowing the phone to die on a job site one day, it would not take a charge. The good news is that sprint will not attempt to open the phone and so no unrooting was necessary to replace it. In fact they did it there in the store since I was within fourteen days of the original purchase date. No removable battery! It was their contention, and I tend to agree, that it simply became unseated within the case, although I hadn't dropped it. fine. new phone. I once again unlocked the bootloader and installed TWRP and cyanogenmod 10. used it for a day (which was quite cold and humid, but I was inside primarily) and the audio stopped working. No music, no in-call audio. While frantically texting customers, I managed to download the nightly cyanogen update and flash it. My in-call audio came back, but ringtones, notifications, music, games and all other possible audio remained null.
I unrooted it by running the RUU in a virtual machine (I use a mac) and, even returned to stock, no sound. In-call audio remained (thank god). I took it in again and after the obligatory sea of clerical errors, sprint ordered me a new one. I really don't want to go through this again. I love the phone, but business is suffering. Is it possible that either of these issues were my fault? I've heard the inside of the M7 is quite convoluted and littered with coaxial cables like older HTCs and I did drop the second one twice. It had a nice case and simply slid out of the angled, inside breast pocket of my coat maybe three feet onto the floor each time. No such occurrence on the first. It makes sense what some are saying that the sound card simply became disconnected inside the case, but now I'm wondering if I'm mussing the root up somehow. My new phone will be here in a few days and I'm simply never going to use Sense 5. I'd rather eat discarded blowpops out of a sandbox. How can I make sure this doesn't happen again? Is it possible that these are both hardware defects and I'm the most unlucky customer ever? I see minimal cases of the latter issue occurring on the stock ROM, but it does happen. Usually it is fixable however. Mine was definitely not. Are these phones as unreliable as they have been for me? They seem to really impress even the picky crowd, so I'm thinking no. Help! Were these really both hardware issues, or did I mess them up?

Longest post I've ever seen. LOL
Sent from my HTCONE using Tapatalk

I would unlock, root, and S-off your new device as soon as you get it, and try something different. CM10 is pretty outdated as it is, and even if you are hesitant to go to a newer version for fear of having a less stable experience, there are plenty of 10.2 ROMs that should be stable. Not only that, but there are numerous stock-based ROMs that will offer a great user experience with the ability to disable sense or remove it completely. RENOVATE is a great choice for that sort of experience. If you are looking to try something new, my latest build of Beanstalk is 4.4.2, CM based, and offers a lot of custom features not found in most other ROMs here at M7SPR. It does have some small bugs here and there, but nothing that impedes your ability to use it as a daily driver. Not pimping my own build, mind you, just offering options. So, give something new a try and hope for the best is my advice. Oh, and try harder not to drop the damn thing.
Happy Holidays!

derp
elvisypi said:
Longest post I've ever seen. LOL
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
Yeah, sorry for the verbosity. I think I may have a problem 19th century British dramas.

hey thanks!
BMP7777 said:
I would unlock, root, and S-off your new device as soon as you get it, and try something different. CM10 is pretty outdated as it is, and even if you are hesitant to go to a newer version for fear of having a less stable experience, there are plenty of 10.2 ROMs that should be stable. Not only that, but there are numerous stock-based ROMs that will offer a great user experience with the ability to disable sense or remove it completely. RENOVATE is a great choice for that sort of experience. If you are looking to try something new, my latest build of Beanstalk is 4.4.2, CM based, and offers a lot of custom features not found in most other ROMs here at M7SPR. It does have some small bugs here and there, but nothing that impedes your ability to use it as a daily driver. Not pimping my own build, mind you, just offering options. So, give something new a try and hope for the best is my advice. Oh, and try harder not to drop the damn thing.
Happy Holidays!
Click to expand...
Click to collapse
Thanks for the advice!:highfive: Out of curiosity, why do you say to get s-off instead of just HTCdev unlock? Also, I find alot of files that I assume are for the m7wls with m7spr in the title. I don't really not follow most of what people have posted about the different modes and titles, but I gather that as long as the ROM says m7 and is a CDMA version I'm good? I'm going to superglue this new one to my hand. not really. I need to be more careful though. never had a nice phone before. I would like one that has kitkat... I never had that phase of, "I hope I don't mess my phone up," with the EVO, but I like the one so much that I find I'm apprehensive about ROMs now. For the sake of calming my paranoia, what do you think the likelihood is that either of those issues had to do with CM10? It feels low to me since I unrooted and the problem persisted on the second one. Do you use your kitkat mod? I kinda do want kitkat and I'm such a fan of CM. admittedly partially because I like the color, but still. I like it. Where can I download?

[FAQ] Jan 2014 Bionic handbook

I've noticed that some new people are still trickling in to the Bionic scene, and stumble over old/outdated guides, ROMs, root methods, etc. So I figured I'd post up a refresher on the current state of things. Hopefully this is more helpful than spamful.
(this is the first time I'm writing one of these posts, so please judge hard
TLDR tips:
HDMI can only be used on Stock based ROMs, or alternatively in AOSP ROMs by installing the JBX-kernel.
You must use Linux, or a Virtual Machine running Linux (easy method) to root JB (though there is apparently one other way using safe root).
ROMs that predate the JB update won't boot on JB firmware.
Bootstrap will (soft) brick a Bionic on JB firmware.
The Bionic is locked, we use "SafeStrap" as our recovery to install ROMs, flash zips, etc.
Downgrading below JB is not (yet) possible. Maybe one day, but I don't cross fingers.
House of Moto is your (soft) brick buster, RSD alternative for clean wipes, upgrade tool to JB from ICS/GB.
Firmwares / Moto updates / Android Versions
There have been just a few official updates from Moto for the Bionic, and none have been reversible (excluding some ICS leaks). The current most updated official version is moto-98.72.22 on android-4.1.2 or Jelly Bean. Updating to JB will cause removal of any previous root access.
A much easier way to update is to use the House of Moto; it'll perform a FDR and optionally wipe your SD card, but it is the easier/more thorough/recommended update path.
Current official update : cdma_targa_9.8.2O-72_VZW-22_cfc.xml.zip
md5sum : 1481ac6035682b732f76a621a36a9153
Info about other firmwares/updates/OTAs (.905, .2233, .232, .246 FXZs)
The Bionic has had a number of updates, some official and some leaked. There was a security change during its course of history, and because of it we are not able to downgrade the firmware after a certain point.
You may find some threads lingering around about old updates and OTAs. Here is a bit of info about them, in chronological order (or at least to the best of my knowledge).
GB
Blur_Version.5.9.902.XT875.Verizon.en.US FXZ
Blur_Version.5.9.905.XT875.Verizon.en.US.zip OTA
ICS leaks
232
235
238
6.7.242
6.7.244
ICS
Blur_Version.6.7.246.XT875.Verizon.en.US FXZ
JB
Blur_Version.98.72.22.XT875.Verizon.en.US FXZ
twinkyz1979 outlines which versions can downgrade back to 905 and below here.
Basically, there was a change in some security code between the leaked firmwares .232 and .235. Before this change, the Bionic was able to jump back and forth from 902 to 232 and between. Once the Bionic is updated to 235, it is not able to go back down any more, and can only go up on each firmware.
Root
A thread here detailing the easy method, using a VM by marty45714
Thread describing the Linux-only method, for native *nix users
As of this post, there is only one root method for Bionics on the official JB firmware. The method requires a Linux installation, and uses a samba share exploit. There is NO way to get around this requirement, though it is possible to run a Virtual Machine on top of Windows to achieve this.
An alternative way to root may be to use "safe root". I am unfamiliar to this method and haven't tried it myself. A youtube video shows the process. I haven't come across any threads detailing any further (feel free to tip me if you find any).
Recovery / Safestrap
You can get it from Hashcode's website.
We used to have a tool around called Bootstrap, but it does not work with the current JB update so please do not try it on JB. It will cause a (soft) brick and other messes.
Safestrap is a work around for our locked bootloaders. Once you install it, you have the option to make up to 4 "safe" slots to flash ROMs to. It's comparable to dual-booting. Although it is possible to flash ROMs over your stock/"unsafe" slot, it's unnecessary and dangerous (in my opinion, of course).
The slots reside on your internal-SD, and can each have your choice of 2/3/4 GB in size of a Data partition (for app installs).
ROMs
This section can sort of be divided into 2 subsections; Blur/stock based ROMs and Kexec/AOSP ROMs
Kexec ROMs do not (yet)can now support HDMI (not docks?) with the help from a kernel. Webtop is not found on these ROMs.
Kexec ROMs can be more or less stable than Stock ROMs, but usually contain more experimental and reversed code.
As far as loading pre JB Kexec ROMs onto a JB Bionic, I've never wondered about that until this moment. If anyone knows, please let me know.
-----
Stock ROMs cannot be updated/based on a version of android that Moto has not updated us to (nothing greater than 4.1.2 JB as of this post).
Stock ROMs are pretty likely to be your stable ROMs, being mostly based on moto's code and not so much including experimental code.
There are still some GB/ICS stock ROMs that are floating around, and these cannot be loaded onto a Bionic that is updated to JB.
Stock ROMs can use the HDMI port and docks.
Kernels
A third-party kernel can be loaded with some AOSP ROMs to add/change features. A project called JBX-kernel is being developed by dtrail1 for 4.4 ROMs and is aimed primarily at low power consumption, while having options for performance as well.
House of Moto
A guide written by bigv5150 (Windows/Linux/Mac)
It is posted in the droid ultra forums, but can apply to the Bionic. The root method (if still included) will not work on JB Bionic.
A very handy tool, put together by SamuriHL. If you find yourself stuck with a non-booting Bionic, this is your next step. It is also handy for completely wiping your Bionic (think FDR but for all partitions in the phone) (this wipe will erase root).
If you need to use this tool, you're expected to read all the instruction before downloading, reading the instruction again before launching it, and reading the instruction while using it just in case. You can mess some things up using this tool, and you can clean some big messes with it as well. Pretty much every question about using it has been asked and answered already. Tread carefully my friend
Verizon alternatives
I haven't played in this area yet, but I may be soon.
So far I've seen people use their Bionics on pageplus, cricket, T-mobile, and I've seen efforts for getting on Boost mobile and at&t. But I don't know much about this.
Some helpful links :
Patch to fully enable GSM on Verizon CDMA Android phones
Thanks to bedwa for the tip
If any thread or download links become dead, let me know. I have found many alternates, made copies, and have backed up and stored most Bionic related material I've come across, except for most ROMs.

I thought I'd list some ROMs here, divided by their status (Stock vs Kexec). These are (semi) current, and you should be able to find these and load them up on any Bionic updated to stock JB :
Stock based
RAGING BIONIC
Blurry
Call of Droid
FlyingJelly
Gameblur
Revolution-Unleashed
Kexec
Cyanogenmod
Cool Blu
Eclipse v5
LiquidSmooth
CyanFox
Avatar
PACman
CarbonRom
Mokee OpenSource
Gummy
AOKP
Thanks to KenanAlcorn for the tips
Basically, if you see "Stock / moto / no gapps needed" then its a Stock based ROM. (webtop, docks, hdmi)
If you see "Gapps / CM / AOSP / AOKP / Kexec " or an android version number > 4.1.2 then it's a Kexec ROM. (no webtop, docks, hdmi).
I'd be happy to add links, if they would be helpful to any one. Though I don't want to upset anybody. Some ROMs are released exclusively on some forums, in order to keep a hold on issue tracking and other such things. If you see this, I'd be glad to link to any ROMs with permissions.

Great post for the bionic noob!
Sent from my KK DROID BIONIC using my fingers

Thanks for this, I'm sure it will help out a lot of bionic beginners. A few KEXEC ROMs you could add to that list are Mokee OpenSource, Gummy, and AOKP.

chrisp6825 said:
Verizon alternatives
I haven't played in this area yet, but I may be soon.
So far I've seen people use their Bionics on pageplus, cricket, T-mobile, and I've seen efforts for getting on Boost mobile and at&t. But I don't know much about this.
Click to expand...
Click to collapse
As long as things are done right, running it on AT&T is no issues whatsoever.
You follow the instructions in the Q&A section (Root, NV edit and Prop Edits) I have been using CM 11 with no issues, tethering the whole 9 yards.
I Flash this zip Here. This Zip is GOLD.

Thanks for this! Great post
XT875 Running CyanFox

Thanks! I recently reset my computer and lost all of the settings I had when I first rooted my Bionic. This is a great thread to help if that were to happen again!

This will sound weird, but I'm one of the guys that NEVER got the official JB firmware from Verizon. And I'm running SlimKat just fine through Safestrap ROM slots, and my last official firmware is the official ICS release.
Right now I have 3 slots
Stock = Technically Icarus HD, but it's still based on stock
Slot 1 = My "daily driver" Cyanogen MOD 10, NOT the latest (I think I'm still on 10.1.2 when they're up to 10.2.1 already)
Slot 2 = SlimKat, not the latest either, I think it's a beta from February 2014.
I switch among them "at will" via Safestrap, and I got SlimKat pretty dialed in now.
So if people are having problems upgrading to JB... Or problems with firmware after JB OTA, perhaps they shouldn't do it, and just live with the previous firmware? What are the potential problems?

kschang said:
So if people are having problems upgrading to JB... Or problems with firmware after JB OTA, perhaps they shouldn't do it, and just live with the previous firmware? What are the potential problems?
Click to expand...
Click to collapse
As far as I can tell, there are no true benefits to upgrading to JB, as opposed to staying on ICS. Any benefits can easily be found in a CM based ROM (now are fairly stable, even on 11/Kk).
But just to clarify, once you begin the JB upgrade process, you most likely cannot abort or undo it. You risk a great chance of messing the flashing process up and potentially bricking.
If the upgrade completes, you most certainly cannot go back to ICS (as of yet).
(All in regards to the official moto upgrades, JB, ICS, etc)
Sent from my XT875 using Tapatalk 2

Yeah, that's what I figured. Since I'm KEXEC'ing SlimKat I see no reason to do the official JB upgrade at all. My ROM at the time was to customized to run the FXZ upgrade.
There are a few things to note:
1) Only stock based ROMs have dock support... ANY dock support. That includes HD dock, Nav Dock, clock/desk dock, etc.
HashCode said NavDock was on the todo list for CM10 for MONTHS... until Bionic fell off the scope. So I guess that's our "last best hope".
You can work around the Nav Dock by having in-car bluetooth autorun the car mode app. Not as convenient, but tolerable.
2) Only stock based ROMs have WebTop support... if any one still use that.

CM11 NavDock DOES work
kschang said:
...
1) Only stock based ROMs have dock support... ANY dock support. That includes HD dock, Nav Dock, clock/desk dock, etc.
HashCode said NavDock was on the todo list for CM10 for MONTHS... until Bionic fell off the scope. So I guess that's our "last best hope".
You can work around the Nav Dock by having in-car bluetooth autorun the car mode app. Not as convenient, but tolerable.
...
Click to expand...
Click to collapse
There was a commit back around 04/08/2014 that enabled USB analog dock audio for OMAP4; there was another dock-related OMAP4 commit on 04/06/2014 as well. Since the 04/09/2014 nightly build on CM11, my Moto NavDock works - the phone automatically recognizes NavDock insertion and opens my chosen car mode app (I use IBolt as my dock screen software), and closes out from it upon removal. Audio via the dock's split USB cable functions as well. The phone successfully recognizes and sets car mode (seen in notifications), but you need a program installed to handle car mode, as otherwise it does nothing.

Shakkuras said:
There was a commit back around 04/08/2014 that enabled USB analog dock audio for OMAP4; there was another dock-related OMAP4 commit on 04/06/2014 as well. Since the 04/09/2014 nightly build on CM11, my Moto NavDock works - the phone automatically recognizes NavDock insertion and opens my chosen car mode app (I use IBolt as my dock screen software), and closes out from it upon removal. Audio via the dock's split USB cable functions as well. The phone successfully recognizes and sets car mode (seen in notifications), but you need a program installed to handle car mode, as otherwise it does nothing.
Click to expand...
Click to collapse
I noticed that the 4/15 nightly of SlimKat does this too. May have to revise my statement.

A couple notes on hardware...
1) It is possible to replace the trim piece (that metalic looking cover on top that goes around the screen and buttons, has the Verizon logo), you can often find it on Amazon or eBay, but it's a pretty involved process as it uses a trimmed sheet adhesive. Probably not worth the effort, just put a case on it.
2) I got the Diztronic case that fits the extended battery. Fits like a glove, cheap (about $10) feels grippy and pliant, doesn't add too much bulk (still fits into docks).
3) You can get super-extended battery that's even bigger than the BX8 extended battery, but those often requires its own battery back, and thus no longer fit into docks. If you have no docks this doesn't affect you much, except those super-sized setup are too big to fit into belt cases and such, so you'll have to carry the phone naked, and the battery backs often comes with bad tolerance problems. I bought one and I had to sand down a lot of areas to get it to fit properly.
4) If you have the extended battery, your best option for belt case is... wait for it... a Mophie Juicepack Belt Case for iPhone 5, available at most Best Buys for $29.95. It's designed for iPhone 5 with the extended battery case by Mophie, but it fits the Bionic quite well. Your other option is order one of those (p)leather cases off Amazon. There's one that has the clip AND two belt loops for under $10, and it fits surprisingly well.
5) The best car dock is still the Moto NavDock.

Very useful to me,thanks a lot.
从我的 XT875 上通过 xda-developers.com 发送 powered by appyet.com

Just wanted to note, I've moved much of my focus to a new device (moto x), and won't be paying full attention to the Bionic development anymore.
I do still have the device and am planning to use for a project in the future, although it's battery is seriously shot (wont hold a charge for more than 7 hours, even with screen off the whole time).
I still checkout the various forums I used to frequent over the years, but I know that will become less and less over time.
If anyone spots any out-dated info in this thread, please feel free to post here or PM me to let me know, and I'll update the original posts. I'm glad this thread was able to help a few people, and I hope it continues to help long after activity dies and info is buried.
Live long Bionic scene, the most helpful/entertaining/surprising phone group I've been a part of. lol

chrisp6825 said:
Just wanted to note, I've moved much of my focus to a new device (moto x), and won't be paying full attention to the Bionic development anymore.
I do still have the device and am planning to use for a project in the future, although it's battery is seriously shot (wont hold a charge for more than 7 hours, even with screen off the whole time).
I still checkout the various forums I used to frequent over the years, but I know that will become less and less over time.
If anyone spots any out-dated info in this thread, please feel free to post here or PM me to let me know, and I'll update the original posts. I'm glad this thread was able to help a few people, and I hope it continues to help long after activity dies and info is buried.
Live long Bionic scene, the most helpful/entertaining/surprising phone group I've been a part of. lol
Click to expand...
Click to collapse
Thanks again for doing this, you may be moving to greater things but your legacy lives in the Bionic forums :good:

Confirm Alt Root Method
Root
A thread here detailing the easy method, using a VM by marty45714
Thread describing the Linux-only method, for native *nix users
As of this post, there is only one root method for Bionics on the official JB firmware. The method requires a Linux installation, and uses a samba share exploit. There is NO way to get around this requirement, though it is possible to run a Virtual Machine on top of Windows to achieve this.
An alternative way to root may be to use "safe root". I am unfamiliar to this method and haven't tried it myself. A youtube video shows the process. I haven't come across any threads detailing any further (feel free to tip me if you find any).
Click to expand...
Click to collapse
I just wanted to confirm that the second method in the Rootjunky YouTube video above does work as advertised. Much simpler than setting up a Linux VM. Thanks for all of the info.

I think towelroot was also reported to work. IIRC, it is for Android 4.4.2 and lower.
edit: ok, maybe not - I just tried it on one. (unless there is a modstring you can enter in the app in the place you enter those to get it working on this phone)

there was a time when I felt like I knew all there was to know about the Bionic...3 phones later, i don't remember so much about the early days. I have a bionic on .905 (as to preserve the original web top). I probably have to keep it on crap software, which is ok. I want the appropriate version of Eclipse (for that many moons ago, i think 6/2012) os I can at least have a custom rom that supports web top/hdmi dock/car dock/wireless charging. i honestly just found out today that the bionic works with it...and picked up the back for $5 on ebay. :0 anyway, My question that i do not remember the answer to is what versions of safestrap can i use and stay on .905 . the newest one (1/2015) would be awesome, but somehow, i doubt that works. I don't want to make the only Bionic i still have on GB a sacrificial experiment, but at the time i left it on .905, i had 3 bionics and there was a reason i didn't upgrade safestrap. i just can't find and don't remember why. anyone have a copy of Eclipse? thank you!!

kitcostantino said:
there was a time when I felt like I knew all there was to know about the Bionic...3 phones later, i don't remember so much about the early days. I have a bionic on .905 (as to preserve the original web top). I probably have to keep it on crap software, which is ok. I want the appropriate version of Eclipse (for that many moons ago, i think 6/2012) os I can at least have a custom rom that supports web top/hdmi dock/car dock/wireless charging. i honestly just found out today that the bionic works with it...and picked up the back for $5 on ebay. :0 anyway, My question that i do not remember the answer to is what versions of safestrap can i use and stay on .905 . the newest one (1/2015) would be awesome, but somehow, i doubt that works. I don't want to make the only Bionic i still have on GB a sacrificial experiment, but at the time i left it on .905, i had 3 bionics and there was a reason i didn't upgrade safestrap. i just can't find and don't remember why. anyone have a copy of Eclipse? thank you!!
Click to expand...
Click to collapse
Newest safestrap has to have jellybean kernel don't flash it, stay on the 3. X that your on, no need to update I miss webtop2 so bad
Sent from my Z970 using XDA Free mobile app

OverClocking Kernel

Hi,
I have an ASUS TF701T (K00C) Tablet, with Jelly Bean v4.3.
It is Rooted and has CWM Recovery installed.
The SETTINGS >> ABOUT screen reads as follows:
Kernel Version:
3.4.57-g15e4406
[email protected] #1
Build Number:
JSS1SJ.US_epad-1.0.26.1.7.20131108020115_2013.10210002
I am not a developer, nor a programmer, so I need like a file (Zip, or whatever) and a method to install it.
Pershoot gave me this link:
https://github.com/pershoot/android_kernel_asus_tf701t
...but I can't make any sense of it. I don't know what all of those files are.
I can follow instructions. I've Rooted and installed Recovery on a number of devices and Kernels on a couple of them as well. But there was always a file and instructions. Like "Install from Zip" in Recovery, or sideloading with ADB (command line provided).
Can anyone please help me? I would really love to get this done!
THANK YOU IN ADVANCE!!!

Thats the kernel source ya?
Try this tutorial if you want to build your own kernel. Looks promising.
http://forum.xda-developers.com/sho...mctr=(not provided)&__utmv=-&__utmk=198280108

YayYouFixedIt said:
Thats the kernel source ya?
Try this tutorial if you want to build your own kernel. Looks promising.
http://forum.xda-developers.com/sho...mctr=(not provided)&__utmv=-&__utmk=198280108
Click to expand...
Click to collapse
I don't want to build my own kernel. That was the point of my post.
Not everyone wants to build everything they use from scratch. That's why Dominos & Dell are both so succesful.

There are only 3 custom roms out there for this device and they use the CM11 kernel or repacked stock kernel.
Nobody has released a custom kernel for this tablet, so if you want an OC kernel, you will HAVE to build it yourself.
Or be patient....
BTW, before you install any custom software you should upgrade to the .18 bootloader. Each of the 3 custom Roms requires it and if somebody builds a custom kernel it will most likely be designed to run with the latest bootloader and those roms.
Sent from my ASUS Transformer Pad TF700T using Tapatalk

Tbh I don't think this device needs much OC right now and there is no way of doing it without rebuilding the kernel. I have no idea how to add OC to the source other than look at how _that did it using clemsyn's hack. That may not even work.
I wouldn't count on it soon. It's not high priority right now.

berndblb said:
There are only 3 custom roms out there for this device and they use the CM11 kernel or repacked stock kernel.
Nobody has released a custom kernel for this tablet, so if you want an OC kernel, you will HAVE to build it yourself.
Or be patient....
BTW, before you install any custom software you should upgrade to the .18 bootloader. Each of the 3 custom Roms requires it and if somebody builds a custom kernel it will most likely be designed to run with the latest bootloader and those roms.
Sent from my ASUS Transformer Pad TF700T using Tapatalk
Click to expand...
Click to collapse
Okay, I don't know what a ".18 Bootloader" means, but like I said, I am not a programmer by any means. I can follow instructions, ya know?
Let me tell you my experience...
I have overclocked four devices in the past. In each instance, it was a very simple procedure, laid out step by step by whomever made it available. I had used both Pershoots Kernels and one called an "A1", for my old Glxy Tab 10.1".
It was only a few steps. And I didn't do it as part of a ROM or anything. In fact, in every case (except with my Note 2), I ran the Factory ROM on each device, Rooted.
Don't get me wrong, I'm not knocking anyones efforts in creating ROMs. Everyone likes what they like. For me, I like TouchWiz and I like the Asus unterface (whatever it's called) and I do not want to change them. Besides having to wipe my device every time I update a custom ROM, which I don't have to do with the Factory ROM, as it will always upgrade without wiping my data, it's a lot of work to to the next Android, without using another custom ROM. With the Factory ROM, I can unroot and even get the factory recovery back in place if I need to and away I go!
Besides this, if I use a cutom ROM and let's say then KitKat is available for my device, what if only one developer(s) has put out a custom ROM with KitKat for me and I do not like their ROM? With the Factory ROM, I can update and then I can teak this and that, to get the experience I want, without cutting off the factory update channel.
Anyway, that's my take and my experience. You may completely disagree with all of it. <lol>
So the bottom line is, I was hoping to get just a flashable Kernel to add to my Factory ROM (Rooted) and a way to install it and that's it.
To the next fellow that responded, to me, it does need overclocking. Mine runs very slow quite often. Slower than my old Galaxy Tab 10.1" a lot of the time. The TF700T I had a while back would blow this thing's doors off!
But I blame the Jelly Bean 4.3 version of Android, because I know what this thing should be able to do and I have read a lot of speed complaints across devices with JB 4.3.
And don't you dare disagree! I choose to believe this, because if you burst that bubble on me, I'll be running down the street screaming, while pulling my hair out! Hahaha!
Thanks to both of you for responding to my post and letting me know what the current situation is. I appreciate you taking the time to do that for me.

Zeuszoos said:
Okay, I don't know what a ".18 Bootloader" means, but like I said, I am not a programmer by any means. I can follow instructions, ya know?
Let me tell you my experience...
I have overclocked four devices in the past. In each instance, it was a very simple procedure, laid out step by step by whomever made it available. I had used both Pershoots Kernels and one called an "A1", for my old Glxy Tab 10.1".
It was only a few steps. And I didn't do it as part of a ROM or anything. In fact, in every case (except with my Note 2), I ran the Factory ROM on each device, Rooted.
Don't get me wrong, I'm not knocking anyones efforts in creating ROMs. Everyone likes what they like. For me, I like TouchWiz and I like the Asus unterface (whatever it's called) and I do not want to change them. Besides having to wipe my device every time I update a custom ROM, which I don't have to do with the Factory ROM, as it will always upgrade without wiping my data, it's a lot of work to to the next Android, without using another custom ROM. With the Factory ROM, I can unroot and even get the factory recovery back in place if I need to and away I go!
Besides this, if I use a cutom ROM and let's say then KitKat is available for my device, what if only one developer(s) has put out a custom ROM with KitKat for me and I do not like their ROM? With the Factory ROM, I can update and then I can teak this and that, to get the experience I want, without cutting off the factory update channel.
Anyway, that's my take and my experience. You may completely disagree with all of it. <lol>
So the bottom line is, I was hoping to get just a flashable Kernel to add to my Factory ROM (Rooted) and a way to install it and that's it.
To the next fellow that responded, to me, it does need overclocking. Mine runs very slow quite often. Slower than my old Galaxy Tab 10.1" a lot of the time. The TF700T I had a while back would blow this thing's doors off!
But I blame the Jelly Bean 4.3 version of Android, because I know what this thing should be able to do and I have read a lot of speed complaints across devices with JB 4.3.
And don't you dare disagree! I choose to believe this, because if you burst that bubble on me, I'll be running down the street screaming, while pulling my hair out! Hahaha!
Thanks to both of you for responding to my post and letting me know what the current situation is. I appreciate you taking the time to do that for me.
Click to expand...
Click to collapse
I am going to disagree and also say you have something wrong with your device. Out of the box the TF701 is one of the fastest android devices out there. Once you put a custom ROM on it it is even faster. And that is with out over clocking. Right now the CPU is not the bottle neck trust me.
The fact that you said your TF700 blows it out of the water indicates there is something seriously wrong. Go and run some benchmarks and give us some evidence where it is slow and maybe we can help you.
BTW I made a stock rooted ROM if you want to try messing.
Also are you using a microsd card. Maybe that is causing your issues. It's happened to a lot of others. Try removing it.

If I'm not mistaken, even if u unlock and install custom ROM, u can STILL return to stock and apply ota updates from Asus as they are released. So ur not cutting ur channel to getting latest stock updates. U just need to install stock firmware, and then place latest Asus firmware (ex: KitKat) in root of SD and reboot. U will update to the latest stock firmware. The only difference is that u won't receive the ota AUTOMATICALLY to us device rather u manually install it. Which is good as u won't have to WAIT for Asus to push the ota to ur device.
As for speeds, don't even compare the tf700 to tf701. If ur is running slow than ur tf700, then u SERIOUSLY have problems with ur device. Best way to find out is try running benchmarks and compare scores to tf700.
Sent from my K00C using Tapatalk

zabih107 said:
If I'm not mistaken, even if u unlock and install custom ROM, u can STILL return to stock and apply ota updates from Asus as they are released. So ur not cutting ur channel to getting latest stock updates. U just need to install stock firmware, and then place latest Asus firmware (ex: KitKat) in root of SD and reboot. U will update to the latest stock firmware. The only difference is that u won't receive the ota AUTOMATICALLY to us device rather u manually install it. Which is good as u won't have to WAIT for Asus to push the ota to ur device.
As for speeds, don't even compare the tf700 to tf701. If ur is running slow than ur tf700, then u SERIOUSLY have problems with ur device. Best way to find out is try running benchmarks and compare scores to tf700.
Sent from my K00C using Tapatalk
Click to expand...
Click to collapse
You can't do OTA but you can do full stock firmware installs.

sbdags said:
You can't do OTA but you can do full stock firmware installs.
Click to expand...
Click to collapse
Ota are firmwares that Asus pushes to our device "over the air"?
Sent from my K00C using Tapatalk

zabih107 said:
Ota are firmwares that Asus pushes to our device "over the air"?
Sent from my K00C using Tapatalk
Click to expand...
Click to collapse
Exactly.
Sent from my K00C using Tapatalk

So yes, ur not "cutting ur channel" to being on the latest stock Asus firmware Mr. Zeuszoos.
Sent from my K00C using Tapatalk

sbdags said:
I am going to disagree and also say you have something wrong with your device. Out of the box the TF701 is one of the fastest android devices out there. Once you put a custom ROM on it it is even faster. And that is with out over clocking. Right now the CPU is not the bottle neck trust me.
The fact that you said your TF700 blows it out of the water indicates there is something seriously wrong. Go and run some benchmarks and give us some evidence where it is slow and maybe we can help you.
BTW I made a stock rooted ROM if you want to try messing.
Also are you using a microsd card. Maybe that is causing your issues. It's happened to a lot of others. Try removing it.
Click to expand...
Click to collapse
What benchmark do you use? I have the Pay version of that one that starts with a "Q"? Quadrant, or something like that.
I do have an External SD Card installed, but I always do, so it's apples and apples, ya know?
I do have a very fast SD Card, one of those UHC-10's, or something to that effect. I think it's supposed to be the fastest one out there right now.
I've actually been pretty fortunate when it comes to SD Cards. My devices have always run exactly the same, with or without them installed.
As for this device, I was originally running it without one. Had to wait for them to arrive. But again, I noticed no difference in how it performs.
My biggest slowdowns are waiting for the screen to draw and for a file operation to start, etc., et al. And I have even installed an SD booster, which did smooth it out pretty well, compared to what it was, but it's still not so fast.
But I get what you're saying. I ran it ithout modifications at first and it had JB 4.1.2 at first (mine did not come with 4.3) and it ran great! But once I installed JB 4.3, well, that pretty much ended my daily cherring that I was doin in the direction of my Tablet.
As for speed, I know that you're right about custom ROMs, especially with the CM ROMs. I know they're wicked fast!
But remember my friend, I didn't mention speed when I discussed custom ROMs.
My choice to stay with the Factory ROM, has nothing to do with speed. I stay with it only for the reason that I mentioned.
I appreciate your offer of help. I really do! And I would have provided a benchmark, but I wasn't sure which one you'd find acceptable.
Oh, I remember the name now! Quadrant!
Will that one do? I personally do not think it will reflect what I'm seeing though. Plus, it's not just me. As I said, I read about this across devices and specifically regarding the TF701T, so I don't think I'm crazy.
Also, with no disrespect intended, if you're running a "really fast" custm ROM, then you can't really tell me how mine's doing, because it would be apples and oranges, ya know?
But I am certainly willing to try stuff with you, no problem! And thanks a bunch for wanting to do so!!!

Zeuszoos said:
Will that one do? I personally do not think it will reflect what I'm seeing though. Plus, it's not just me. As I said, I read about this across devices and specifically regarding the TF701T, so I don't think I'm crazy.
Also, with no disrespect intended, if you're running a "really fast" custm ROM, then you can't really tell me how mine's doing, because it would be apples and oranges, ya know?
But I am certainly willing to try stuff with you, no problem! And thanks a bunch for wanting to do so!!!
Click to expand...
Click to collapse
I would bet you are mixing up reports about the TF700 with the TF701. I am following quite a few forums and threads on both devices and nobody, ever complained about the 701 being slow - except you of course
I was running it on stock until about 2 months ago and even then it was blazingly fast in everything: Downloads, browsing, file transfers, switching between apps - no hesitations whatsoever.
Face it: It's something YOU did. [emoji12][emoji56][emoji33]
Flash sbadgs's rooted Asus stock rom. It's pure stock - just cleaned up with few optimazations. You won't even notice the difference to pure stock - except exceptionally better performance of course.
And if you don't, it's time to wipe your data partition, re-install your apps slowly and find what's causing this beautiful machine to bog down.

Zeuszoos said:
What benchmark do you use? I have the Pay version of that one that starts with a "Q"? Quadrant, or something like that.
I do have an External SD Card installed, but I always do, so it's apples and apples, ya know?
I do have a very fast SD Card, one of those UHC-10's, or something to that effect. I think it's supposed to be the fastest one out there right now.
I've actually been pretty fortunate when it comes to SD Cards. My devices have always run exactly the same, with or without them installed.
As for this device, I was originally running it without one. Had to wait for them to arrive. But again, I noticed no difference in how it performs.
My biggest slowdowns are waiting for the screen to draw and for a file operation to start, etc., et al. And I have even installed an SD booster, which did smooth it out pretty well, compared to what it was, but it's still not so fast.
But I get what you're saying. I ran it ithout modifications at first and it had JB 4.1.2 at first (mine did not come with 4.3) and it ran great! But once I installed JB 4.3, well, that pretty much ended my daily cherring that I was doin in the direction of my Tablet.
As for speed, I know that you're right about custom ROMs, especially with the CM ROMs. I know they're wicked fast!
But remember my friend, I didn't mention speed when I discussed custom ROMs.
My choice to stay with the Factory ROM, has nothing to do with speed. I stay with it only for the reason that I mentioned.
I appreciate your offer of help. I really do! And I would have provided a benchmark, but I wasn't sure which one you'd find acceptable.
Oh, I remember the name now! Quadrant!
Will that one do? I personally do not think it will reflect what I'm seeing though. Plus, it's not just me. As I said, I read about this across devices and specifically regarding the TF701T, so I don't think I'm crazy.
Also, with no disrespect intended, if you're running a "really fast" custm ROM, then you can't really tell me how mine's doing, because it would be apples and oranges, ya know?
But I am certainly willing to try stuff with you, no problem! And thanks a bunch for wanting to do so!!!
Click to expand...
Click to collapse
Trust me I know how the stock ROM runs. In quadrant you should get 15,000+ which isn't slow. You'll also see from the breakdown that the CPU is not the bottle neck. Tweaked and customised you'll see 18,000
Do me a favour get rid of that SD software and remove the sdcard, reboot. Run quadrant. What do you get....?
Time for a factory reset?

berndblb said:
I would bet you are mixing up reports about the TF700 with the TF701. I am following quite a few forums and threads on both devices and nobody, ever complained about the 701 being slow - except you of course
I was running it on stock until about 2 months ago and even then it was blazingly fast in everything: Downloads, browsing, file transfers, switching between apps - no hesitations whatsoever.
Face it: It's something YOU did. [emoji12][emoji56][emoji33]
Flash sbadgs's rooted Asus stock rom. It's pure stock - just cleaned up with few optimazations. You won't even notice the difference to pure stock - except exceptionally better performance of course.
And if you don't, it's time to wipe your data partition, re-install your apps slowly and find what's causing this beautiful machine to bog down.
Click to expand...
Click to collapse
Not confusing the two. I know what I'm typing on, my friend.
I personally do not even like custom ROMs based on the Factory ROM. You still have to wipe and install again when the new version comes out (if it does) and since that takes me 2-3 days of setup, I don't want to do that. And when, as I said, on my Note 2, I installed a custom ROM, it was also based on the Factory ROM and was v4.1.2, but when v4.3 came out, guess what? There would be no new ROM versions to replace the one I had, because the developer got rid of his Note 2, so that meant a wipe/reset and starting from scratch!
No with a straight Factory ROM, that would not be necessary when an update came out.
Again, I'm not knocking custom ROMs. In fact, the developer did one heck of a nice job with the one I installed on my Note 2! But I just do not wish to go through that and so, I left my Note 2 at v4.1.2 and even sold it with that custom ROM still installd on it (they knew everything, I didn't hide anything from the buyer and they liked it as it was).
You have to understand, that with settin up folders, installing my apps, which is about 375 of them and tweaking the settings in each and every one of them, as I'm going through them, Install/Tweak, Install/Tweak, etc., et al, it can easily take me 2-3 days of work to set up my device again, so Factory Resets do not get done to my devices! I fix problems, I don't erase them!
Anyway, I have been a "Computer/Electronics Tech" for 30 years and taught the stuff as well, so while I'm not a programmer and I'm not an Android "exoert", I do know what my eyes are looking at and I can follow instructions.
So I approached it logically, when it felt sluggish to me and before setting everything up on my Tablet, I did run benchmarks. And I did not have the SD Card installed in the slot yet, being well aware that they can cause performance issues.
And what I did to minimize any possible impact, was to buy the fastest performing Micro-SD Card out there and ran benchmarked both before and after it's installation and saw no impact from it, which surpised me a bit, but never-the-less, there was no impact on my device.
But here's teh thing that I must not have made clear; When I'm running a game or something, it runs great! It's the average little "always doing those things" sort of stuff that's sluggish. Like when you flip an app to the background and you're expecting the screen to redraw and show your icons/shortcuts/whatever you want to call them. Me? That's when I sit and wait. That's just one example.
As for custom ROMs, like I said, not knocking them at all. KJust not a fan of them, because putting the new one on (after OS update has come out) involves wiping and starting from scratch and when you have almost 400 apps installed, it's a 2-3 days job! And I simply do not believe people that claim that they do it a couple of hours and that's it. It takes a lot longer than that, just to !tap "Install" for each one and get the apps on your device
As I said, I had a custom ROM on my Note 2 and like the one you mentioned, it was based on the Factory ROM.
But guess wat happened? The developer got rid of his Note 2, which meant (as he said), no update and so anyone who wanted to go up in their OS version now had to wipe and start from scratch!
As a side note, personally, I do not like it when people are so quick to say; "Just perform a Factory Reset", because they do not know what's involved in that for a number o people. Plus, to me, no offense to anyone, it just seems to me like giving up. I'd much rather figure out how to make it work. But I find lots of people always saying "Factory Reset!", for every little problem and to me, that just doesn't make sense (I'm not saying that it wouldnt, or wouldn't in this case)! I'd much rather have the Factory ROM, Rooted, with an OC Kernel. Then get rid of all of those apps that they know we don't want, but wish to annoy us for a while with them.
So I'm looking to stay with the Factory ROM, without bloat and an OC Kernel. But I have to admit, the ROM that you mentioned does sound intriguing to me! Any links to it?
I guess I'm a bit worried that 4.4.3 will come out right after I install the ROM you mentioned, but I do want to check it out! Who knows? Maybe I'll stick with it and just never change out the ROM.
What ver of Android is it again and did you provide a link for it? I'm in "Reply" mode hereand cannot see your post. right now.
THANKS FOR YOUR TIME!!!
Btw, Quadrant ht 18 thousand. But like I said, it's not the running of apps/games once they've started up. It's the basic stuff and starting up of big apps (star apps, games, etc.) that's not fun!

berndblb said:
I would bet you are mixing up reports about the TF700 with the TF701. I am following quite a few forums and threads on both devices and nobody, ever complained about the 701 being slow - except you of course
I was running it on stock until about 2 months ago and even then it was blazingly fast in everything: Downloads, browsing, file transfers, switching between apps - no hesitations whatsoever.
Face it: It's something YOU did. [emoji12][emoji56][emoji33]
Flash sbadgs's rooted Asus stock rom. It's pure stock - just cleaned up with few optimazations. You won't even notice the difference to pure stock - except exceptionally better performance of course.
And if you don't, it's time to wipe your data partition, re-install your apps slowly and find what's causing this beautiful machine to bog down.
Click to expand...
Click to collapse
Read my other reply that I just finished, but go thru it carefully, please.
As for this ROM, I wish you had pasted in a link. I might have even tried it. But I just spent 3 days setting this thing up two weeks ago and that's a lot to go thru again! Especially so soon after doing it!
And no, I won't believe you if you claim I should be able to do it in a couple of hours. You do not know my setup.
As for it being something I did, that's quite rude and you do have an attitude. You do not even know me and I'm sorry, but you're not going to convince me that I am the only person in the world that waits for a screen to draw, just because it's a 701. That's a ridiculous claim! And you should ask yourself why your ego tells you that if YOU can't find it in the whole minutes that you spent looking for it, that means that it doesn't exist. Apparently you feel that it should all come to you. That's ego.
But hey, maybe I'm just deluded, or on drugs. Or maybe I hit my head falling out of a tree. Or maybe I just don't know anything about electronic devices. I mean after all, YOU could not find it, which MUST mean that it does NOT exist! But let me quote something to you regarding this Tab and 4.3, which is what I said slowed mine down;
"4.3 for the TF701T is on Asus's web site... The I/O has slowed it down to a crawl."
Since you don't like to paste in links and prefer to slam me instead, I won't paste the link in for you either.
I have openly stated that I am not a programmer. I am also not an Android "expert". I do know a lot about the subject, but I am by no means an expert.
What I do have for qualifications, is being a compluter/electronics technician (a real one,) for 30 years and an instructor of everything from sub-atomic teory (which is involved, believe it or not), all the way up to Global Wireless Networking, including satellite technology (and by that, I mean anything involved). And when I say all of this, I mean going anywhere from the overview, down to the board and chip level of every device involved.
I'm not saying any of this to brag. I'm simply showing you what an idiot you are for assuming that you know what I know and what I don't know. And for just assuming that I did something wrong, stating it as an incontrovertable fact!
The bottom line is, it ran nice and smooth in all operations, until I performed the system update to JB v4.3 and then, while games/large apps run beautifully, starting them up is very sluggish! And o is waiting for the screen to redraw after a simple operation like throwing an app to the background.
As for the ROM, like I said, I might have even tried it, even not being a fan of custom ROMs, because it's based on the Factory ROM and if it's a KitKat v4.4.2 for the TF701T, ten I would probably go for it and just leave it at that OS level for as long as I owned the Tablet.
But if it's a JB v4.3 ROM, whether based on the Factory ROM or not, then I'm simply not interested at all, no way, period. I see no point in redoing my entire setup, just so that I can go from v4.3, to v4.3.
I'm sorry to be so blunt in this reply, but you didn't exactly leave a lot of room for friendliness. Especially not with your "Face it! YOU did something wrong!". In truth, that was a comment that was just plain silly! And one that was not based on any facts that you gathered, but rather, just your assumptions about me. And that, my "friend", whether you want to hear it or not, is pure ego!
I'll take a look for that ROM. But as we both know, if I can't find it, that means that it was never written, right? And of course, as we all know, that would also mean that YOU did something WRONG when you mentioned it, right?
Update: I just searched XDA for "TF701T" "ROM" "sbadgs" and it responded with zero results. Guess that means that YOU did something WRONG! <lol!>

sbdags said:
Trust me I know how the stock ROM runs. In quadrant you should get 15,000+ which isn't slow. You'll also see from the breakdown that the CPU is not the bottle neck. Tweaked and customised you'll see 18,000
Do me a favour get rid of that SD software and remove the sdcard, reboot. Run quadrant. What do you get....?
Time for a factory reset?
Click to expand...
Click to collapse
I believe you do, my friend! I was not doubting you on that at all!
I did just notice that you are the guy making the custom ROM being discussed here. That's cool. To talk to the source, I mean.
I am not interested though. Not because of the quality of your work or anything. From the discussion here, it seems like a great product! I'm just not interested in spending days setting up again, just to go from v4.3, to JB v4.3, that's all.
But if I were to install a ROM, I'm quite sure that it would be yours, as I do very much appreciate retaining the factory experience and getting rid of as much bloatware as possible!
Just FYI, I did strip out at least 2/3 of the bloatware that comes with the ASUS Factory ROM.
Just as a note; If your ROM was KitKat v4.4.2 and you did what you did to this v4.3 ROM, then in all truth, I probably would install it and just leave it at that forever and enjoy your ROM!
Unless you can tell me that I could install your ROM over the Factory ROM and I won't lose my apps? I know that can be done in certain circumstances and of course, when the factory puts out a ROM update, it does do exactly that and you do not lose your apps, nor any of your own data.
If I cannot do that with your ROM, could you please tell me why I should change my mind and install yours anyway?
Please understand, I'm not asking that out of vanity, nor am I intending to be demanding.
Instead, I am genuinely asking a sincere question. I am actually going for humility, not vanity here, in that I recognize that no one is going to know your ROM better than you and I'm thinking that due to your superior knowledge (that's not meant to be patronizing), you would be able to tell me (if you feel so inclined) to tell me what important advantages I might gin from your custom ROM, that I do not currently possess,
As for where I am right now, of course I am on Jelly Bean v4.3.
I have also stripped out the majority of the bloatware that comes from the factory and so, it is not a case in which I just have a ton of stuff running wild on my tablet, eating up resources and thus, performance.
Again, just FYI, I am also running "Greenify", as well as "BootManager" (Defim Utils) and of course, "App Quarantine" for anything that might slip through my barricades <lol!>
So I leave it up to you, my friend. If you are so inclined (if not, then I appreciate the time you gave me already), what is it that should really draw me to your ROM, versus what I already have/have done?
Once again, THANK YOU for your time! I REALLY DO appreciate it!!!

Zeuszoos said:
I believe you do, my friend! I was not doubting you on that at all!
I did just notice that you are the guy making the custom ROM being discussed here. That's cool. To talk to the source, I mean.
I am not interested though. Not because of the quality of your work or anything. From the discussion here, it seems like a great product! I'm just not interested in spending days setting up again, just to go from v4.3, to JB v4.3, that's all.
But if I were to install a ROM, I'm quite sure that it would be yours, as I do very much appreciate retaining the factory experience and getting rid of as much bloatware as possible!
Just FYI, I did strip out at least 2/3 of the bloatware that comes with the ASUS Factory ROM.
Just as a note; If your ROM was KitKat v4.4.2 and you did what you did to this v4.3 ROM, then in all truth, I probably would install it and just leave it at that forever and enjoy your ROM!
Unless you can tell me that I could install your ROM over the Factory ROM and I won't lose my apps? I know that can be done in certain circumstances and of course, when the factory puts out a ROM update, it does do exactly that and you do not lose your apps, nor any of your own data.
If I cannot do that with your ROM, could you please tell me why I should change my mind and install yours anyway?
Please understand, I'm not asking that out of vanity, nor am I intending to be demanding.
Instead, I am genuinely asking a sincere question. I am actually going for humility, not vanity here, in that I recognize that no one is going to know your ROM better than you and I'm thinking that due to your superior knowledge (that's not meant to be patronizing), you would be able to tell me (if you feel so inclined) to tell me what important advantages I might gin from your custom ROM, that I do not currently possess,
As for where I am right now, of course I am on Jelly Bean v4.3.
I have also stripped out the majority of the bloatware that comes from the factory and so, it is not a case in which I just have a ton of stuff running wild on my tablet, eating up resources and thus, performance.
Again, just FYI, I am also running "Greenify", as well as "BootManager" (Defim Utils) and of course, "App Quarantine" for anything that might slip through my barricades <lol!>
So I leave it up to you, my friend. If you are so inclined (if not, then I appreciate the time you gave me already), what is it that should really draw me to your ROM, versus what I already have/have done?
Once again, THANK YOU for your time! I REALLY DO appreciate it!!!
Click to expand...
Click to collapse
Well you can install my ROM over the top and it would keep your apps and data. However the Asus unlock tool wipes the device But you can use the Asus backup tool to backup and then restore afterwards. You'll lose 15 minutes of your life doing it and you could do something more important during that time
Anyway you haven't run quadrant. I also don't like or recommend apps like greenify and bootmanager as they can and do introduce problems. You seem to be running a lot of background stuff. Why? Just unlock, flash my ROM, choose only the apps you want and be done with it
BTW I also created a 4.4.2 based ROM in original dev but it is still beta and doesn't support the Asus apps although it runs most other stuff fine.

sbdags said:
Well you can install my ROM over the top and it would keep your apps and data. However the Asus unlock tool wipes the device But you can use the Asus backup tool to backup and then restore afterwards. You'll lose 15 minutes of your life doing it and you could do something more important during that time
Anyway you haven't run quadrant. I also don't like or recommend apps like greenify and bootmanager as they can and do introduce problems. You seem to be running a lot of background stuff. Why? Just unlock, flash my ROM, choose only the apps you want and be done with it
BTW I also created a 4.4.2 based ROM in original dev but it is still beta and doesn't support the Asus apps although it runs most other stuff fine.
Click to expand...
Click to collapse
I do get what you're saying and thanks for the info. But to address a few points:
1) I did run Quadrant and stated that it hit 18k.
2) I also stated that I don't have a problem with how apps run. The problem I see with speed, as I've said a couple of times, is the basic stuff, like exiting an app and waiting for the screen to draw, shortcuts getting created, stuff like that. The basic stuff. But once an app does come up (which seems delayed to me), it runs smooth as glass!
3) As for what I'm choosing to run in the background, you don't usually choose to do that. Apps do that all by themselves when you install them. That's why I said that setting up for me is not a 2 hour affair, but a 2 day affair. Because I go into the settings for each and every app I install and disable that stuff whenever possible.
4) The reason I use a bootmanager and Greenify, is because Task Managers (an erroneous title for those apps) kill the apps, but not the problem. The apps just start right back up again. I prefer to change the settings in an app and for those that don't allow that, I keep them from running in the first place. Then they only run when I want to use them. For example, I do not have news apps updating in the background. I update them manually after I open them.
5) I do not care about running the Asus apps. I have removed all of those that I can, except a couple of necessary ones. If you have a 4.4.2 ROM that will run stable, I would be interested in testing it for you once you consider it to be "finished". I'm using that term loosely of course, meaning that there will always be some sort of bugs in any piece of software that's out there.
You've been very kind and very helpful. Thank you for your time!
Also, I am a tech and have been for 30 years. So if there's ever any hardware, or Windows (I know) questions you have, please feel free to PM me and I'll give you my personal email address there. I appreciate community and people like you help to make it one! I sincerely mean that!
As for your ROM, I'm going to wait for you to come out with a KitKat ROM and then install that. I assume it will be after ASUS releases the OS update???
It's fine, because I've got some othr priojects, like trying to convince my LG Optimus F6 that the 32GB External SD Card is actually its Internal Storage. There actually is a way to do it, but so far, I can't get it to do anything more than swap the two while it's running. Once I reboot it, it says; "Nuh, Uh!!!".
Do you have your own thread where you announce your stuff? I'd like to keep up to date with your new releases. I don't trust stuff from too many people, but as far as how a ROM should be done, you and I seem to be on the same page. Just what you need and then customize it with apps yourself.
P.S.: I'm still interested in OverClocking this thing. For me, the rule is as follows: "Does it run? Yes? Then it needs to be overclocked!".
I.e., Asking ME if it needs to be overclocked is kind of like taking my friend Jeff shopping for his next motorcycle. He was looking at two of them. He asked about the top speed. The sales guy told him one went up to 160MPH and the other to 170MPH. The salesman then said; "But at that speed, does the 10MPH really matter?".
My friend Jeff looked at him with a very serious face and eyes wide open and said; "Of course it does!!!".
My philosophy with Porsches and computing devices.
Thanks again!

Should i sign up for android n?

i want the new look. and enjoy new features. i have never seen a boot loop. so i cant take risk of that. though everyday bugs are okay. as i have other devices. id be okay? as in from boot loops or soft or hard bricks? Thanks.

No, definitely not. I don't know what your Android experience is, but from your comments and the "junior member" tag (not a reliable indicator, I know), plus the fact that you've never had a bootloop (lucky!) I'm guessing that it's not much.
I've had Nexus devices for several years and I'm sort of comfortable with upgrading and fixing, so I tried the Android N preview. I lasted about a week. Far too many things were broken - many apps have not been upgraded, and probably won't be until we're far closer to the final release.
So unless you want to ruin your day-to-day experience with one non-working app after another, have patience and wait at least until the second preview, and even then wait to read in these forums about how many problems still remain.
As to new features and new look - minimal, and not worth the aggravation, in my opinion.
But there you go - others may have a different opinion - you'll have to decide for yourself, of course.

akholicc said:
i want the new look. and enjoy new features. i have never seen a boot loop. so i cant take risk of that. though everyday bugs are okay. as i have other devices. id be okay? as in from boot loops or soft or hard bricks? Thanks.
Click to expand...
Click to collapse
I'd say a minimum for checking out the preview is:
-leave the bootloader unlocked
-Know how to flash a factory image on a per image basis (no flash-all.bat)
-Have 0 critical data on the thing, if you wipe it you lose nothing you care about. Keep in mind even camera photos, sms history, small things like that. (btw N preview is very very buggy trying to take pictures on any app I got force closes everytime I opened google camera, lcamera, or open camera)
When the marshmallow preview came out I put it on my N5, it was just a table weight at the point when the preview came out as I had my N6. Now with the N preview I went and charged ahead putting it on my daily use device, and it "worked" but a LOT of apps weren't working correctly, many games Bloons monkey city, hill climb racing, etc crashed randomly or didn't open at all, some other apps like Dish anywhere, yahoo messenger, google camera, UPS, etc didn't work either. MXplayer was running every video in super safe Software decoding mode.
The transitions and animations were pretty awful on stock kernel, only kernel I found to work well was 2.95GHz Elementalx (running on ondemand and yes I noticed slightly smoother performance because ondemand shoots to max frequency under any load) or Elite Kernel with Blu-active governor (highly recommend elite though smoothest kernel I've seen.) And under any kernel the device ran much hotter than Marshmallow, I could only get 2.5 hours of mid brightness SD youtube over wifi from 100 to 0 battery (I can easily exceed that with a stock N5...) and again device ran hot on stock kernel doing that.
SOoo if your N6 is your sideline phone go for it, it'll dirty flash over stock and I didn't see any improvement from clean flashing :/. But seriously this preview is more buggy than the first Lollipop preview was imo.
Long story short I'm back on Marshmallow PureNexus + Elite kernel. Much smoothness and back to my cool running 4 hour screen time every day phone that sleeps like a baby . (granted that could just be more of not running stock but I went from Marshmallow xposed gravitybox stock rom and N was buggier w/ more random reboots and freezups.

Make sure to read the sticky`s thread (in my signature) for usefull and lifesaving threads about flashing etc etc and getting some basic knowledge you will need before you tinker with your phone, after that unlock the bootloader and backup important files just to be sure and then enroll to the google beta thread.
-Edit- first backup off course and then unlock the bootloader. Btw for a first release its quite stable and fluent, the 2nd release should come within a week i guess.

dahawthorne said:
No, definitely not. I don't know what your Android experience is, but from your comments and the "junior member" tag (not a reliable indicator, I know), plus the fact that you've never had a bootloop (lucky!) I'm guessing that it's not much.
I've had Nexus devices for several years and I'm sort of comfortable with upgrading and fixing, so I tried the Android N preview. I lasted about a week. Far too many things were broken - many apps have not been upgraded, and probably won't be until we're far closer to the final release.
So unless you want to ruin your day-to-day experience with one non-working app after another, have patience and wait at least until the second preview, and even then wait to read in these forums about how many problems still remain.
As to new features and new look - minimal, and not worth the aggravation, in my opinion.
But there you go - others may have a different opinion - you'll have to decide for yourself, of course.
Click to expand...
Click to collapse
thanks man. so i guess i should wait for more stable build.

StykerB said:
I'd say a minimum for checking out the preview is:
-leave the bootloader unlocked
-Know how to flash a factory image on a per image basis (no flash-all.bat)
-Have 0 critical data on the thing, if you wipe it you lose nothing you care about. Keep in mind even camera photos, sms history, small things like that. (btw N preview is very very buggy trying to take pictures on any app I got force closes everytime I opened google camera, lcamera, or open camera)
When the marshmallow preview came out I put it on my N5, it was just a table weight at the point when the preview came out as I had my N6. Now with the N preview I went and charged ahead putting it on my daily use device, and it "worked" but a LOT of apps weren't working correctly, many games Bloons monkey city, hill climb racing, etc crashed randomly or didn't open at all, some other apps like Dish anywhere, yahoo messenger, google camera, UPS, etc didn't work either. MXplayer was running every video in super safe Software decoding mode.
The transitions and animations were pretty awful on stock kernel, only kernel I found to work well was 2.95GHz Elementalx (running on ondemand and yes I noticed slightly smoother performance because ondemand shoots to max frequency under any load) or Elite Kernel with Blu-active governor (highly recommend elite though smoothest kernel I've seen.) And under any kernel the device ran much hotter than Marshmallow, I could only get 2.5 hours of mid brightness SD youtube over wifi from 100 to 0 battery (I can easily exceed that with a stock N5...) and again device ran hot on stock kernel doing that.
SOoo if your N6 is your sideline phone go for it, it'll dirty flash over stock and I didn't see any improvement from clean flashing :/. But seriously this preview is more buggy than the first Lollipop preview was imo.
Long story short I'm back on Marshmallow PureNexus + Elite kernel. Much smoothness and back to my cool running 4 hour screen time every day phone that sleeps like a baby . (granted that could just be more of not running stock but I went from Marshmallow xposed gravitybox stock rom and N was buggier w/ more random reboots and freezups.
Click to expand...
Click to collapse
thanks for detailed reply sir. i decided to wait untill some stable build comes. as i dont know anything about flashing. im too afraid to even try. :crying: thanks though:good::good:

If you do decide to register for the N preview, you'll eventually get an OTA update which will apply the N over your existing M and you'll lose nothing.
BUT...
I think I've read a couple of threads where people have accepted the OTA and it hasn't worked, and they hadn't unlocked their bootloaders and therefore have no phone at all. As a bare minimum, if you're going to try the preview, you should unlock the bootloader so that you have at least a fighting chance of installing a new ROM if there's a problem.
Normally root prevents OTAs, but strangely it worked fine on my rooted N6. Maybe the systemless root fooled it...
BUT...
If you unlock the bootloader, you'll lose all your data - it wipes the phone, so back up photos, SMS, etc.
And if you're not confident about doing this, then I stick with my original answer - don't touch N at all until the final factory release around October.
(P.S. A plea to everyone in these forums. Don't reply to a simple 1-page thread post copying the entire post to which you're replying. I've already read the original - I don't need to read it again. Copy the original post only where necessary - e.g. if it's on a previous page. And even then copy only the point to which you're replying, not the entire post. The result will be clearer and shorter threads which will be more enjoyable to read.)

i'm going to wait for the factory release. Thanks again. and sure no problem ill keep that in mind.

These are horrible answers
These are horrible answers by people who themselves don't know enough about the subject to give any advice, for example, the first gentleman referred to your XDA member status to partially determine your knowledge on the subject. Consider mine, i have a senior member account, and i have now started this one which i use when i want to have some quiet time. It is annoying that there are some who think that after they have learned to flash a ROM on their Nexus device (the easiest device to flash) that they are part of some exclusive club in which their first duty is to deter any would be members from ever wanting to join. These people should be praising you for your interest, not deterring you from it.
That being said, here is my opinion on your question, you have a Nexus device so you probably have some sort of interest in Android or AOSP in general, so start learning all that you can about it. You're main focus should be in researching your bootloader unlock, fastboot, ADB, and your custom recovery of choice... (My preference is TWRP). Once you have your custom recovery in place and have made a full backup with it, there is little you can do to ruin your device, just make sure to never touch the recovery partition again until you are a little more knowledgeable. Once you feel like you have done the research you need, than take a crack at it. We all had to take the leap at one point or another. It isn't rocket science, these people are not smarter than you are, and its no big deal if you aren't happy with the new version, worst case scenario is you wipe and re flash. You said you have other devices in case yours has a hiccup and takes a day or so to come back, so just have fun with it. Good luck and feel free to pm me if you need any info or help.

S1CAR1US said:
These are horrible answers .
Click to expand...
Click to collapse
I agree.. I never signed up for the beta program(unless flashing N automatically enrolled me).. At the minimum unlock the bootloader.. Learn what you can and give it a shot. My experience with N has been almost perfect. All the apps I use work, I've installed my magpie transparent theme, camera opens normally, not one unintended reboot. I like N a lot. I came from pureNexus rom. Losing a device or two might come with the learning experience(I lost one Evo & Evo Lte) but I have more knowledge because I learned along the way. Go for it!!

its very easy..
if you want a N ota(all the N previews), then sign up. if you could care less about otas, then dont sign up. all signing up will do is let you get a N ota.

Uh oh..another 'horrible answer' coming up!
Depends. How badly do you NEED your phone? Do you use it for important business? Can you afford it to be 'down' for any length of time? What are your expectations..root?Adaway?TWRP? etc. Will your desired themes/layers/tweaks work on N? I cannot answer these questions for you, and no one else can. It's all a balancing act between risk and stability..some of us live on the edge, some should have no shame in waiting for stability.

And this may help people to decide:
http://forum.xda-developers.com/nexus-6/help/unlock-bootloader-t3356276
If you don't know what you're doing, just don't do it. Simple.

Slight deviation from the topic but can i accept the N ota if I am stock rooted? Will it work and will I lose root?

Depends on the root. I was rooted with (as I remember, may be wrong) SuperSU v2.67 and to my astonishment the OTA worked. You will lose root, but it's simple to restore.
But read the warnings above - unless you're really experienced and can fix your phone the risk outweighs the small benefits, in my opinion, especially if you do it now when the second preview will be available shortly.
And whether you do or not, unlock your bootloader so that if you have problems you have at least a fighting chance of recovering your phone.
And note - UNLOCKING YOUR BOOTLOADER WIPES YOUR PHONE.

Thanks for the detailed response. My bootloader is unlocked already so at least that bit us done. I rooted just before the April update came out. Happy to lose root and try to get it back once the ota has been installed as there isn't much I use it for anyways.
Sent from my Nexus 6 using XDA Free mobile app

Heck yes. That is the joy of having a Nexus

I'm still running preview 1 and it's cool and all but, the lag gets pretty frustrating. I would at least wait until preview 2 if you're really feeling it.

Database Develop

welcome