yashsingh1/xdaforums huggingface dataset:
[Galaxy Ace S5830 Q&A, Help & Troubleshooting] n0p3zz:
Hardly,as he is suspended from forum :P
[Galaxy Ace S5830 Q&A, Help & Troubleshooting] panaderodc:
Tried to edit post as I saw the account was disabled - had to wait five minutes. Thanks for the quick snark!
[Galaxy S 4 Accessories] rlrmineiro:
Hi everyone! Check this out...

https://www.youtube.com/watch?v=e9e6SZRxU_o&feature=youtube_gdata_player

For all of those who, like me, want to have the possibility of fm radio...

Seems like a compromisable workaround... ordered myself one from ebay yesterday. Should have it in a couple of days.

Sony mw600

Please leave your comments!
[Galaxy S 4 Accessories] ozkaya:
When you receive your headphones, could you please check if Song titles (stock music player) and Caller IDs (caller name) show up on the screen?
[Galaxy S 4 Accessories] rlrmineiro:
Will test them extensively... as far as i could see from a youtube video with a motorola phone, the callers number does show up...
[Galaxy S 4 Accessories] JayceOoi:
Song title is working on stock music player and Play Music. But only caller number show up, no caller name.
[Galaxy S 4 Accessories] mythoc:
caller name shows up sometimes on my mw600. I own it for about 2 years now. totally worth the money.

Στάλθηκε από το GT-I9505 μου χρησιμοποιώντας Tapatalk 2
[Galaxy S 4 Accessories] Netuser:
looking at reviews on amazon this is an old device with so many negative reviews. Be careful it don't seem to be worth
[Galaxy S 4 Accessories] tiggerbcn:
I have them, but does not connect with bt of S4, I tested with several cooked roms. With the Galaxy Nexus I worked perfectly.
[Galaxy S 4 Accessories] nmnm4alll:
I have ordered a similar one last year from ebay, works great i do not use it with my headphones tho, i use it in my aux cable in my car, so I have a bluetooth in my car for only $23 :D

http://www.ebay.com/itm/Bluedio-DF620-Bluetooth-3-0-Stereo-Headset-Caller-ID-Black-/130909660622
[Galaxy S 4 Accessories] torroa:
I've had this bluetooth headset a few years. The biggest drawback is that it only got Bluetooth profile 2.1, but all the A2DP functions and Caller ID and played music track is shown. I can be paired with 3 different devices and it has an RDS enabled FM radio. I have yet to find a newer small stereo bluetooth headset with radio at this price. I'am however thinking about getting a Sony SBH50 as it looks like a decent upgrade. It got Bluetooth 3.0 and also an FM radio function. The MW600 is probably not a bad choice, but why get 5 year old technology when you can get the newest at almost similar cost?
[Galaxy S 4 Accessories] rlrmineiro:
Wasn't aware of this one... looks pretty high end! I wonder if the message reading options are available for the s4... would have gotten this one if i had seen it before. In white to go along with my phone.
[General Topics] Swifty:
Well I've had my XDAIIs for about 5 days now and the power button seems to be randomly not working. It won't turn on if I use the power button on the top (comes on about 1 in 10 presses), but if I press any of the other buttons it comes on. Same trouble when it comes to turning it off!

I'm gonna try a hard reset in a bit just to make sure its nothing software related doing something to the button configuration.. but if it still doesn't work where do I stand in terms of getting it replaced ?

I got it from Uplands, am I right in thinking because its less than 14 days old I am entitled to an exhange for a new unit straight away ?

Cheers
[General Topics] dcs:
Sounds like a faulty power button to me. You should be able to have it replaced, no problem.
[General Topics] gary333:
Within the 14 day money back terminator you can demand an exchange or your money back.

Between 14 days and 28 days if a fault develops you can request for a new unit to be issued.

After 28 days to 12 months you have to make a warranty claim.

Hope you got it sorted, what ever the problem was.
[Nexus 7 General] oldblue910:
Hey everyone,

If anyone has bought a new WiFi-only or 3G Nexus 7 in the last week or two, can you check and see if your device shipped with JDQ39B? If it did, please let me know. I need two pieces of information from your device. One is the value of ro.build.date.utc in /system/build.prop and the other is the bootloader version. You can get this by rebooting your N7 into bootloader mode. The version will show right on-screen. Also, if anyone has a 3G N7 with JDQ39B, please let me know the baseband version as well. You can find that in Settings - About Tablet.

Thanks!
[Nexus 7 General] armada786:
I just ordered one and it'll arrive either today or tomorrow so I'll tell you what I know as soon as I get it.
[Nexus 7 General] oldblue910:
Thank you! It's much appreciated. Out of curiosity, did you get a WiFi-only or a 3G model?
[Nexus 7 General] armada786:
Mine is WiFi only.
[Nexus 7 General] oldblue910:
Cool. Well definitely check in when you get it and let me know. Thanks!
[Nexus 7 General] simarilon:
Hi,

I have one with this number, but I am not on stock anymore.

I am on XenonHD and Franco's nightly.

If I can help with information, please let me know

Best regards

Simarilon

--> Boot loader is 4.10

ro.build.date.utc=1367483752
[Nexus 7 General] oldblue910:
Is that build date from your old stock JDQ39B ROM? Also are you sure the Bootloader is 4.10? Older devices now have 4.18, so if you got a new one with JDQ39B, it should have at least 4.18. Thanks!
[Nexus 7 General] simarilon:
Checked again, with my glasses.... it is 4.18 sorry is damming small

Gesendet von meinem Nexus 7 mit Tapatalk 2

---------- Post added at 12:55 PM ---------- Previous post was at 12:53 PM ----------

I don't know if a custom Rom change the build date

Gesendet von meinem Nexus 7 mit Tapatalk 2

---------- Post added at 12:56 PM ---------- Previous post was at 12:55 PM ----------

I use the one from XenonHD

Gesendet von meinem Nexus 7 mit Tapatalk 2
[Nexus 7 General] oldblue910:
The custom ROM definitely changes the build date. Thanks for the bootloader info, though. It appears new devices are shipping with JDQ39B while older devices are remaining on JDQ39.

If anyone can provide the UTC date from the stock JDQ39B build.prop file, I'd greatly appreciate it. Thanks!
[Nexus 7 General] Macmee:
WHAT THE!

I have an old device that was serviced in the ASUS repair in Ontario (man, I had to be patient when it shipped from Nova Scotia to Ontario (American? Don't know where Nova Scotia is? It's that island looking thing that's not an island at the bottom of Canada (don't know what Canada looks like? Jesus where did you go to school?))).

They gave me a new LCD which is what I asked for, and for some strange reason they gave me a new battery, writing "battery error" on my fix sheet. God knows why they did that, the battery was perfectly fine but who am I to complain.

I turn on my precious N7 when it gets here (did I mention I had to be patient when I waited for it to ship?). Bam, JDQ39B hits me right in the face.

WHO KNOWS IF I CAN USE WUFRESH'S TOOLKIT TO UNLOCK AND ROOT THIS THING. GOD DAMNIT NOW I'LL HAVE TO SPEND THE NEXT HOUR AND A HALF GOOGLING THIS EXTRA B TO MAKE SURE I DONT BLOW THE DAMNED THING UP.

(and knowing me, five minutes after my N7 arrived from the repair center, I'll of hard bricked it and will be packaging it up to ship off again).

You just wait and see!
[Nexus 7 General] oldblue910:
If you don't mind, could you please get the value of ro.build.date.utc from /system/build.prop on the stock JDQ39B ROM before you do any flashing? Thanks!
[Nexus 7 General] Macmee:
Yeah sure but remind me again, do I have to root to gain access to /system/? I have a memory like a rock, not as solid as a rock just like a rock - lacking and non-existent in every single way.

edit:

ro.build.id=JDQ39B

ro.build.display.id=JDQ39B

ro.build.version.incremental=592281

ro.build.version.sdk=17

ro.build.version.codename=REL

ro.build.version.release=4.2.2

ro.build.date=Mon Mar 4 20:06:29 UTC 2013

ro.build.date.utc=1362427589

ro.build.type=user

ro.build.user=android-build

ro.build.host=vpbs27.mtv.corp.google.com

ro.build.tags=release-keys

ro.product.model=Nexus 7

ro.product.brand=google

ro.product.name=nakasi

ro.product.device=grouper

ro.product.board=grouper

ro.product.cpu.abi=armeabi-v7a

ro.product.cpu.abi2=armeabi

ro.product.manufacturer=asus

ro.product.locale.language=en

ro.product.locale.region=US

ro.wifi.channels=

ro.board.platform=tegra3

edit 2: bootloader version 4.21 (WTH?) Also MASSIVE light leak on the right side of screen, spreads when pressing.

me: ASUS, I have a giant light leak on the screen.

ASUS: send your n7 back to us we will give you a new LCD

* gets new lcd with worse light leak*

:/
[Nexus 7 General] oldblue910:
No, you don't need root. Just open up your favorite file manager application, browse to /system and open up build.prop as a text file. Inside, you'll see a line that begins with ro.build.date.utc=<some number>. I need to know what <some number> is.

Thanks!
[Nexus 7 General] oldblue910:
THANK YOU!!!
[Nexus 7 General] Macmee:
No problem, do you know if my bootloader version or this B will mess me up in any way if I attempt to install a custom recovery etc?
[Nexus 7 General] oldblue910:
It'll be fine. That's the beauty of Nexus devices. Bootloaders never make it so you can't root or install custom ROMs. Nexus devices don't lock bootloaders down. Just use your toolkit as if it were JDQ39 and you'll be fine.
[Nexus 7 General] Macmee:
Thank you for your help, although the toolkit wasn't able to find my device, and I just hooked it up to the iMac and did an adb devices and don't see it either. Ehhhhhhh this is quite the mess.

edit: I'm an idiot, I was doing adb devices and not fastboot devices. I got it unlocked using the command line, looks like I'll have to do everything from it and not the toolkit. Bloody Windows. Didn't even need to install drivers for OS X.
[Nexus 7 General] oldblue910:
Did you enable USB debugging in your stock ROM first?
[Nexus 7 General] Macmee:
Thanks for your help, I think it's a driver situation on Windows. Just going to look for a toolkit for OS X instead and if that fails I'll just do it all from adb and fastboot myself.
[Nexus 7 General] oldblue910:
Doing it yourself is always better than using toolkits anyway. :) And it only takes an extra 5 minutes if that.
[Nexus 7 General] Macmee:
Until something goes wrong anyway:

mv: can't rename 'recovery-from-boot.p': No such file or directory
[Nexus 7 General] oldblue910:
That error message means absolutely nothing. recovery-from-boot.p will only ever be found on firmware that was updated via an OTA update. Since you're using the firmware your device shipped with, recovery-from-boot.p and install-recovery.sh won't exist.
[Nexus 7 General] simbin:
Has anyone successfully rooted JDQ39B yet? I also got my Nexus 7 serviced for a broken screen and it came back with this ROM. Nexus Root Toolkit doesn't show the new ROM yet, so I'm unsure if it's safe to proceed, thanks.
[Nexus 7 General] sgt. meow:
4.20 bootloader you say? Is it possible to get a dd IMG of the bootloader and upload it on XDA?
[Nexus 7 General] oldblue910:
Nevermind
[Nexus 7 General] simbin:
JDQ39B is 4.2.2
[Nexus 7 General] sgt. meow:
I was talking about the boot loader version. Something entirely different. :D
[Nexus 7 General] veeman:
Just do it manually. It's easy and guaranteed to work on a nexus device.
[Nexus 7 General] Logomotph:
I find it funny how people use toolkits to run a simple 3-word command. Just do it manually.

From a Nexus 4 bathing in Jelly Beans
[Nexus 7 General] player911:
Fastboot oem unlock doesn't root the device. You have to push several APKs over using multiple commands and know their placements within the OS. Let's not over simplify it.

My other new N7 came with 4.2.2 as well.
[Nexus 7 General] Logomotph:
Actually, you just need to copy the su zip over, which can be done while booted. The only other command you need to write is fastboot flash recovery whatever.img and click/tap a few times to flash su. My opinion is that people who root their devices should know these things as it's really simple.
[Nexus 7 General] mlvNN:
Any method for rooting this? Im new with rooting so is there an easy tutorial? For the JDQ39B
[Nexus 7 General] spitfire2425:
Just like normal. Unlock bootloader and fastboot flash recovery then flash an su.zip.
[Nexus 7 General] mlvNN:
Okay i think i unterstand a Bit of that. Should i just Flash the Su.zip per CWM?

And one last question. Is it dangerous to use this for JDQ39B?
[Nexus 7 General] player911:
I agree to some extent but as you described... is not just a simple 3 word command to root. Some people don't really care about learning the under workings of this or that.

Honestly the best way [to learn and to do] is to download the Unlocker/Rooter ToolKit. This is not only easy, but you can edit the batch files to see the actual command line code (assuming you are using a Windows PC). Not only is it easier but also offers a few other tools/commands to assist in the event something goes wrong, also viewable when editing the batch files in Notepad if you are interested).

I would never put a noob behind the wheel of a car and tell them to give it their best shot. The Toolkits act like cabs; they get you to where you want to go and you can also pay attention and learn something. Once you understand the PROCESS and see how the commands work, then you can experiment if you want.
[Nexus 7 General] Logomotph:
True, but this lack of knowledge often results in another "I flashed X and it doesn't work, how do I do Y?" thread. I don't know, I guess I like to know everything I can about how something works before I start modifying it. :)
[Nexus 7 General] player911:
Assuming you have all the files you need the process basically consists of "fastboot oem unlock" which will format your device completely (including any saved data on the internal memory).

Unlocking your device will allow you to push a recovery "fastboot flash recovery recovery.img" [where recovery.img will be downloaded from either TWRP or ClockWorkMod Recovery]

Once you have TWRP or ClockWorkMod recovery installed on your device, you should be able to just "fastboot reboot recovery" [I think] and it should boot you into your custom recovery. I personally use ClockWorkMod, whatever is the latest for the N7. Typically the toolkits will come with a version of ClockWorkMod.

From the Recovery, you can either just flash a custom rom (what I do) or try to find a flashable su.zip or whatever you need. I don't really see the point in rooting a stock rom but whatever floats your boat.

A toolkit will fetch all the needed files and step you through everything if you are unsure of the process.
[Nexus 7 General] cmstlist:
Got a replacement N73G two weeks ago on a device swap. It shipped fresh out of the box still with JVS15S, the original 4.2 build that didn't have lock screen widgets. This is exactly what my original shipped with on launch week last year.
[Nexus 7 General] player911:
I believe they shipped with 4.1 during launch. Then 4.1.1, then 4.1.2, then 4.2, and now 4.2.2.
[Nexus 7 General] oldblue910:
The 3G models shipped with 4.2/JVP15S. They didn't come out until four months after the WiFi models.
[Nexus 7 General] player911:
I always forget about the 3G models.
[Nexus 7 General] cmstlist:
Right, JVP15S. When the N73G first came out it shipped with that build (which was 4.2), and then immediately got a system update to a newer also-4.2 build that added in the lock screen widgets. Apparently the units that ship out today still have that same old build.

Sadly my replacement unit has some "creak" to it on the left side, but the reason I sent it out was for a defective speaker on the previous one.
[Nexus 7 General] BrianDigital:
Copy and pasting terminal commands don't teach anything either.
[Nexus 7 General] Mach3.2:
Copy and pasting terminal commands don't work for commands with tags.(e.g. java -jar apktool.jar...)

Beamed from my Grouper
[Nexus 7 General] kypeth:
I received a brand new 16gb wifi version yesterday, shipped with 4.1.2
[Nexus 7 General] BrianDigital:
Ah and that's used in rooting
[Nexus 7 General] Mach3.2:
Oh wait, I don't even remember using it in either unlocking or rooting..

Figured it out while trying to decompile framework-res.apk to mod the nav bar..

Beamed from my Grouper
[Nexus 7 General] BrianDigital:
And now back to what I said before
[Nexus 7 General] AndyMark:
JDQ39B UPGRADE during repair.

I had sent in my Nexus 7 to the repair facility in Ontario for a battery charging problem. I sent it in with a rooted device and got it back yesterday with the jdq39b rom and now it's not rooted anymore.

I'm scared to root / unlock/flash it. can I use the Google Nexus 7 Toolkit? as it doesn't list the jdq39 b rom, just the jdq39 rom as selection 15. if i try flashing, and saying i have the non-b version, will I end up bricking it and have to send it in for service for a second time?

Did you ever have success in flashing yours?

Andy in Vancouver
[Nexus 7 General] Mach3.2:
When in doubt, don't screw around with anything.

Beamed from my Maguro.
[Nexus 7 General] oldblue910:
If you use your toolkit, root it using the JDQ39 method and you'll be fine.
[Nexus 7 General] AndyMark:
Rooting Build JDQ39B (upgraded) from repair depot in North Bay, Ontario

and what are the three magic words to do the root/unlock manually on my nexux 7 which was sent in for a battery repair. I sent it in rooted and having 4.1.2, it came back ten days later with a build number JDQ39B and was no longer rooted...

Did you ever root it? If so, please tell me how.

Andy
[Nexus 7 General] veeman:
Here you go man. This guide should walk you through the rooting process.

http://www.nexus7nexus10.com/forum/...-7-windows-keep-root-through-ota-updates.html

Also your username is AndyMark. Are you from FRC by chance?
[Nexus 7 General] Trmyers515:
nexus 7

have a nexus 7 with JDQ39B....ANY SUCCESS ..ANYONE ON UPDATE to 4.3
[Verizon Samsung Galaxy Note II] DerTeufel1980:
This Kernel is based off the sources of AndreiLux Perseus Kernel (alpha35).

If you consider to thank me, please also consider to thank him http://xdaforums.com/showthread.php?t=1927852

special greetings:

to the guy in the general section who told me being kind of stupid, because NO kernel could boot aosp and tw at once :p

:laugh::eek:

Many Thanks to:

- RichMD (I wouldn't have this device without him)

- Gokhanmoral

- Andreilux

- DAGr8

- simone201

- ptmr3

- Stratosk

- RolloS

- kasper_h

- all the others mentioned in the changelogs
[Verizon Samsung Galaxy Note II] DerTeufel1980:
more to come ...
[Verizon Samsung Galaxy Note II] stryver:
Awesome.
[Verizon Samsung Galaxy Note II] TheLoonyRebel:
I'm assuming MHL (and HDMI) doesn't work at this point on this dual boot kernel?
[Verizon Samsung Galaxy Note II] DerTeufel1980:
I don't have anything to test mhl/hdmi.

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Verizon Samsung Galaxy Note II] droidstyle:
Nice work!!
[Verizon Samsung Galaxy Note II] Herk718:
Will this work on the Sprint Galaxy Note II L900?
[Verizon Samsung Galaxy Note II] DisposableHero1985:
im getting status 7 error when flashing the recovery, any ideas?

edit btw im on a sprint note 2 using twrp
[Verizon Samsung Galaxy Note II] honki24:
Please see this post by the OP on the Sprint (L900) forum: http://xdaforums.com/showpost.php?p=41931707&postcount=52

In short - yes.
[Verizon Samsung Galaxy Note II] DerTeufel1980:
Yes, both cdma devices use the same kernel.

Anyone else getting this?

Is there something more in the error you get?

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Verizon Samsung Galaxy Note II] Herk718:
Well when I flashed the Verizon version on my sprint note 2, im getting endless boot loops...:confused:

P.S - Can we just use the kernel for single ROM support, or its only gonna work with dual booting?
[Verizon Samsung Galaxy Note II] shangrila500:
It works for both, you can use it to just run one rom or to dual boot. If you want to dual boot you need to install the recovery that has been modified by him too.
[Verizon Samsung Galaxy Note II] DisposableHero1985:
im getting assert failed error in twrp and as previous poster mentioned bootloop on the kernel
[Verizon Samsung Galaxy Note II] Herk718:
And on top of getting endless boot loops, its boot looping my stock boot animation *Not* the custom animation I have placed it data/local folder. (Indicatoring NO custom boot animation support on this kernel :(
[Verizon Samsung Galaxy Note II] DerTeufel1980:
Is it booting for someone on verizon device? Maybe sprint needs another initramfs.

To the status 7 error, have you tried flashing it from cwm, too?

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Verizon Samsung Galaxy Note II] DisposableHero1985:
i got status 7 in cwm too. i used cwm and cwm touch

i didn't see anything in the updater-script about it but i do know sprint writes /data on /dev/block/mmcblk0p17 instead of on /dev/block/mmcblk0p16
[Verizon Samsung Galaxy Note II] DerTeufel1980:
Oh well, found the issue with sprint. Trying to fix it asap.

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Verizon Samsung Galaxy Note II] Herk718:
No I'm using TWRP and its flashing successful without error, but reboots into boot loops... U can try changing the initramfs for us sprint users and see if that helps... And BTW I don't mind testing it out on my device if u like.
[Verizon Samsung Galaxy Note II] DerTeufel1980:
exactly, that is the reason for the bootloops. didn't think of it. :(

now i need the help of a sprint users.

please use adb shell, or terminal app, to run this command:

ls -l dev/block

and psate the output here. thanks
[Verizon Samsung Galaxy Note II] DisposableHero1985:
u0_a155@android:/ $ su

root@android:/ # ls -l dev/block

brw------- root root 7, 0 2013-05-28 12:30 loop0

brw------- root root 7, 1 2013-05-28 12:30 loop1

brw------- root root 7, 2 2013-05-28 12:30 loop2

brw------- root root 7, 3 2013-05-28 12:30 loop3

brw------- root root 7, 4 2013-05-28 12:30 loop4

brw------- root root 7, 5 2013-05-28 12:30 loop5

brw------- root root 7, 6 2013-05-28 12:30 loop6

brw------- root root 7, 7 2013-05-28 12:30 loop7

brw------- root root 179, 0 2013-05-28 12:30 mmcblk0

brw------- root root 179, 1 2013-05-28 12:30 mmcblk0p1

brw-rw---- system radio 179, 10 2013-05-28 12:30 mmcblk0p10

brw-rw---- system radio 179, 11 2013-05-28 12:30 mmcblk0p11

brw------- root root 179, 12 2013-05-28 12:30 mmcblk0p12

brw------- root root 179, 13 2013-05-28 12:30 mmcblk0p13

brw------- root root 179, 14 2013-05-28 12:30 mmcblk0p14

brw------- root root 179, 15 2013-05-28 12:30 mmcblk0p15

brw------- root root 259, 0 2013-05-28 12:30 mmcblk0p16

brw------- root root 259, 1 2013-05-28 12:30 mmcblk0p17

brw------- root root 179, 2 2013-05-28 12:30 mmcblk0p2

brw------- root root 179, 3 2013-05-28 12:30 mmcblk0p3

brw-rw---- system radio 179, 4 2013-05-28 12:34 mmcblk0p4

brw-rw---- system radio 179, 5 2013-05-28 12:31 mmcblk0p5

brw-rw---- system radio 179, 6 2013-05-28 12:30 mmcblk0p6

brw-rw---- system root 179, 7 2013-05-28 12:30 mmcblk0p7

brw------- root root 179, 8 2013-05-28 12:30 mmcblk0p8

brw------- root root 179, 9 2013-05-28 12:30 mmcblk0p9

lrwxrwxrwx root root 2013-05-28 12:30 param -> /dev/block/mmcblk0p7

drwxr-xr-x root root 2013-05-28 12:30 platform

brw------- root root 1, 0 2013-05-28 12:30 ram0

brw------- root root 1, 1 2013-05-28 12:30 ram1

brw------- root root 1, 10 2013-05-28 12:30 ram10

brw------- root root 1, 11 2013-05-28 12:30 ram11

brw------- root root 1, 12 2013-05-28 12:30 ram12

brw------- root root 1, 13 2013-05-28 12:30 ram13

brw------- root root 1, 14 2013-05-28 12:30 ram14

brw------- root root 1, 15 2013-05-28 12:30 ram15

brw------- root root 1, 2 2013-05-28 12:30 ram2

brw------- root root 1, 3 2013-05-28 12:30 ram3

brw------- root root 1, 4 2013-05-28 12:30 ram4

brw------- root root 1, 5 2013-05-28 12:30 ram5

brw------- root root 1, 6 2013-05-28 12:30 ram6

brw------- root root 1, 7 2013-05-28 12:30 ram7

brw------- root root 1, 8 2013-05-28 12:30 ram8

brw------- root root 1, 9 2013-05-28 12:30 ram9

drwx------ root root 2013-05-28 12:30 vold

root@android:/ #