Database Users

I'm done with all Android phones and tablets not released from Google.

FYI: This is a venting post, written spur of the moment. Probably rambling from point to point without proofreading or organizing thoughts. Don't even know if it will make sense to anyone.
In my haste to, you know, have the newest version of Android running on my Transformer, I totally destroyed it and cannot get it to be recognized in any USB form on my computer. There are tons of great ROMs built by the awesome development community, but I'm just sick of having to try out multiple ROMs just to find one that works without issues. IMO, the fault is split between Google and the hardware manufacturers. Google should force manufacturers to ship phones and tablets with stock Android. It is Google's system and they should have the control to do that. The manufacturers should be ashamed of themselves for not being able to release an update to the latest OS within a few weeks of the release, jellybean, and on a tablet that was only launched in the US in April 2011. Google should be ashamed for letting these manufacturers get away with running an outdated version on a device that is completely cabable of running the newest iteration. Had an official means of updating to Jellybean been available I would not have spent so much of my time rooting and testing ROMs to make sure I have a consistent user experience.
I look at Apple; the structure and consistency they have in regards to software updates. The first gen iPad received updates until iOS 5 for two years. Then you devices that are put out by Android manufacturers, new models are frequent and in the furry to try and saturate the market with tablets, they forget about the one that came out the day before. Too many screen sizes, different processors, causes developers to shy away. For example, there has yet to be a legitimate Spotify (which I use daily), twitter, Facebook tablet app. Even the official apps they do have for "tablets" are weak in the user interface compared to iPad apps.
I know the general public will probably never care that their phone/tablet doesn't receive the newest Android update, they call their phones "droids". That's because they don't know what they are missing since the manufacturers do not care about updating the firmware and they are running terrible skinned versions of the OS. I enjoy using my Galaxy Nexus on Verizon, but even that does not get updated from Google. Google needs to reassess how they distribute the OS and to who. Maybe it needs to be a little closed and vertical. It could help.

You have a very good point on it, I couldn't agree more with it.
But regarding the distribution of Android, I think that if the OS had to be the same on every phone/tablet, there wouldn't have a reason to exist so many different devices, it would be like Apple's iOS and its devices.
What makes the platform interesting is the fact that anyone can use it and alter some elements of it, a thing that you don't have in the strict control that Apple has on iOS.
Sent from my MB525 using xda app-developers app

I agree with you in certain points - as for update procedures in general.
I am still very annoyed by the update politics of the Transformer, since the officially offered upgrades caused so
many troubles for me, as random reboots and freezing ,......
On top of it, skilled people in this forum then manage to get nice kernels and ROMs done which are just
much better in performance and stability compared to stock, that you really do wonder who the heck ASUS is hiring
I found finally a stable combo for me based on ICS but failed so far for JB.
I am at the moment testing different JB EOS and kernel combos but experience still issues.
This can become indeed kind of boring....
Your view comparing the great support of Apple on the other hand I don't share completely. It is basically the same as for their Desktop/Laptops.
It is really so much easier to only support a handfulll of devices than thousands of different combinations. Sure, you have a point that
you benefit when you choose one of their devices. But bluntly I become afraid of the growing power of Apple, since I really embrace choice.
Their are always people who prefer a certain different device because it helps their needs ( look at all the different screen sizes for Android and
then check Apple), me I prefer e.g. HW keyboard for a mobile phone.
But then I prefer as well Linux and the choice to put together your preferred OS over a non-customizable MacOSX ...
BTW: I own as well Apple devices and this is not supposed to become a flame thread, please

At the end of the day its down to us as individuals what we buy.
The reviews are not always impartial but certainly a good starting point, but i find researching any product i buy before hand a must now a days.
Great example was when i had bought my gtab - if i had read about it properly i would have know Samsung are one of the worst for updates.....but then again none of the manufacturers promise any future upgrades - maybe again we are just expecting something that we were never told we were going to get??
Never had an issue with my TF but i agree you should not have to rely on a developers site to get "improved" versions of the software - but if i had an Ipad i would have no doubt jailbroken it to improve my ipad experience aswel, just like ive done in the past with ipod touches etc. Would i get another TF - yes - im looking to get the Infinity as i still feel that the Asus TF fits my needs and is still one of the best supported tablets out there.
So the moral of the story is nothings perfect, the infos out there......we just need to be a little more astute as individuals and put the time into looking at the pros and cons before we buy. We spend the money and make the choice - not Google, Asus or Apple.:good:

ultmontra08 said:
I totally destroyed it and cannot get it to be recognized in any USB form on my computer.
Click to expand...
Click to collapse
That's more or less impossible unless you managed to corrupt the first few EMMC blocks that contain the apx mode code. Which you have to know what you're doing to wipe.
Boot into apx mode, install the naked apx driver, then use Easyflasher to flash back to stock

ultmontra08 said:
In my haste to, you know, have the newest version of Android running on my Transformer, I totally destroyed it and cannot get it to be recognized in any USB form on my computer. There are tons of great ROMs built by the awesome development community, but I'm just sick of having to try out multiple ROMs just to find one that works without issues
Click to expand...
Click to collapse
ultmontra08 said:
I would not have spent so much of my time rooting and testing ROMs to make sure I have a consistent user experience.
Click to expand...
Click to collapse
ultmontra08 said:
I know the general public will probably never care that their phone/tablet doesn't receive the newest Android update, they call their phones "droids". That's because they don't know what they are missing
Click to expand...
Click to collapse
You don't need to update Android unless it's a big jump like going from Honeycomb to Ice Cream Sandwich going to all that trouble to Root, Install a custom Recovery, Install a custom ROM for a minor update like Jelly Bean is silly what could you possibly need from Jelly Bean that Ice Cream Sandwich can't already do I bet the only reason is "It's the latest" and Asus are officially going to release Jelly Bean for the Transformer.
ultmontra08 said:
There are tons of great ROMs built by the awesome development community, but I'm just sick of having to try out multiple ROMs just to find one that works without issues.
Click to expand...
Click to collapse
Unfortunately if you want to use something other then the stock ROM it's a process of trial and error I tried Android Revolution HD ROM for example (popular ROM) and had problems with my Transformer not responding in sleep mode and random reboots I found that Cyanogenmod was stable for my device every device is different so the trial and error process is unavoidable.
ultmontra08 said:
IMO, the fault is split between Google and the hardware manufacturers. Google should force manufacturers to ship phones and tablets with stock Android. It is Google's system and they should have the control to do that.
Click to expand...
Click to collapse
ultmontra08 said:
I enjoy using my Galaxy Nexus on Verizon, but even that does not get updated from Google. Google needs to reassess how they distribute the OS and to who. Maybe it needs to be a little closed and vertical. It could help.
Click to expand...
Click to collapse
Google Android is licensed as an open source operating system so Google doesn't have any power to tell manufactures they can't make their own version of Android to sell with their hardware or when you receive updates that's all the manufacturer.
ultmontra08 said:
since the manufacturers do not care about updating the firmware.
Click to expand...
Click to collapse
Asus have actually been great with Android updates for the Transformer just a bit slow.
ultmontra08 said:
The manufacturers should be ashamed of themselves for not being able to release an update to the latest OS within a few weeks of the release, jellybean, and on a tablet that was only launched in the US in April 2011.
Click to expand...
Click to collapse
You don't understand that it takes time to develop and test a new operating system on a device the process isn't as simple as you think it is you wouldn't want to suddenly get an update from Asus and then be complaining that it's unstable would you?.
ultmontra08 said:
there has yet to be a legitimate twitter, Facebook tablet app
Click to expand...
Click to collapse
If you are using a Tablet the screen is wide enough to be able to acceptably use a web browser for these tasks so you don't really need a specific App developed, it's really only necessary for Mobile due to small screens.
ultmontra08 said:
I look at Apple; the structure and consistency they have in regards to software updates. The first gen iPad received updates until iOS 5 for two years. Then you devices that are put out by Android manufacturers, new models are frequent and in the furry to try and saturate the market with tablets, they forget about the one that came out the day before. Too many screen sizes, different processors, causes developers to shy away.
Click to expand...
Click to collapse
If you prefer Apple feel free to switch but while having a range of hardware options does have it's down falls it gives you and developers more freedom and choice where as Apple will always have a small limited choice range.

Just get a Windows Phone or Windows 8 tablet. I am too, one of those who are totally sick about Android.
You know, I bought Asus Transformer TF101 right on launch and YOU HAVE NO idea how excited I am. But things started to change after using it for a day, lags, crashes, limited apps.
I've been waiting and waiting for months before ICS came, but a lot of issues are still left unresolved. Asus firmware is very prone to crashes.
I've been flashing ROM after ROM and wasted so many days on this... No way I will ever get an Android again.

LastBattle said:
Just get a Windows Phone ....
Click to expand...
Click to collapse
Talk about limited apps...

Eh, the way I look at it, ill have this tablet forever and by the time its so scratched and old I can give it to my kids and I can get the latest and greatest NEXUS having learned my lesson buying non NEXUS.
Sent from my SCH-I510 using xda app-developers app

im on jb rom from team EOS, this is the only jb rom i use until now. using nova launcher makes it almost perfect buttery smooth (perfect without Widgets on the screen) .
it's easy to find good rom without having to try all of them. just read people's comment. go to last page and see how many complaints user's has.

Using the EOS build 74 with KAT 1.4 and nothing else yields a Transformer that works perfectly for me minus the GPS. I know that people with the dock have a different set of issues but honest, my TF with EOS and KAT runs better than any stock ROM. The difference is amazing. Web browsing is very very fast, I can play all my 720P videos via SMB streaming with BSplayer.
So after more than a year my TF works as I expected it to out of the box.

ultmontra08 said:
I totally destroyed it and cannot get it to be recognized in any USB form on my computer.
Click to expand...
Click to collapse
Have you tried Wheelie?
http://forum.xda-developers.com/showthread.php?t=1676845

Android Revolution HD and be done with it. Why the need for the latest and greatest when you can use what works? I used to be an HTC fanboy, until I got the mytouch 4g slide. I hated that phone so much. I love Sense, but just the phone was.... eh. I'm very happy with my Galaxy S3. I feel like I should have opted for the Nexus, but I'm happy with my purchase.
I still have a G1 sitting on my dresser with a charged battery just in case I feel like rockin it oldschool. I'm an OG Android user. Been using android ever since the release of the G1. I do love vanilla android, but what Samsung did with TouchWiz is just short of amazing. I used to run MIUI on my HTC Vision, I ran it for a few hours on my S3, and had to go back to TouchWiz!!
And what was posted earlier, why are you using apps on a tablet when the browser works perfectly for all those websites? Apps are more of a phone thing, screen sizes sub-5"

The update from Honeycomb to ICS was a huge one and we got it, it was not bug free but good enough to get developers working. JB is not that big update unless you need Google Now.

wow i dont know where to start. i really dont want to turn this into an ios vs android flame war. but youre completly out of your mind. first of all you have to look at it from the carriers, hardware manf, and googles point of veiw.
now hardware manuf. , and carriers have it in their best interest to not release updates for all the previous gen devices from a year or two ago, even if they are capable of running the new versions. this way the new devices look more attractive to current and potential customers.
another thing is that you cant really compare the updates from iphone-iphone3g-iphone3gs-iphone4-iphone4s-iphone5-and probably in a couple months the iphone5s that wont do anything more exciting than the last model did. same thing with the ipads. before you know it you have a drawer full of iphones that look the same and dont really do anything different.
then you have android. approx 800,000 new android devices are activated every day. EVERY EFFIN DAY. now thats insane.
how many devices that didnt originally come with ios can now run ios better than they ran their org stock os? for example there are tons of devices that came stock with windows mobile/symbian/webos etc etc and they can now run many different versions of android.
my htc HD, my htc HD2, my hp touchpad, and those are just the ones ive owned. theres tons of others that were given new life because of android and the dev community.
another thing that doesnt make sense is how you can blame google, and the hardware manufacturers and the carriers for 3rd party apps that they have no involvement in. there are millions of developers making millions of apps for millions of devices. its not googles job to make sure they run perfectly on every device. thats the deveolpers fault if facebook app works better on one device than it does on another.
you see iphone and ipad apps dont really have that problem because all the devices are exactly the same. screen size/resolution doesnt change very much at all, and new features are a bore. "oh yay the new iphone can make face time calls over a cell connection and isnt limited to wifi anymore" so what they should have been able to do that years ago.
its also not googles or the hardware manuf. fault if you knowingly go against their waranty terms and screw up your device. thats the risk you knew was there. and its part of the learning process. things like unlocking bootloaders, building custom roms, modifying hardware, cross compiling drivers and kernels, overclocking, and overall getting he most out of your device, is not for kids.
yes the typical ios fanboy just wants to get his facebook updates and be able to locate the nearest starbucks, or genius bar, just by asking siri.
but the android dev comunity and the devices they work on are doing it right. why should you be told what you can and cant do with your device? why should you pay more for a device that only does less. why should you sleep on the sidewalk for 7 days to be first in line to get the new lame updated iphone that costs double and doesnt do double.
the hp touchpad is a great example of an awesome device that was on sale for 99-150 dollars from hp. it currently runs ICS like a champ, and will be getting JB roms that rock. i also have a tf101 asus that runs JB eos like WHOA! overclocked on both cores, awesome tegra2 chip. expandable memory, AND A NORMAL HEADPHONE PORT AND USB PORT. even a nice little hdmi port. its an old device already and it still blows he doors off any current gen ipad.
then theres the newer mk802 devices and hackberry A10 boards that will do anything a high end smartphone will do for 50 bucks and hooks right up to your tv. LETS see apple tv or roku do that.
bottom line is that you dont understand how this really works, and youre getting frustrated and giving up instead of learning and becoming better and the tech.
YOU EITHER MASTER TECHNOLOGY OR TECHNOLOGY WILL MASTER YOU!! thats all for now.
---------- Post added at 10:38 PM ---------- Previous post was at 10:30 PM ----------
redrol said:
Using the EOS build 74 with KAT 1.4 and nothing else yields a Transformer that works perfectly for me minus the GPS. I know that people with the dock have a different set of issues but honest, my TF with EOS and KAT runs better than any stock ROM. The difference is amazing. Web browsing is very very fast, I can play all my 720P videos via SMB streaming with BSplayer.
So after more than a year my TF works as I expected it to out of the box.
Click to expand...
Click to collapse
yeah i just updated with eos jb rom today and its so much faster than the stock asus ics rom. i was really surprise, because its still got a ways to go.
---------- Post added at 11:08 PM ---------- Previous post was at 10:38 PM ----------
Then you devices that are put out by Android manufacturers, new models are frequent and in the furry to try and saturate the market with tablets, they forget about the one that came out the day before. Too many screen sizes, different processors, causes developers to shy away.
Click to expand...
Click to collapse
just to clarify a couple of things. There's no such thing as Android Manufacturers. well i guess with the exception of googles devices that they release is as close as you could come to calling them and android manufacturer, but the rest are not Android manufacturers. and when you think about it the screen sizes are usually pretty consistent even across different hardware manuf. you had 2.8"/3.5"/3.8"/ 4.2's were common for a while. now youre seeing mini tablet/phones in the 4.7-5+ range. but there arent that many sizes to worry about development wise. same with tablets. 7"-8"-9.7"-10.1" etc etc. same with the cpu and gpu arcitecture. you got your arms, your tegras, your mali 400's, etc etc theres an android device for everyone for anything.
i also love how my buddies iphone 5 wont display netflix properly or pandora correctly on the new screen size/dimension. maybe the iphone5s ver. 2.1 will have fixed that. in a couple years.
I know the general public will probably never care that their phone/tablet doesn't receive the newest Android update, they call their phones "droids". That's because they don't know what they are missing since the manufacturers do not care about updating the firmware and they are running terrible skinned versions of the OS. I enjoy using my Galaxy Nexus on Verizon, but even that does not get updated from Google. Google needs to reassess how they distribute the OS and to who. Maybe it needs to be a little closed and vertical. It could help.
Click to expand...
Click to collapse
the general public doesnt care that their phones arent getting the newest rom/kernel versions although alot of them do. android seems to realease new versions as the hardware advances. they grow with the advancing power and abilities of devices. you wouldnt really expect a first generation tmobile g1 to run the latest jellybean version would you? its almost as if the hardware cannot really come out faster than the os to support it. everytime you hear of a new android version theres a whole new generation of way better spec'd devices that shortly follow. sorta opposite of apple, they release devices that are barely on par with devices that were released over 6 months ago or longer. if carriers dont want o update devices in order to entice customers to upgrade then i understand that. theyre in business to make a profit. i really dont see how restricting and limiting android would help in any way at all. thats the great thing about android. its just linux with a few things on top. and that is the nail in the coffin right there. unlimited customization and hackability.

haxin said:
YOU EITHER MASTER TECHNOLOGY OR TECHNOLOGY WILL MASTER YOU!! thats all for now.
Click to expand...
Click to collapse
AMEN!

Heads up: Code Aurora Forum has released 64 bit marshmallow source tree for msm8916.

msm8916 a.k.a. snapdragon 410 which is there on the LTE versions of Moto E. I wonder if we can get this up and running on our phones.
Link - "www(.)codeaurora(.)org/xwiki/bin/QAEP/release"
Check the October 9 releases with tag 'LA.BR.1.2.6-00110-8x16.0' and chipset 'msm8916_64'

BUMP!

*If it could be ported to Moto-E so we can get Marshmallow then yeah cool.
I have no clue about that stuff but i will keep an eye out for this topic.

Since we have only 1 GB of RAM, 64-bit is pretty much useless to us. This is a popular SoC among low end to low mid range phones though, so I expect us to easily get 6.0 in some form if Motorola won't do it. It helps that we're on stock android with little modifications already.

64bits demands more RAM to run system, apps that are developed on 32bits don't get any performance gain running on a 64bits system.

i have ported a LOT of x86 'c' code to 64 bit since 2001 roughly and there is far more to it than that..
understanding data types is your first step.. the x86 memory size limit is only part of the equation.
i have hard that as an excuse for dev's to not update their programs for a decade or two though..
you here the same old myth's about the x64 architecture.
..from people who don't code.

One example of the contradiction..
Years ago i got the source code for Cudaminer (crypto currency miner program)
And i compiled it by making slight changes to make sure it compiled in Visual Studio / MingW
And when i launched the 64bit build it was way faster than the 32bit build.
The dev of the cudaminer program said he was never going to do 64bit
because it was not any faster.. i proved crystal clear that yes indeed it WAS much faster
and not long after that he started doing his own 64bit build LOL
I also have run that test on various other miners for crypto coins and every single time the 64 bit was faster.
then years before that i had done other conversions such as eMule
I was one of the very first guys to make and share a 64bit build of eMule on the web.
it used a LOT of 3rd party libs and it had a massive code base.. it was no easy task.
64bit gives no performance gains is a myth.
All i was trying to say is this myth should not be perpetuated but rather we should look
at each case independently and see if this allegation holds true.
Some may benefit and others will not.. best way to see is do it and benchmark etc.
The internet is full of people who spout off and don't know what their talking about and i have made a career out of proving them wrong.
For example i was the only guy to crack/unlock a series of LG cell phones.
I was told by everyone on the web it can't be done because of DRM.
They were wrong and.. it had nothing to do with DRM either.
I wrote a program with a GUI (available in both x86 and x64 windows formats)
posted them online at Howard forums (nobody else ever have)
I don't listen to people on the web ..i go check for myself.
Usually when people say can't they are wrong.
Such as cloning the MEID on 2 of my old phones.. every where i looked i was told no.. "can't"
Well.. LOL
When i finished cloning them i showed some people what i did and laughed..
I had (back in '08) one LG phone and one Samsung phone (running different systems)
and i had my friend call me and text me.. both phones started ringing at once
and both received the text msg at the same time.
You don't believe everything you hear on the web

so why there is no 64 bit roms for this device and why every other sd410 phone with 1gb of ram is 32bit too?

jeez you guys really want to start with me..
look i give up, you all know more than me about 64bit code.
i give up LOL
can we get back to the main topic (the porting of Marshmallow to the phone)
you guys can keep quoting me saying you don't understand what i said (but you know i am wrong) LOL
that make sense ?
64bit is a debate all over the web.. if you have enough experience you have seen the matter argued before.
it's a hot topic so if someone brings it up don't be surprised to see some conflict.
it's sort of like saying the new versions of windows are ugly or not.. it's going to start some arguing.
the difference is i can post proof backing up my mouth (if i had to)
showing how people were wrong about 64bit being slower.
but about Android ? i never claimed to know.. all i said is let's not assume and check.
does that warrant an avalanche of mouthy replies ?
I simply said let's not jump to conclusions.
blame the guy saying that who didn't prove claims.. not me.
edit:
by the way since you guys seem so interested in replying back to me ?
how about answering one of the many topics were i asked for help ?
seems you guys know sooooo much about this yet i am still waiting like a week later to flash my phone LOL

Yes 64bit or not.... i still think Marshmallow would be interesting for our phone.
I know almost nothing about that update though so i have no idea if it's going to work
very well for our low spec phone.
which is why i came to hear from you guys that DO know this stuff

Honestly I have it (Marshmallow) on my N5 and its pretty decent. Certainly not worth a bump to 6.0 IMHO maybe 5.3??? Its just a very polished version of lollipop as far as I can see...
Sent from my XT1526 using Tapatalk

Thread cleaned of the stupidity and childish bickering... Back on-topic now thanks guys.

so what MameTozhio said is fact then ?
oh ok then..
well i change my mind then i see no point in getting this update my phone only has one gig of ram
and 64bit is only for devices with lots of ram..
childish bickering ?
or some guy making bold claims that no on is allowed to refute ?
edit:
By the way i proved it (and mods deleted it)
but for giggles i google'd it and hit no. 1
http://www.osnews.com/story/5768/Are_64-bit_Binaries_Really_Slower_than_32-bit_Binaries_
seems i am not the only one who actually checked LOL
and i quote the guy..
I wondered if it would be best to compile my applications in 32-bit mode or 64-bit mode. The modern dogma is that 32-bit applications are faster, and that 64-bit imposes a performance penalty. Time and time again I found people making the assertion that 64-bit binaries were slower, but I found no benchmarks to back that up. It seemed it could be another case of rumor taken as fact.
Click to expand...
Click to collapse

xpmule said:
so what MameTozhio said is fact then ?
oh ok then..
well i change my mind then i see no point in getting this update my phone only has one gig of ram
and 64bit is only for devices with lots of ram..
childish bickering ?
or some guy making bold claims that no on is allowed to refute ?
edit:
By the way i proved it (and mods deleted it)
but for giggles i google'd it and hit no. 1
http://www.osnews.com/story/5768/Are_64-bit_Binaries_Really_Slower_than_32-bit_Binaries_
seems i am not the only one who actually checked LOL
and i quote the guy..
Click to expand...
Click to collapse
Perhaps you should read more carefully...
I said that I had cleaned the thread of the stupidity and childish bickering.
Do you see your posts removed or are they still visible?
Clearly then, I wasn't referring to you.

i support you @xpmule, too many people talking everywhere without a proper knowledge

well i was saying that guy posted it should be slower pretty much and i thought hey you know what ?
Let's not jump to conclusions and wait and see.. Let's actually check.
And i tried to post some example about how 64bit myths are spread.
It's really up to each program out there as to whether it will benefit or not.
And if you listened to that guy earlier many of you would probably just oh well i don't want that update then.
With out even checking.. to see if it was better etc.
64bit vs 32bit touches a nerve on the web and i didn't want to stir up some drama for you guys here.
If i did then you all have my apologies
i say let's check it out and maybe do some benchmarks etc and see how it goes.
PS:
I am trying to leave this topic alone i don't want to agitate the mods (more than i prob have already)

[IMPORTANT] We need to do something about our current situation with the 5.1 Update

hey everybody,
As mentioned in the title we need to do something about all the 5.1 lollipop issues we have right now with our beloved tegra note 7.
If we all stick together now and show nvidia that we need there help, that we might get enough attention to get most (if not all) of the problems solved we have right now.
My idea is basically nothing else than just contacting Nvidia together and state our issues. NOT just on their nvidia tegra facebook page or whatever.
we all should take a few minutes to contact them everywhere possible. ONLY on sites which are related to the Tegra Note 7 of course.
we don't want to create unnessecary spam threads on sites which aren't related to the TN7.
so, here are some links to some a few pages where you can leave a post stating some of your issues you have with the 5.1 update:
NO SPAMMING, NO SWEARING, just state your issues
- Tegra Note 7 Board (Geforce Forums) <--- This link will redirect you directly to a new opened thread that i made where you can post about your issues regarding the TN7
- Nvidia Tegra (Facebook Page)
if there are any more sites which are related or important for the TN7 Issue reporting, then pls, feel free to post the link

I get the impression that NV is done supporting their Tegra 4 hardware. Go look at the Shield Portable forum and see the same complaints. This hardware is getting pretty old now.
I do wish it had been more popular and attracted some custom ROM developers.

swaaye said:
I get the impression that NV is done supporting their Tegra 4 hardware. Go look at the Shield Portable forum and see the same complaints. This hardware is getting pretty old now.
I do wish it had been more popular and attracted some custom ROM developers.
Click to expand...
Click to collapse
But they can't just leave us with one of the worst updates ever. They really should take responsibility for what they have done to us (and to the shield portable users).
Sent from my TegraNote-P1640 using XDA Free mobile app

155 views on this thread but only 2 posts at the thread at the geforce forums?!
Come on guys, if you want to get your tegra note 7 (hopefully) fixed, then you need to show Nvidia that you care about your Tablet.
Account registration just takes a minute, so please, just take this minute to help us all together out on this.

@GodOfPsychos
There is one more community related to Tegra Note on google+
I am restricted from posting the link.
Just google it

Godlets start a campaign against Nvidia t
Lets show them we care

btw. i will also try to reach out to the live chat support from nvidia when i have time.
Sadly they don't have a real support page for tegra note 7 (at least i can't see any).
so in this case i will just "invade" (not literally ) their Shield Portable support via live chat and talk to them as long as it is needed until i get a satisfying answer.
i know this might be kind of a "strange" move to make. but i won't just sit here and let nvidia do that to us. so i will try any possibility that it takes to get noticed by nvidia.
AND it still would be pretty nice if all the ppl that viewed this thread without even replying to it, would at least help us reaching out to nvidia because right now there are only a few that try to help. AND we need more people for that.
Please everybody, we need your support on this one.

swaaye said:
I get the impression that NV is done supporting their Tegra 4 hardware. Go look at the Shield Portable forum and see the same complaints. This hardware is getting pretty old now.
I do wish it had been more popular and attracted some custom ROM developers.
Click to expand...
Click to collapse
The Shield Portable does have Cyanogenmod tho...while Tegra Note does not

proudtobepinoy said:
The Shield Portable does have Cyanogenmod tho...while Tegra Note does not
Click to expand...
Click to collapse
^ Thats true
Even Shield Tablet has a Cyanogen Mod
http://forum.xda-developers.com/shi...-cyanogenmod-12-shield-tablet-lte-na-t3055043

Guys any one know how to make new roms or we could ask the shield guys to make us one

Posted.
Sent from my HUAWEI NXT-AL10 using XDA Premium 4 mobile app

Really wish some dev would give us a custom rom with decent performance, as opposed to stock lollipop. or even better, marshmallow.
I mean if 6.0 on my old Moto G is any indication on how much better the performance coule be then... yeah

Attempt to get graphics drivers for latest android versions for TF300T

will put more info on this later today and i will also update this periodically with other info as well. but i am attempting to contact asus and show that we really desire their support and help with this issue as we need these drivers to fully utilize our devices!!! these devices function perfectly well and we just need drivers.
UPDATE (10/2/17): Asus doesn't care and neither does Nvidia, so we are basically on our own. Only hope would be if someone could reverse engineer the drivers so we could make our own, but that would take a tremendous amount of effort and really doesn't seem like it would be worth it.
Admins please close this thread.

Please delete

Please delete

Please delete

Sending what good karma I can your way. I really hope you are successful with this

I hate to be the one to burst your bubble but Asus abandoned these devices long ago. Latest Graphics blobs we have are for 4.2.1 and that's all we are going to get. The original Asus Nexus 7 tablet has slightly newer ones that could potentially be ported over but with the age of these tablets we were lucky to have someone as talented as timduru to be able to hack some of the blobs just to make the transformers work on newer versions of Android. Sadly you would be better off moving on to a device that's a little more current.

hardslog said:
I hate to be the one to burst your bubble but Asus abandoned these devices long ago. Latest Graphics blobs we have are for 4.2.1 and that's all we are going to get. The original Asus Nexus 7 tablet has slightly newer ones that could potentially be ported over but with the age of these tablets we were lucky to have someone as talented as timduru to be able to hack some of the blobs just to make the transformers work on newer versions of Android. Sadly you would be better off moving on to a device that's a little more current.
Click to expand...
Click to collapse
This Really Suck... :crying:

hardslog said:
I hate to be the one to burst your bubble but Asus abandoned these devices long ago. Latest Graphics blobs we have are for 4.2.1 and that's all we are going to get. The original Asus Nexus 7 tablet has slightly newer ones that could potentially be ported over but with the age of these tablets we were lucky to have someone as talented as timduru to be able to hack some of the blobs just to make the transformers work on newer versions of Android. Sadly you would be better off moving on to a device that's a little more current.
Click to expand...
Click to collapse
That isn't the point. Maybe we could go the route of porting the Nexus 7 drivers, but regardless, there is no reason whatsoever that Asus doesn't help us out as they claim to be "open source friendly" or what not.

rjmxtech said:
I am attempting to contact Asus and show that we really desire their support and help with this issue as we need these drivers to fully utilize our devices!!! These devices function perfectly well and we just need drivers.
Click to expand...
Click to collapse
Did you already receive any reply from Asus on your attempts. What do you think about to contact NVIDIA as well as the manufacturer of the processor and the graphic hardware? Please have a look at the NVIDIA site. Maybe you can find an access to trace the needed drivers there http://www.nvidia.com/page/home.html.

ebonit said:
Did you already receive any reply from Asus on your attempts. What do you think about to contact NVIDIA as well as the manufacturer of the processor and the graphic hardware? Please have a look at the NVIDIA site. Maybe you can find an access to trace the needed drivers there http://www.nvidia.com/page/home.html.
Click to expand...
Click to collapse
Asus ignored me. I could try Nvidia, but I do not think we are going to have much luck. I don't know what to do next.

@Diamondback even though you are a retired moderator, could you please get someone to close this thread?

N6F26R 7.1.1 February image posted

As title...
https://developers.google.com/android/ota#shamu - OTA full image
https://developers.google.com/android/images#shamu - full image

Is the microphone issue fixed?
Sent from my Nexus 6 using Tapatalk

Same bootloader, same radio. FYI

FLaMpeR said:
Is the microphone issue fixed?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I have the same question. This bug is annoying.

Demonoid_i_am said:
I have the same question. This bug is annoying.
Click to expand...
Click to collapse
Yes it's fixed for me.
Sent from my Nexus 6 using XDA-Developers Legacy app

buge boyo said:
Yes it's fixed for me.
Sent from my Nexus 6 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Glad we can fix it...is dirty flash from 7.1.1 alright?
Sent from my Nexus 6 using Tapatalk

Strange. Just swapped phones with my wife and the loudspeaker echoes horribly, so I guess it's not fixed for me, unless I'm misunderstanding the problem...
Edit: Half an hour later, after dinner and a flash of Yoinx's speaker fix, both my wife's Nexus 5 and my Nexus 6 are clear as a bell, both of them on loudspeaker. I therefore say that the Google image does not contain the loudspeaker fix - not from where I sit, anyway. Anyone else?
"is dirty flash from 7.1.1 alright?"
Yes. I flashed the OTA directly over the existing N6F26Q and it works fine.

Best way to tell is if someone could pull the mixer file and diff it to see any changes ... I would but I'm not in front of my setup right now.

Well, from where I sit the best way is to call someone, switch on your N6 loudspeaker, and see if they can hold a conversation with you... Which I did. And it didn't work until I flashed Yoinx's zip.

Google will most likely not fix it. Any new updates will most likely just be security patches. If you want the fix then I would flash the zip or grab a custom roms that has it fixed for ever. Never can say I ever had this issue as I don't use speaker phone ever. Unless completely alone it is considered rude.

The nerve. Why in the world would they leave such a feature broken. I know some people don't use it but the purpose of a phone is to freaking work. Doesn't matter if you use that feature or not. Others do. I use speaker all the time because I work from home. Stock software shouldn't have this problem. Period. It's been over a month and still no fix from Google. Meanwhile our guys fixed it almost immediately. This is just plain negligence and disrespectful at this point. I guess it's a sign they want us to get a new device so they completely fu**ed this phone by breaking what is a core and even basic feature of all phones. Ridiculous and ******y practices. At this point there literally is nothing that's making me more mad.

MysticKing32 said:
The nerve. Why in the world would they leave such a feature broken. I know some people don't use it but the purpose of a phone is to freaking work. Doesn't matter if you use that feature or not. Others do. I use speaker all the time because I work from home. Stock software shouldn't have this problem. Period. It's been over a month and still no fix from Google. Meanwhile our guys fixed it almost immediately. This is just plain negligence and disrespectful at this point. I guess it's a sign they want us to get a new device so they completely fu**ed this phone by breaking what is a core and even basic feature of all phones. Ridiculous and ******y practices. At this point there literally is nothing that's making me more mad.
Click to expand...
Click to collapse
What do you expect. The device is EOL which means anything broken will stay broken. Then add in that the OS was coded for 64 bit devices and had to be ported to our device to begin with. Also really if you are not willing to dig in and fix the issue then you miss the whole point of owning a nexus. It's a developer device.
And yes some people use it and some don't. That is the way it is with all features.
Getting upset about it is really pointless.

AOSP commits from 7.1.1_r13\N6F26Q to 7.1.1_r17\N6F26R
.
project bionic/
e046081 Check for bad packets in getaddrinfo.c's getanswer.
project build/
8a89878 N6F26R
e225344 Update Security String to 2017-02-05 on nyc-dev
8e84b75 Update Security String to 2017-02-01 on nyc-dev
project device/htc/flounder/
a37d1ee Fix security issue in Visualizer effect
project external/libavc/
cf606f3 Decoder: Fix in checking for valid profile flags
project external/libgdx/
c156e72 Fix security vulnerability
project external/libhevc/
3a64694 Fixed handling invalid chroma tu size for error clips
f22345d Fixed out of bound reads in stack variables
e20f6b8 Fix in Chroma SAO for non-multiple of 8 height
project frameworks/av/
048ba59 Fix security vulnerability: potential OOB write in audioserver
bab10e4 Effect: Use local cached data for Effect commit
project frameworks/base/
593144f [DO NOT MERGE] Fix vulnerability in MemoryIntArray - fix build file
de5747d Fix vulnerability in MemoryIntArray
a66099e DO NOT MERGE. Retain DownloadManager Uri grants when clearing.
4df434d DO NOT MERGE: Check provider access for content changes.
project frameworks/native/
541b1eb Correct overflow check in Parcel resize code
74dae33 Fix security vulneratibly 31960359
509fb5c Fix SF security vulnerability: 32706020
project hardware/libhardware/
9f0e940 Fix security vulnerability: potential OOB write in audioserver
project libcore/
c55ce33 Fix URL parser may return wrong host name
project packages/apps/Bluetooth/
379e7b6 Remove MANAGE_DOCUMENTS permission as it isn't needed
project packages/apps/Messaging/
1bb11f3 resolve merge conflicts of eafd58a to nyc-dev
13f739b 32807795 Security Vulnerability - AOSP Messaging App: thirdparty can attach private files from "/data/data/com.android.messaging/" directory to the messaging app.
86e5bf5 32322450 Security Vulnerability - heap buffer overflow in libgiftranscode.so
project packages/apps/UnifiedEmail/
1fc7b01 Don't allow file attachment from /data through GET_CONTENT.
project system/core/
7f94bb4 change /data/bugreports to /bugreports
project system/sepolicy/
54a3eec label /bugreports

dahawthorne said:
As title...
https://developers.google.com/android/ota#shamu - OTA full image
https://developers.google.com/android/images#shamu - full image
Click to expand...
Click to collapse
Is there a TWRP flashable version? Those of us with root ava TWRP need to extract the zip and flash system. IMG, boot.img etc. Using ADB?

zelendel said:
What do you expect. The device is EOL which means anything broken will stay broken. Then add in that the OS was coded for 64 bit devices and had to be ported to our device to begin with. Also really if you are not willing to dig in and fix the issue then you miss the whole point of owning a nexus. It's a developer device.
And yes some people use it and some don't. That is the way it is with all features.
Getting upset about it is really pointless.
Click to expand...
Click to collapse
Okay so you're telling me it's perfectly fine for a manufacturer to leave a device in a broken state because the device reached the end of its life? This is what's wrong with the world lol. And no I'm not missing the whole point of the nexus line. This is my first Nexus device however. But that's not the point. You don't leave major bugs like this unfixed. Not sure about you but if I pay for something EVERYTHING on the phone should work correctly. Of course there'll be a few minor hitches here and there. I expect that from betas and custom roms. But that's what BETAS and custom roms are for. The point of the nexus line is to play with custom software. Of course if some things from that doesn't work then of course you can't expect google support. You buy a nexus (or at least you used to) to get pure Android without skins like TouchWiz or HTC sense. And of course to experiment with custom software. Just because google allows custom software on the device does not give them the right to fu** us on an update then leave it to the community to fix it. Luckily we have a terrific community that fixed it in no time. But still I expect that google fixes the mistake they made. Because it was in fact their mistake. They released an official update. Not a beta. This is supposed to be stable!

sanumaj said:
Is there a TWRP flashable version? Those of us with root ava TWRP need to extract the zip and flash system. IMG, boot.img etc. Using ADB?
Click to expand...
Click to collapse
No, you don't need to do all that. You can if you want, but the OTA is a one-button solution - sideload via ADB, reboot, job done. You'll need to reroot.

zelendel said:
The device is EOL which means anything broken will stay broken.
Click to expand...
Click to collapse
I wouldn't argue with zelendel on technical matters, but I can on matters of policy and principle.
This is no different from taking your phone in for repair and finding that they've fixed what you asked them to fix but have broken another component. You could argue that the difference here is that the ROM upgrade is free; I refute that by saying that I paid a great deal of money (£549/$800) on the understanding that I would receive ongoing support. That support does continue to come, and I welcome it, but the bottom line here is that Google broke a function and are therefore morally obliged to repair it. And since this is the company whose motto at the beginning was (is it still...?) "Don't be evil" I think I'm entitled to get upset, no?

For me its simple. Google broke it so Google needs to fix it. EOL or not, they brought out an official security update that has a error in it. But to be honest, i don't believe that Google even cares about the N6, to them its an old phone not worth putting much time and energy in.

Well it's a punch in the face to all of us who purchased the Nexus 6. This year Nexus 6p and 5x will suffer the same fate and next the Pixel phones. Great way to keep trust. The speakerphone is really important while driving or when using in a conference call which the latter is in my case. They've spent way to long time without fixing it. I'm grateful for the custom ROM community but Google should have fixed it long time ago for those who depends on running stock. Because of issues like this and conducts like this, people will move on to a different OEMs. In a marketing side of view, Google will loose customers in the long run.

TMG1961 said:
For me its simple. Google broke it so Google needs to fix it. EOL or not, they brought out an official security update that has a error in it. But to be honest, i don't believe that Google even cares about the N6, to them its an old phone not worth putting much time and energy in.
Click to expand...
Click to collapse
EOL does matter though. Google broke a core function of our device on the last official Android update we will get. One could argue it was not intended to make us buy a newer device, but Google's behavior on it leaves much open to speculation.
And to the anyone defending Google, would it be OK if auto manufacturers updated your car's radio on the first service appointment after the warranty had expired, and said update disabled all but one of your speakers? That's essentially what Google has done to the N6. To top it off, seeing the defense of Google is like going back to work after your service appt, and when you complain about the broken speaker functionality at the water cooler, your co-workers tell you you should give Ford some slack, after all, you're outside the warranty period, and they didn't the have to update anything for you.