yashsingh1/xdaforums huggingface dataset:
[T-Mobile, Samsung Galaxy SIII] Perseus:
Please try another Rom. Some of the Custom Roms may not be uptodate with CM Checkins. This issue was reported a bit back. There were CM Code Fixes that may not have been incorporated in that rom.

I am using Slimbean 2.0 (Android 4.3.1) and have seriously tested its bluetooth capabilities.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
its also been reported thst msny car manufacturers did not bother to put any time or money into their BT capable systems. they just threw it together so they could add to feature lists.

Lots of peopke have problems with BT in the car, especially on cm roms. but those are notorious for BT issues to begin with.
[T-Mobile, Samsung Galaxy SIII] yardsale:
Thanks for the replies. I flashed to Paranoid Android 3.99.1 RC1 but the problem still exists. I never had this issue with any of our vehicles, until switching to PA from stock ROM. If problem becomes unbearable, may go back to stock. Thanks again.
[T-Mobile, Samsung Galaxy SIII] Perseus:
[MENTION=5547996]yardsale[/MENTION]

I should have mentioned in the previously. Please read this post of mine. Yes its a different Rom. However, here primarily the issue is that of hardware antenna of the T999 talking to the Car's antenna. Doc is 100 % correct, the manufacturers do use substandard Antenna. On that thread, someone else reported issues with two '13 VW for themselves and their brother's.
[Nexus 7 Q&A, Help & Troubleshooting] thedjinni:
The official download link for the KitKat 4.4 update on the Nexus 7 (wifi) is returning a 404:

https://dl.google.com/dl/android/aosp/nakasi-krt16o-factory-db4a1a8a.tgz

Has anyone been able to successfully download this?

Are there any google/android folks out there who can fix this link so I can join the KitKat club?

UPDATE: Nov 21, 2013

A new KitKat update has been released (build krt16s) which fixes the bad link and missing bootloader issues that were discussed in this thread. Here is the link to the Nexus 7 (WiFi) factory image:

https://dl.google.com/dl/android/aosp/nakasi-krt16s-factory-da7dee49.tgz

Thanks to all for posting helpful comments and suggestions.
[Nexus 7 Q&A, Help & Troubleshooting] ivn888:
I receive this message:

404. That’s an error.

That’s all we know.

View attachment 2392319
[Nexus 7 Q&A, Help & Troubleshooting] Cwoomer:
I too would like to know this valuable information. I just saw on twitter that the links were up to dload the factory image and low and behold 404!!!!

All other links appear to be working fine!
[Nexus 7 Q&A, Help & Troubleshooting] issak42:
If you're in a hurry, grab a 4.3 image and update it with kitkat update.zip.

Otherwise I suggest waiting until tomorrow and trying again.
[Nexus 7 Q&A, Help & Troubleshooting] khaytsus:
I downloaded it about an hour ago, no problem...

Um, okay, no I didn't. I wound up with the Mobile. Damn.
[Nexus 7 Q&A, Help & Troubleshooting] phonic:
The Razor image is downloadable, but only 835 bytes. It's missing all the binaries.
[Nexus 7 Q&A, Help & Troubleshooting] khaytsus:
NOW the images are up, heh!
[Nexus 7 Q&A, Help & Troubleshooting] Hanger84:
The link works now. If anyone has trouble downloading it, let me know and I'll make a mirror.
[Nexus 7 Q&A, Help & Troubleshooting] thedjinni:
Fixed!

The link is working now.
[Nexus 7 Q&A, Help & Troubleshooting] gc84245:
Here's another link to the factory images:

http://www.mediafire.com/download/5hf2507c66cly45/nakasig-krt16o-factory-9c987833.tar
[Nexus 7 Q&A, Help & Troubleshooting] Hanger84:
lol looks like Google goofed yet agaij, the 4.23 bootloader is missing from the file still
[Nexus 7 Q&A, Help & Troubleshooting] PackMan55:
Dead Link

. . . Link is still the 835 byte file for me :crying:
[Nexus 7 Q&A, Help & Troubleshooting] gc84245:
Try the link I posted
[Nexus 7 Q&A, Help & Troubleshooting] zamuz27:
Coming from CM10.2, I went back to 4.3 and then flashed the 4.4 OTA. Is there any difference between that and flashing the factory image? I have a feeling that using the factory image is "cleaner" somehow, although I have no real reason for that.
[Nexus 7 Q&A, Help & Troubleshooting] Pont91:
I can confirm, the link is working now!

The file is 345 MB for me! :)
[Nexus 7 Q&A, Help & Troubleshooting] Hanger84:
From what I can tell, there's nothing different.

Personally, I prefer to do a completely clean flash of a rom instead of updating. I know it's not as much of an issue these days as it used to be, but I remember having tons of issues back when Froyo and Gingerbread was still new.....that, and HTC just generally sucked at OTA updates at times.

I'm making a deodexed and rooted flashable right now, and I'm adding in the new launcher and updated Google Now. I'll upload and share here is there's a demand for it, or if no one else does it. The updated Google Now and GEL run like the should now with no issues...including working auto rotate.
[Nexus 7 Q&A, Help & Troubleshooting] apecx92:
has google fix the missing bootloader?
[Nexus 7 Q&A, Help & Troubleshooting] Hanger84:
Nope, but you can pull it from the 4.3 stock image zip though. no change in bootloader version.
[Nexus 7 Q&A, Help & Troubleshooting] thedjinni:
FIXED - Update Nexus 7 to 4.4 KitKat

The link is now working, but the tarball is missing the required bootloader image. I tried using the 4.23 image from the previous release (jwr66y) but it appears to be corrupt. To fix the problem, I dug up an older jwr66v release (link below) and copied the bootloader-grouper-4.23.img file into the newest release folder, then ran the flash-all script. Seems to be working now.

Here is a link to the OLD release containing the GOOD bootloader:

https://dl.google.com/dl/android/aosp/nakasi-jwr66v-factory-d341d356.tgz

Here is a link to the NEW release with the MISSING bootloader:

https://dl.google.com/dl/android/aosp/nakasi-krt16o-factory-db4a1a8a.tgz

MD5SUM for the GOOD (jwr66v) bootloader-grouper-4.23.img: df53028033c9eccf4fe5ba7bc198ce24

MD5SUM for the BAD (jwr66y) bootloader-grouper-4.23.img: 5bdb2e87370cdb1a7ea14bb0c3e21390

TLDR:

Copy the bootloader-grouper-4.23.img file from the old (jwr66v) release into the new (krt16o) release folder then run flash-all.
[Nexus 7 Q&A, Help & Troubleshooting] thedjinni:
The version number didn't change, but the bootloader from the 4.3 stock image is corrupt.

Here is a link to a version containing a good 4.23 bootloader:

https://dl.google.com/dl/android/aosp/nakasi-jwr66v-factory-d341d356.tgz

See my other post for MD5SUMs on both the good and bad bootloader image files.
[Nexus 7 Q&A, Help & Troubleshooting] Hanger84:
The easiest thing to though, is to just remove the bootloader flash lines from the install script. Since the bootloader is the same, it won't be necessary to flash it.

On another note, while tinkering around, it looks like almost everything essential to the set up and running of the rom was moved from the /app folder in /system to /priv-app. Oddly enough though, Wallet was moved there as well. Considering that all the market downloadable apks were left in /app, it's slightly odd that Wallet is the exception.
[Nexus 7 Q&A, Help & Troubleshooting] thedjinni:
Flashing the factory image using the included flash-all script will wipe your device before applying the update. An OTA update usualy keeps your data intact.
[Nexus 7 Q&A, Help & Troubleshooting] rapunzel11:
Looking out for a Flashable-ZIP
[Nexus 7 Q&A, Help & Troubleshooting] Hanger84:
I got one made, about to test and make sure it's all good, then I'll post it.
[Nexus 7 Q&A, Help & Troubleshooting] gottria:
Is it a rooted stock flash? That is what I have been waiting for, just flash it and go.
[Nexus 7 Q&A, Help & Troubleshooting] zamuz27:
Oh yeah, that's a given. I didn't mind wiping my device, I was just wondering whether installing the factory image would lead to a cleaner flash than using the OTA update, like it usually does on desktop computers - it always seems like a better idea to install an OS from scratch than to update, although I'm not sure there's any basis for that reasoning on a mobile device.
[Nexus 7 Q&A, Help & Troubleshooting] MorRoquen:
The links are working perfectly now. I just used this guide ( http://xdaforums.com/showthread.php?t=1907796 ) to go to Stock 4.4 on my Nexus 7. No issues, all works fine so far.
[Nexus 7 Q&A, Help & Troubleshooting] zamuz27:
Well I had no idea about this. I was on CM10.2, and what I did was run the JWR66Y flash-all.bat (there could have been an error message about the bootloader but I wasn't really paying attention) and then sideload the 4.4 OTA. I have no problems so far, but I'm worried I might. Should I flash the JWR66V bootloader? And also, can I fastboot flash the bootloader only and nothing else, without wiping? Is that a good idea at all?
[Nexus 7 Q&A, Help & Troubleshooting] amrs:
Link's alive, checksums don't match

I just tried pulling https://dl.google.com/dl/android/aosp/nakasi-krt16o-factory-db4a1a8a.tgz. Went fine but checksum doesn't match what Google posted. I get b27054b89ccbf0a268c7bfb9cfd7cc4570f1d0a8 for sha1 instead of db4a1a8a1b288995703c05ba1f9a92e102da2766... So did they just forget to update those or what?
[Nexus 7 Q&A, Help & Troubleshooting] khaytsus:
Download it again.

4.4 (KRT16O)	Link	2d657e7c6e3bf690ef9aee07111d19dd	db4a1a8a1b288995703c05ba1f9a92e102da2766

md5sum nakasi-krt16o-factory-db4a1a8a.tgz

2d657e7c6e3bf690ef9aee07111d19dd nakasi-krt16o-factory-db4a1a8a.tgz

sha1sum nakasi-krt16o-factory-db4a1a8a.tgz

db4a1a8a1b288995703c05ba1f9a92e102da2766 nakasi-krt16o-factory-db4a1a8a.tgz
[Nexus 7 Q&A, Help & Troubleshooting] fushla:
Uhm.. So is the New factory image also infected with a faulty bootloader or did i get something wrong??
[Nexus 7 Q&A, Help & Troubleshooting] cammel:
Apparently the new kitkat full factory image doesn't contain a bootloader file at all, but someone please correct me if I'm wrong...

Enviado desde mi Nexus 4 mediante Tapatalk
[Nexus 7 Q&A, Help & Troubleshooting] thedjinni:
You may run into problems when trying to update the system in the future (that is the problem I was having with an old bootloader) but it seems like you've found a way around to get the new update so you're probably good for now. You can update just the bootloader using the fastboot utility, which you can get from the android SDK.

From the bootloader (power + volume down) run the following command:

fastboot flash bootloader bootloader-grouper-4.23.img
[Nexus 7 Q&A, Help & Troubleshooting] iamelton:
i got exactly the same SHA-1 checksum like u (which disagrees with whats written in the google factory image page)..

i even downloaded the tgz file twice to make sure its not a corrupt download file..

---------- Post added at 01:13 AM ---------- Previous post was at 01:11 AM ----------

there is a bootloader file (ver 4.23) included in the tgz file..

maybe some google guy updated the tgz file with the missing bootloader but forgot to update the checksums?

(see my previous post..)
[Nexus 7 Q&A, Help & Troubleshooting] muamers:
Okay guys, we are good to go...

I downloaded the Factory Image 3 times and had always the same result: the checksumms didn't mach at all with those on the google page...so i just flashed and EVERYTHING went great.

This are the original checksumms (that are forgotten to be updated on the original page):

MD5:

SHA1:
[Nexus 7 Q&A, Help & Troubleshooting] zamuz27:
Thanks! I might flash the JWR66V bootloader just to be sure, although I think that's the one I've been using all this time (since I used the OTA zip to go from JWR66V to JWR66Y, and then jumped to CM10.2 which I assume doesn't mess with the bootloader).

Sounds good! Just to be sure, can you confirm that the bootloader on the latest image flashes correctly?
[Nexus 7 Q&A, Help & Troubleshooting] muamers:
Bootloader version: 4.23 ;)

Edit: I used the Wug's Nexus Root Toolkit v1.7.5 if someone wants to know ...
[Nexus 7 Q&A, Help & Troubleshooting] joedoe:
Deleted.
[Nexus 7 Q&A, Help & Troubleshooting] zamuz27:
Alright, I just fastboot flashed the KRT16O bootloader and it worked perfectly, so I guess Google finally included a proper bootloader this time around. Thanks!
[Nexus 7 Q&A, Help & Troubleshooting] khaytsus:
I'm not sure how people are getting different checksums, my duelist matched the website and contained the bootloader. Perhaps they updated the download but the checksum is correct.
[Nexus 7 Q&A, Help & Troubleshooting] cammel:
They just updated the files on their server, this is weird... Even the n4 images has changed

Enviado desde mi Nexus 4 mediante Tapatalk
[Nexus 7 Q&A, Help & Troubleshooting] GedBlake:
Hi, cammel...

Yes. Indeed they have. Just re-downloaded the 'nakasi/grouper' image for Nexus 7... and it now contains the v4.23 bootloader. Google probably realised that shipping full factory images with important bits missing isn't a good idea:).

And even better news... it's the v4.23 bootloader from Jellybean 4.3 build JWR66V, not the corrupt one from build JWR66Y.

I've just ran an MD5/SHA-1 checksum analysis on it... and comparing the results to a

similar analysis

I ran back in August, it's definitely the v4.23 bootloader from build JWR66V... so people shouldn't have any problems fastboot flashing it.

Rgrds,

Ged.
[Nexus 7 Q&A, Help & Troubleshooting] slimno19:
System.img issue

For some reason Im still having issues sending/writing the system partition. Im using 4.23 Bootloader from the new 4.4 Factory Image. I tried the Bootloader from JWR66V but it still didn't work. Now I cant even use fastboot to get back to JWR66Y. I have no idea what I did wrong. I was able to flash CWM then sideload 4.2.2. Any idea how to get to 4.4 would be appreciated.
[General Questions and Answers] tokenpoke:
I need help modding an app on my phone, where would I request such services?
[LG Optimus L9 P760, P765, P768, P769] mikekoke:
Hello everyone, I'm here to ask you a little curiosity.

Just today I received the iBeats, I already knew that the controls (pause, forward and back for songs) would not work.

So I am here to ask you some trick or app to be able to recognize those commands to my phone.

I hope to be in the right section, otherwise move as well.

Thank you.
[LG Optimus L9 P760, P765, P768, P769] will0899:
I have the same ones and I believe it's only the pause button that works. Anyways I don't think there is a trick for the beats but you can always use xposed module to enable your volume key on phone to skip track. Give it a try it might work on you headphones.
[LG Optimus L9 P760, P765, P768, P769] kuma82:
Do you have a link for that module?

Never mind I found XBlast module :thumbup:
[Eee Pad Transformer Q&A, Help & Troubleshooting] mikeo23:
Hi,

When I am playing games (namely Clash of Clans), sometimes in the middle of the game, half my screen would go black. The game still functions but I am unable to see anything. I am currently rooted on KatKiss 4.3.1 #27 with TWRP 2.3.2.3. This doesn't happen any other time other than when I am playing games.

Thanks,

Mike
[Eee Pad Transformer Q&A, Help & Troubleshooting] frederuco:
Is it corner to corner half, or is it left half vs right half?

The Tegra 2 has some issues with screen tearing during some graphically intensive tasks. It will cause black or white on half of the screen. I am not sure there is a good fix for it at this time.
[Eee Pad Transformer Q&A, Help & Troubleshooting] shredbeta:
Possibly could be the game too. Clash of Clans won't even load on mine and I'm running the same version of Katkiss.

Update: Finally got the game working (turned out to be a firewall issue). I think I got the same problem with the black screen. This doesn't appear to be a tearing problem as it seems the actual game world went partially black (I could actually move the black section while scrolling around). I would say it's a game bug.
[Eee Pad Transformer Q&A, Help & Troubleshooting] frenzy0412:
any updates or workarounds?
[Eee Pad Transformer Q&A, Help & Troubleshooting] shredbeta:
Haven't come across a fix yet but interestingly PvZ2 now goes black straight after the splash screen. This was right after a recent update. Trying to find a way to report it popcap. Not sure if this is related.

I'm on KatKiss 4.4 (23) now.

Update - Confirmed version 1.9.271092 of PvZ2 works fine for me. Updating to version 2.2.1 causes the black screen issue.
[Eee Pad Transformer Q&A, Help & Troubleshooting] edd080:
Yes iam also on katkiss as in my sig, latest update of pvz2 (Ver. 2.2.2) is causing the black screen for me aswell.

Update: sent a message to popcap they should be releasing a fix that addresses a resolution issue;they are aware about it.
[Eee Pad Transformer Q&A, Help & Troubleshooting] shredbeta:
Cool. Hopefully they will mention it in the 'What's New' section so I know when it's safe to try updating.
[Eee Pad Transformer Q&A, Help & Troubleshooting] edd080:
Yep I am assuming the next update will address our issue.
[Eee Pad Transformer Q&A, Help & Troubleshooting] carlosalvatore:
Hi!

Sorry for bumping this post, but I am experiencing this issue too and it is very annoying, specially considering that tablet is used only for playing.

- About tablet
Model: Transformer TF101
Android: 4.4.4 (KatKiss)
Kernel: 2.6.39.4-kat118-g6618e86
Build: KTU84Q KatKiss-4.4.4_036
SELinux status: Disabled

- Hardware accelerated rendering
Force GPU Rendering: Enabled (Problem also happens with this option disabled)

- Performance
Minimum frequency: 1000 MHz
Maximum frequency: 1000 MHz
Governor: interactive

Images of Black half screen in Clash of Clans TF101 KatKiss:

[IMG="Master builder village"]https://s20.postimg.org/wh0uno4gt/IMG_20170802_020747.jpg[/IMG]

[IMG="Home village"]https://s20.postimg.org/g7aokrtst/IMG_20170802_040110.jpg[/IMG]
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] CesarRaimon:
So i just bought a new battery with NFC chip on it, its a 3500 mAh battery with the same size of the original one, anyways when I booted the phone up, I don't see any nfc toggle, so is there like a certain zip file or tweak or maybe an app I should do to get the toggle?
[Android Q&A, Help & Troubleshooting] alecz24:
Hi,

I just managed to birck my phone, an Allview P5 Alldro.I had previously rooted it and installed a custom Android 4.2.2 ROM.I wasn't happy with it's battery efficiency so i decided to go back to the official 4.0.4.All went good with a flashing tool but after the flash tool had the green circle that it was all done, the phone was dead.

Nothing works, cant make it normal start (power button), nor does recovery work (volume - and power).

Even tried plugging it in the PC and it won't get recognised, as in new hardware, in both Windows 7 x64 nor Ubuntu 13.10.Tried some Ubuntu tools that even checked the USB voltages and power that was sent through them and it didn't detect it.Nor does it do anything when plugged in the electric socket.

Just, a brick...

I read about a JIG tool used on Samsung smartphones, might it work on mine too?

The phone is just 3 months old.
[Verizon Samsung Galaxy Note II] morbidrealities:
So here's the deal ladies and gentlemen. Isis wallet is out and I'd like to give it a try. Lucky us V sucks and won't let us use it while rooted. YAY..:good: . So is there anyway to install an unrooted ROM without using Odin to return back to stock. I'd like to keep my recovery that way when I want to switch back to rooted it should be pretty easy without...you know...rooting through Odin again. Thanks in advance!
[Verizon Galaxy Note 3 Themes and Apps] yakitori2:
Taken Down. No longer modding apps and sharing. Sorry for inconvenience.
[Verizon Galaxy Note 3 Themes and Apps] Adrozz07:
Are the quick controls functional? I ask only because those were wonky on the note 2 with the hacked aosp browser.
[Verizon Galaxy Note 3 Themes and Apps] yakitori2:
Yes they are functional
[Verizon Galaxy Note 3 Themes and Apps] krazyace35:
Works great I had to go to settings/accounts/Google and sync browser after installing

---------- Post added at 07:56 PM ---------- Previous post was at 07:31 PM ----------

---------- Post added at 07:59 PM ---------- Previous post was at 07:56 PM ----------
[Verizon Galaxy Note 3 Themes and Apps] yakitori2:
Thanks for screens! Yes I forgot to mention that. After install go to settings/accounts and check browser...then it'll sync.
[Verizon Galaxy Note 3 Themes and Apps] suzook:
Unfortunately this doesn't work with beans 2
[Verizon Galaxy Note 3 Themes and Apps] yakitori2:
more info
[Verizon Galaxy Note 3 Themes and Apps] suzook:
It just fc. ..won't open. Bummer
[Verizon Galaxy Note 3 Themes and Apps] yakitori2:
Did u flash or move apps to system? Be sure that browserproviderproxy.apk is renamed then reboot

u can also try downloading the aosp browser on the market and see if bookmarks sync will work .
[Verizon Galaxy Note 3 Themes and Apps] suzook:
Yup...none of this works on beans2...not sure what has changed.
[Verizon Galaxy Note 3 Themes and Apps] yakitori2:
Idk...beans and hd are modified stock...not even sure what they would've changed from stock. Probably seevices.jar heavily modified.

I run stock rooted...De bloated so idk what to do for ya. Something within the rom. Not the browser zip
[Verizon Galaxy Note 3 Themes and Apps] yakitori2:
Try turning off chrome
[Verizon Galaxy Note 3 Themes and Apps] sudermatt:
This worked in HD 1 and 1.1...but broke in 2....This is kind of a big deal to me so I may revert
[Verizon Galaxy Note 3 Themes and Apps] suzook:
Agreed....not sure wtf happened.
[Verizon Galaxy Note 3 Themes and Apps] yakitori2:
You will have to see what sbreen did differently in hd2. It should technically work since isms built off the same mj7 base but idk what would be going on to cause it to not work.
[Verizon Galaxy Note 3 Themes and Apps] guthrien:
I'm glad it's not just me selfishly. My favorite browser and I just can't get it going.
[Verizon Galaxy Note 3 Themes and Apps] KennyG123:
As there is no download here

Thread closed
[8125, K-JAM, P4300, MDA Vario General] Charley's Angel:
Has anyone figured out how to remap the volume slider on the Wizard?

I hardly ever want to change volume, just turn on/off vibrate mode which is a single keypress anyway, but i would really like it to be an up/down control like my old Dell Axim.

I know it functions like this in IE full screen mode, but I really want it for everything (especially MS Reader).
[8125, K-JAM, P4300, MDA Vario General] joebongo:
I think a lot of people would like this. It allows a better grip on the phone whilst moving within the app you're using (eg: MS Reader).

Any guru's got an idea about this one?

Joe
[8125, K-JAM, P4300, MDA Vario General] mrbuz:
Remapping

Absolutely neccessary thing to fix (volume slider)!

And as using double-language hard-keyboard layout I am in desperate need to remap the change-layout sequence.

What about remapping in this OS, is it possible to do something?
[8125, K-JAM, P4300, MDA Vario General] uczmeg:
Someone did this on the Magician (found it in that group on here at the time), I remember finding it very useful!

If someone could do a Wizard version that would be great!
[8125, K-JAM, P4300, MDA Vario General] joebongo:
Solution Found

Here is how you do it (and it was on the Magician forums, thx for the tip :wink: ):

Install the program found at the URL below, or from the attachment as you wish.

When you get the setup screen, choose "Do not handle" for all except the volume slider, which is set to up/down.

Ok it, and there you go, slider is now up/down and works in MS Reader, Today screen, and general folder browsing.

It says on the site not to put it on any device not listed as compatible, which doesn't include the Wizard, but "He who dares, wins..."

I am well chuffed with it. Now I am all ready for my commute on Monday. :)

http://ae.inc.ru/download/AEBPlus.zip

Joe
[8125, K-JAM, P4300, MDA Vario General] guttrhead:
Unless this is a new version. DO NOT USE AEB+ WITH A WIZARD

I tried AEbuttons plus awhile ago and It deleted a couple of my buttons. I dont think it is meant for a device with as many buttons as the wizard. I had to go in and manually create the buttons again. I told it to handle all buttons though. Maybe telling it to only handle the volume slider doesn't cause this problem. I won't try it again until they actually say the wizard is compatible.