yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) General] Sib64:
For all of us who have the new Nexus 7 "Flo" or "2013", we wait the output of the Factory and Binaries Images for our device.

But after the latest news, we are not sure to have these images.

Look this news from Androidpolice:

Read more, click to =>Legal Issues With Qualcomm May Prevent Factory Images For New Nexus 7 ('Flo') From Ever Being Published, JBQ Strongly Implies

ROM developers and Android tinkering enthusiasts alike have probably noticed at this point that the new iteration of the Nexus 7, unveiled two weeks ago, does not yet have factory images or driver binaries posted on the appropriate Google Developers page. A similar issue plagued the Nexus 4 in its early days, though eventually images were posted. At the time, legal issues were speculated as a possible reason for the delay, and Android build maintainer JBQ - largely responsible for the images / binaries - said only this in response: "I can't comment."

With the new Nexus 7, JBQ has not outright said that legal problems with Qualcomm are preventing the factory images (and possibly the driver binaries) from being published, but a quick look at the relevant evidence makes it pretty duh-obvious that's what's going on. A week after the new Nexus 7's announcement, JBQ tweeted the following:

A few days later, on August 5th:

Those tweets alone aren't enough to be definitively linked to the Nexus 7's image situation, but JBQ's comments on the Android building group regarding the situation pretty much seal the deal. When asked why the new Nexus 7 images were not available, JBQ replied as follows (consolidated for simplicity):

It's that second-to-last comment which points the [middle] finger at Qualcomm. And it's pretty easy to figure out why, looking at the chipset supplier for each Nexus device.

Nexus One: Qualcomm

Nexus S: Samsung

Galaxy Nexus: TI

XOOM: Tegra

Nexus 7: Tegra

Nexus 4: Qualcomm

Nexus 10: Samsung

Nexus Q: TI

Nexus 7 (2013):Qualcomm

All three Qualcomm-powered Nexus devices have had issues related to publishing factory images and binaries.

(Note: HTC did publish factory images for the Nexus One, but Google did not.)

What's the legal issue?

Who knows. Qualcomm is notoriously protective of its technology, having gone so far as to form a separate company devoted to R&D and the guarding of its intellectual property. It really could be anything. Maybe, eventually, things will work out like they did on the Nexus 4 and the images / binaries will be published, but JBQ isn't exactly sounding optimistic. We'll update this piece as we learn more.
[Nexus 7 (2013) General] sfhub:
I don't really care if they give me all the factory images, but at least give me the initial factory image. I can always apply the OTAs to get the rest if I really want to.

It is annoying they are having trouble releasing anything.
[Nexus 7 (2013) General] immunityx:
samething happen with the nexus4 i think we will see the images pretty soon
[Nexus 7 (2013) General] someotherguy:
So without the images is it possible to brick the device or can you pull all of the items needed off of a working nexus?
[Nexus 7 (2013) General] sfhub:
You can pull the recovery, kernel, system for sure (and it has been done). I'm not sure about the bootloader and radio.

So most of the "semi-bricks" which aren't really bricks at all can be resolved.

It is just nice to have something you know for sure is bit for bit the factory image.
[Nexus 7 (2013) General] someotherguy:
I used the system.img on day one, wasn't sure about radio's and such.
[Nexus 7 (2013) General] CMNein:
And it appears JBQ is resigning.
[Nexus 7 (2013) General] andrewNY:
This is horrible news. Google screwed up if they didn't demand the rights to release binaries as part of the deal to use Qualcomm chips.
[Nexus 7 (2013) General] stanglifemike:
My ONLY complaint about the '13 N7 has been that I wish it had the Tegra 4 in it instead. Guess that has become an even bigger importance than I originally thought!!!

SwiftKey'ed from my White Sprint Note 2 using XDA Premium
[Nexus 7 (2013) General] HitBobLer:
Sad about JBQ, sad about flo

I don't have the nexus 7 2013 (damn you Google for not having a UK launch yet) but this is disgraceful. Qualcomm need s to clean up their act and stop being so protective. Its has caused problems and lost one of the android communities best know figures.
[Nexus 7 (2013) General] casonswag:
Delete
[Nexus 7 (2013) General] geckocavemen:
This sucks. In my opinion Google should have learned their lesson and never gone with Qualcomm in the first place.

I've seen at least one tool here on the forum which will return a Nexus 7 to stock, but I haven't seen any plain system images. Just out of curiosity, does a stock jss15j system image and recovery image exist anywhere on the forum?
[Nexus 7 (2013) General] bso44:
Feel free to bombard Qualcomm here:

https://plus.google.com/u/0/+QualcommDeveloper/posts
[Nexus 7 (2013) General] rootusr:
it's a deal breaker for me, until this is changed I'm not getting a Nexus 7 2013, it's just pointless for me.
[Nexus 7 (2013) General] I Am Marino:
This stopped me dead in my tracks as well.
[Nexus 7 (2013) General] Gytole:
Im not gonna lie... Its a really amazing tablet stock even... It doesnt surprise me one bit that the images arent/wont be released though. Probably verizons evildoers
[Nexus 7 (2013) General] IXChicharitoXI:
Just when I was planning on buying the nexus 7 tomorrow...
[Nexus 7 (2013) General] sfhub:
There are pulled images contained in those restore tools. I don't know if they are JWR66N or JSS15J. At least one of the pulled images is pre-rooted so it isn't pure stock.
[Nexus 7 (2013) General] lyall29:
SON OF A ****, GOD ****, *** HOLES. This is disappointing news. Having the factory images was a big reason I like the Nexus so much in the first place
[Nexus 7 (2013) General] sfhub:
I've always had factory images from Samsung and HTC, just not stock android images (until recent pure android models)

Without factory images, Google is actually providing less than other manufacturers.

I guess the reason HTC was able to get out images on earlier Nexus models where it was also troublesome to release was they were probably willing to agree to some term with Qualcomm that the lawyers at Google are having issue with.
[Nexus 7 (2013) General] zaclimon:
My guess here would be like with the nexus 4. Actually they're having problems but i'm pretty sure there will be an aggrement so qualcomm decides to release their binaries.
[Nexus 7 (2013) General] Sib64:
A pure Google factory image, you can not find one on the forum.

Because if you go to Google dev you don't have JSS15J factory image and you don't have factory image for Nexus 7 (2013) "FLO"

I'm afraid that with the news that Google had a drop in sales of its Nexus 7 (2013)... not really important for Google
[Nexus 7 (2013) General] Sensamic:
I think...

I think...

Enough with I think. What matters here is proof, evidence, not personal opinions...

You won't get the factory images.
[Nexus 7 (2013) General] immunityx:
:rolleyes::rolleyes::rolleyes::laugh:
[Nexus 7 (2013) General] Johmama:
Well that's lame. I was going to buy this tablet later this month, but now I might just wait. I won't buy a different tablet, but I just don't think I'll buy the Nexus 7 before they release factory images. It's a big reason to buy and love the Nexus line. It's one of the biggest reasons why I bought my Nexus 4 and have been waiting on this second release of the Nexus 7 to buy it also :(
[Nexus 7 (2013) General] RusherDude:
This sucks hard.

By JBQ's words and resigning, I don't think this is the same story than the nexus 4. I bet that we will NEVER see N7(2013) factory images, and that means that I AM NOT BUYING THIS.

For now, complete stop until I see how this evolves.

In fact, I'm not buying another android device until I see how the AOSP stuff evolves.
[Nexus 7 (2013) General] DsturbD:
nvidia did the same thing with their tegra chips, we never saw an official release on the tmobile g2x nor an official update to ICS because their drivers are proprietary, probably the same issue here with qualcomm

yes i'm glad i had the official firmware for my S3 cause i needed it, but this didnt stop me from getting an N7, if you know what your doing and are careful....IF
[Nexus 7 (2013) General] gksmithlcw:
The difference is that the g2x wasn't a Nexus device meant to be an AOSP flagship.
[Nexus 7 (2013) General] HarmonyFlame:
This deeply saddens me. I think what people don't realize is how much this impacts the platform. This honestly might be the most devastating news to come out in a long time for android. It could honestly be the end of AOSP. Without AOSP android is no more. For me that means a lot. I can seriously say at my core I am absolutely an Android fanboy. No question about it. I love this platform, what it stands for, the community, the software, and it's services and functions. Most importantly I love what Google does and the nexus program. I do not want to see any of that go away and would be crushed if that happened. JBQ leaving may definitely be a huge blow and a sign of what's to come; I hope im wrong.

As a longtime android user/abuser and recent nexus devotee, I could not see myself using anything else besides an AOSP based nexus device. Leaving would be a nightmare and I hope I never have to someday walk away from this great platform.
[Nexus 7 (2013) General] sfhub:
That's being a little overly dramatic.
[Nexus 7 (2013) General] CMNein:
Bombshell day, smoke not yet cleared, but chances are the sky isn't falling.
[Nexus 7 (2013) General] wilsonlam97:
Damn. I've always taken these images for granted and to see them not being made available saddens me.
[Nexus 7 (2013) General] cyberprodigy:
Perfect poetically-based representation of the situation. People are overreacting.
[Nexus 7 (2013) General] CMNein:
I should have gone for the haiku. Worst day EVER.
[Nexus 7 (2013) General] HarmonyFlame:
Possibly. Completely far-fetched though? I'm not so sure. It's all just very disheartening is all. I'm sure we all agree.
[Nexus 7 (2013) General] jack.achbird:
thanks ;)
[Nexus 7 (2013) General] DsturbD:
true, but the g2x was a pure android device with no carrier or manufacturer overlays, like the moto xoom, and besides even though it wasnt a nexus device, still a case in point that hardware makers still use proprietary bits for their devices/chips and can license then as the see fit

its just one device, and has happened to other nexus devices in the past, its not the end of the world :eek:
[Nexus 7 (2013) General] paranoid android85:
I'm sure some sort of agreement will happen. As far as jbq, much respect, but im sure someone with as much knowledge will take his place. I seriously doubt this is the end.
[Nexus 7 (2013) General] -viperboy-:
I didn't mean to thank your post, hit the wrong button. Don't know if the Verizon joke was your attempt at humor or not, but they have nothing to do with it.

While I never figured this would happen for the new N7 (I was unaware of the N4 issue) it's not the end of the world. It's just annoying to not have factory images. We have this issue with HTC devices sometimes when we don't get RUUs right away or sometimes not at all.

We can get by without them, it would just be nice to have them like all the other Nexus devices. We'll just have to make sure to dump the tablet after all updates.
[Nexus 7 (2013) General] browngeek:
Without factory images, etc, does it mean we may not see custom Rome like Cyanogenmod fr the N7 2013?
[Nexus 7 (2013) General] viralbug:
This is seriously very sad news.

What some of us aren't understanding is that though we can get by without an official Google firmware, it's just not the same. The whole point of having a Nexus device is lost. This is against what AOSP stands for.

Honestly speaking after the issues during Nexus 4, I thought Qualcomm was ready to work things out. However, this news comes as a huge disappointment. I hope Nvidia, Samsung, Mediatek, Intel and all others step up with their SoCs so we don't see this happening again.
[Nexus 7 (2013) General] paranoid android85:
We'll still have custom roms. Aosp will still be there. We just won't have a stock img atm.
[Nexus 7 (2013) General] Hnk1:
I do not think the Qualcomm would be in much of advantage if they decide not to make factory images official.

Suppose, they do not let new nexus 7 carry on with distributing factory images. This will result in Google look for a new chip in all future models rather than Qualcomm as Google is known to have complete freedom and ASOP. The Qualcomm wouldnot let 10 millions or maybe more of chips never being used for New Nexus devices like Nexus 5 etc. However, Qualcomm thinks that it is best out there in the field and thus it doesnot want its technology to be open source. I guess Mediatek is catching up with Exynos and Tegra 4 a little behind at the moment.

But suppose, Google can not carry on with distribution Asus can surely do something as HTC did with HTC Nexus One.

Qualcomm if you release the factory images or not, you are going down !
[Nexus 7 (2013) General] Sib64:
Sign the petition

Petition to Qualcomm to allow Google to release factory images hits Change.org => Go ahead and

find the petition at Change.org.

If you want to read more go here => news from Phandroid

and this news from AndroidPolice about =>

Jean-Baptiste Quéru, Post-Nexus 7 Factory Image Debacle: "I'm Quitting AOSP"
[Nexus 7 (2013) General] diestarbucks:
He also said this:

Petition?

Petition for Qualcomm? Haha. LOL. No, seriously.

Such a petition is a waste of everyone's time.

It's a waste of time for people signing it (kitten videos are a much more efficient way to feel better).

The bigger issue is that such a petition actually makes things worse, because the people who could actually work toward a solution will now need to spend their time and energy dealing with the petition itself instead of dealing with the real problem.

Doh.

;p
[Nexus 7 (2013) General] Sib64:
Ok I understand what he want to say, so I'll delete the link for.

Thanks for your post ;)

If you want to know more about JBQ comments go here =>

Jean-Baptiste QUERU G+
[Nexus 7 (2013) General] diestarbucks:
Lol, no, I wasn't saying you needed to do that. Just showing his response to it. You may link whatever you like (within XDA rules of course :P)
[Nexus 7 (2013) General] CMNein:
At the end of the day it is not a big deal for ANY party involved; XDA and the Android tinkering microcosm are like echo chambers. This isn't the first Nexus that wouldn't have factory images.
[Nexus 7 (2013) General] mssam:
Well, I just signed the petition and there were only 583 other people who signed it. 24,416 are still NEEDED...
[Nexus 7 (2013) General] Sib64:
I've understood that you did not said that, but the comments from JBQ are clear and explicit for all.
[Nexus 7 (2013) General] Zurginator:
Maybe I should ask some of my Qualcomm buddies to let something slip. <_<
[Nexus 7 (2013) General] paranoid android85:
Factory images officially posted!
[Nexus 7 (2013) General] immunityx:
what was that? :rolleyes:

https://developers.google.com/android/nexus/images
[Nexus 7 (2013) General] rxnelson:
I'm probably in over my head here but the binaries are out too? Isn't this what all the stink was about?

https://developers.google.com/android/nexus/drivers

Maybe something is missing?
[Nexus 7 (2013) General] chiikko561:
Sent 4rm my Nexus 7 FLO... Only thing missing is O.G. N7's development...
[Nexus 7 (2013) General] DsturbD:
oh yeah!!! game on
[Nexus 7 (2013) General] RusherDude:
Then JQB failed?
[Nexus 7 (2013) General] jakdillard:
no not at all
[Nexus 7 (2013) General] chiikko561:
The complete opposite... Success!!!

Sent 4rm my Paranoid Nexus 4.3 LTE...
[Nexus 7 (2013) General] RusherDude:
I highly doubt that it was his resign what made the images to be published, there was no resign on the Nexus 4 case and they also took like 1-2 weeks to appear.
[Nexus 7 (2013) General] CMNein:
His post clearly states that qcom wasn't the ultimate reason regardless.....
[Nexus 7 (2013) General] Cuzz1369:
I thought this was "flo" what's "razor"
[Nexus 7 (2013) General] sfhub:
nsa codename.
[Nexus 7 (2013) General] zaclimon:
Flo = board name razor = device name, nuff said.

Envoyé depuis mon Nexus 7 en utilisant Tapatalk 4
[Nexus 7 (2013) General] wilsonlam97:
Fastboot says it's flow but Google gives it the codename razor. It's really confusing :crying:

Razor = Flo = Nexus 7 2nd Gen = Nexus 7 FHD = Nexus 7 2013
[Nexus 7 (2013) General] NYCHitman1:
Lol, not really all that confusing at all.
[Nexus 7 (2013) General] wilsonlam97:
One device needs only one name. Even two is kinda stretching it.
[Nexus 7 (2013) General] Sib64:
If you need more info read this post from [MENTION=3289998]TheManii[/MENTION] (Wiki Admin / Recognized Contributor)

I think that is clearly explicit ;)
[Nexus 7 (2013) General] matafact:
Google Image are out, just saw it...

The Stock Img's are now out....

<https://developers.google.com/android/nexus/images>

Finally, bout time!!!

New user so had to post that way...
[Nexus 7 (2013) General] Sib64:
the factory images and binaries for the new Nexus 7 Flo JSS15J

Finally, the factory images and binaries for the new Nexus 7 Flo JSS15J are released and if you want to download, go to => [Index] REPO for all you need for your nexus 7 FLO (2013) - Update 10 August 2013 ;)
[Nexus 7 (2013) General] dkb218:
Factory image released. I just all the hullabaloo was for naught.

https://developers.google.com/android/nexus/images#razor
[Nexus 7 (2013) General] Moscow Desire:
Thread Closed

As now factory images have been released, Philos64 has asked this thread to be closed.

Sooooooo.......

Cheers!
[Verizon Samsung Galaxy S 4] coltonwood:
http://xdaforums.com/showthread.php?t=2395549

everyone should go check this guy's app out. its the active display lock screen, but us currently only available for 4.3 unless people show interest.

point is, SHOW INTEREST :) so we can get it.
[Verizon Samsung Galaxy S 4] lolerpro8:
If I have time, i will try to compile AOSP 4.3 for our hd2. That is just a MAYBE, since i DON'T really have much of free time.
[Verizon Samsung Galaxy S 4] coltonwood:
hey if you DO start working on it, awesome! would be excited to check out your work sometime in the future!
[Verizon Samsung Galaxy S 4] lolerpro8:
Yup

I have been developing on a less known manufacturer based phones, but i didn't get much attention, so i have quited. Then i was searching for another device, and got hd2 from someone(for free :D ). Currently im using this rom http://xdaforums.com/showthread.php?t=2126053 .

Most stable i could find :p . Maybe (if i DO have some time) It won't be the best jelly bean rom out there xD
[Verizon Samsung Galaxy S 4] coltonwood:
in my op they have a working version for us (alpha version). just a heads up to those interested
[Verizon Samsung Galaxy S 4] JoeFCaputo113:
So which one do we download (if we're on a stock 4.2.2 ROM).... v1.4 or v1.5alpha2 ?
[Verizon Samsung Galaxy S 4] coltonwood:
I'm on the 1.5 and its working. but SMS does not work if you are using the stock touchwiz sms. this is because it wakes the screen when you get a message so that ruins it. but hangouts, emails, instagram, etc work fine for me
[Verizon Samsung Galaxy S 4] HwaA18:
I disabled Stock SMS notifications and I'm using 88SMS for stock 4.2 look
[Verizon Samsung Galaxy S 4] coltonwood:
I would think that should work fine then. I tested it with Sliding SMS and it worked perfectly!
[Verizon Samsung Galaxy S 4] HwaA18:
For the TTS problem, did you uninstall Samsung TTS and Talk back? The voice-over is really annoying
[Verizon Samsung Galaxy S 4] coltonwood:
mine never had the problem but I'm not sure why yours did though. the Dev may respond on the thread from my op. he seems pretty set on keeping it updated and fixing bugs.
[Verizon Samsung Galaxy S 4] jfu:
I think the talkback is just an accessibility bug for samsung devices. Only happens when an app is using accessibility.
[Verizon Samsung Galaxy S 4] coltonwood:
dev claims to have fixed the Samsung SMS bug. haven't tried it yet.
[Verizon Samsung Galaxy S 4] coltonwood:
added several new options. most notably (for me) was the option to use this as the lock screen. went ahead and went premium!
[Other Tools & General Discussion] ilie321:
Hello to all,

What I'm asking you guys is if you consider good to have a smali to java converter.

I am working at one and i want to know if to continue or not; if is good to something etc.

Please post your opinion here

Thanks

To moderators: please put this thread in the good section if is not (thanks)
[Other Tools & General Discussion] ilie321:
Hmm no opinion. Am I in the wrong section?
[Other Tools & General Discussion] ilie321:
im working when i have time at it but i have problems with "if " at this moment

continued here http://xdaforums.com/showthread.php?p=53819600
[Eee Pad Transformer Q&A, Help & Troubleshooting] Rabid Ewok:
Please forgive but i'm a total moron:

I screwed up my tablet, I screwed it I installed a jelly bean from paranoid android 368 and it ill not gp past the fish logo ....and I need help... it does not see the internal or external sd...... HELP!!!!!!!!!!!!!!!!!!!!!!
[Eee Pad Transformer Q&A, Help & Troubleshooting] *Detection*:
Use Easyflasher to unbrick and flash TWRP

http://xdaforums.com/showthread.php?t=1688012

Boot into TWRP Recovery, Wipe SYSTEM, CACHE, DALVIK CACHE

Then flash KatKiss ROM

http://downloads.timduru.org/android/tf101/K.A.T/KatKiss/stable/KatKiss-4.2.2_224.zip

And Gapps

http://goo.im/devs/teameos/roms/eos4/gapps/gapps_4.2.2_TF101_20130323b.zip

Remember to wipe Cache and Dalvik Cache only, AFTER flashing everything else

Then reboot
[Eee Pad Transformer Q&A, Help & Troubleshooting] Rabid Ewok:
Wow... tried :( .... the tablet does'nt show up..... no APX no MTP all fail to install drivers.......
[Eee Pad Transformer Q&A, Help & Troubleshooting] *Detection*:
Try a different PC / USB port

Once you get APX working Easyflasher should be able to do it's job

Nothing shows up on the TF screen when it's in APX mode

--

Plug TF into PC USB

Power off the TF101

Hold Volume Up & Power until you hear the USB connect sound

Install the Universal Naked Drivers

http://xdaforums.com/showthread.php?t=1514942
[Eee Pad Transformer Q&A, Help & Troubleshooting] Rabid Ewok:
I did the easyloader.... used TWRP but it goes into CWM 5.8.1.8....... nothing... no TWRP ,please forgive may ignorance
[Eee Pad Transformer Q&A, Help & Troubleshooting] *Detection*:
If you had the tablet in APX mode and had the correct drivers installed, and you chose TWRP in Easyflasher, it should have flashed TWRP for you

Do you have another machine you can try it with ?

Did Easyflasher say success or any message ?
[Eee Pad Transformer Q&A, Help & Troubleshooting] Rabid Ewok:
..... no success message... i'll try again.... ok got this.

Running Wheelie..

>Tablet is now ready for Nvflash

Flashing twrp.SOS

>Finished, now reboot into recovery! :)

power/vol down then vol up........ CWM Recovery 5818
[Eee Pad Transformer Q&A, Help & Troubleshooting] frederuco:
Did any text appear on the tablet when in APX mode? It should show something when it is flashing.
[Eee Pad Transformer Q&A, Help & Troubleshooting] Rabid Ewok:
Thanks guys!.... it's alive!:D
[Eee Pad Transformer Q&A, Help & Troubleshooting] frederuco:
Sweet! The good thing - with the TF101 (non 3G version) the only way to really brick it is to throw a brick at it, or drop it like a brick.