yashsingh1/xdaforums huggingface dataset:
[Galaxy Note GT-N7000 Android Development] dev_freak:
Battery is sometimes bad, but I love this. I got some bugs anyway. In the browser app when you first login it goes on and on with checking and signing in, chrome is sometimes buggy, sometimes OK Google doesn't work from all screens.
[Galaxy Note GT-N7000 Android Development] rafi_android:
If you want to update to beta3, you must flash gapps as well. If you want to flash beta 3, use the kernel on the first post, boot to recovery, wipe data, wipe cache, wipe dalvik cache (optional), flash beta3, flash gapps, reboot, profit!
[Galaxy Note GT-N7000 Android Development] bauner:
here is my local manifest

<?xml version="1.0" encoding="UTF-8"?>
<manifest>

<remove-project name="CyanogenMod/android_bionic" />
<project name="bauner/cm-android_bionic" path="bionic" remote="github" revision="cm-12.0" />
<project name="bauner/cm-android_device_samsung_galaxys2-common" path="device/samsung/galaxys2-common" remote="github" revision="cm-12.0" />
<project name="bauner/cm-android_device_samsung_n7000" path="device/samsung/n7000" remote="github" revision="cm-12.0" />
<remove-project name="CyanogenMod/android_frameworks_av" />
<project name="bauner/cm-android_frameworks_av" path="frameworks/av" remote="github" revision="cm-12.0" />
<remove-project name="CyanogenMod/android_frameworks_base" />
<project name="bauner/cm-android_frameworks_base" path="frameworks/base" remote="github" revision="cm-12.0" />
<remove-project name="CyanogenMod/android_frameworks_native" />
<project name="bauner/cm-android_frameworks_native" path="frameworks/native" remote="github" revision="cm-12.0" />
<remove-project name="CyanogenMod/android_frameworks_opt_net_wifi" />
<project name="bauner/cm-android_frameworks_opt_net_wifi" path="frameworks/opt/net/wifi" remote="github" revision="cm-12.0" />
<remove-project name="CyanogenMod/android_hardware_broadcom_wlan" />
<project name="bauner/cm-android_hardware_broadcom_wlan" path="hardware/broadcom/wlan" remote="github" revision="cm-12.0" />
<remove-project name="CyanogenMod/android_hardware_libhardware" />
<project name="bauner/cm-android_hardware_libhardware" path="hardware/libhardware" remote="github" revision="cm-12.0" />
<remove-project name="CyanogenMod/android_hardware_ril" />
<project name="bauner/cm-android_hardware_ril" path="hardware/ril" remote="github" revision="cm-12.0" />
<project name="bauner/cm-android_hardware_samsung" path="hardware/samsung" remote="github" revision="cm-12.0" />
<project name="bauner/cm-android_hardware_samsung_slsi_exynos4" path="hardware/samsung_slsi/exynos4" remote="github" revision="cm-12.0" />
<remove-project name="CyanogenMod/android_packages_services_Telephony" />
<project name="bauner/cm-android_packages_services_Telephony" path="packages/services/Telephony" remote="github" revision="cm-12.0" />
<remove-project name="CyanogenMod/android_system_core" />
<project name="bauner/cm-android_system_core" path="system/core" remote="github" revision="cm-12.0" />
<remove-project name="CyanogenMod/android_system_vold" />
<project name="bauner/cm-android_system_vold" path="system/vold" remote="github" revision="cm-12.0" />
<project name="bauner/android_kernel_samsung_smdk4412" path="kernel/samsung/smdk4412" remote="github" revision="cm-12.0" />
<project name="CyanogenMod/android_packages_apps_SamsungServiceMode" path="packages/apps/SamsungServiceMode" remote="github" revision="cm-12.0" />

</manifest>
[Galaxy Note GT-N7000 Android Development] bauner:
3. can come from an dirty or broken usb connector
[Galaxy Note GT-N7000 Android Development] qdh1502:
That mean the Beta 3 will wipe system partition ? So we have to flash again gapps every time we flash this Beta 3 (coming from Beta 2 without wipe data for exemple) ?
[Galaxy Note GT-N7000 Android Development] bauner:
yes after every rom flash you need to flash gapps too
[Galaxy Note GT-N7000 Android Development] action_papst:
battery drain seems to be gone for me by now. had it twice the first day of using beta3, now everything seems to be fine :3 thank you, [MENTION=799465]bauner[/MENTION].
[Galaxy Note GT-N7000 Android Development] I_android:
+1 [MENTION=799465]bauner[/MENTION]

I also made this request in past...may be you have missed it. bauner could you please release beta3 stock kernel installable zip? It would be really great to have if someone wants to return back to stock kernel after trying/testing third party kernel. Otherwise we are forced to flash whole ROM again.

Thanks a lot in advance
[Galaxy Note GT-N7000 Android Development] ishanbhatnagr96:
Which kernel are you using?
[Galaxy Note GT-N7000 Android Development] roman gabriel:
phone calls

anyone having trouble making phone calls?i'm using beta 3 but sometimes when i want to make a call i'm getting this message:call not sent
[Galaxy Note GT-N7000 Android Development] action_papst:
stock beta3
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] belu:
I flash my V1605 with the exe file : RUU_Hermes_HTC_WWE_2.05.255.1_6275_1.34.00.10_108_Test.exe and after reboot my devis was an Herm100.

Why ? it's probleme ? what can i do for reswitch in Herm200 ?
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] Pyranwolf:
It's not a problem, unless you're really bothered about the digit being different. :D
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] belu:
How can i change this ?
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] Olipro:
ignore it, c'est pas probleme!
[Nexus 9 Q&A, Help & Troubleshooting] foxmeister:
Has anyone managed to get ABD sideload working from stock recovery?

I'm trying to sideload the latest OTA.

I have ADB up and running fine when the N9 is fully booted, but when I drop into recovery and select the option to sideload via ADB, I get the Windows "chime" for a new device, and unknown device (Volantis) appears in the device manager, for which I can find no driver.

No driver means no ADB and thus no sideload.

Thanks,
[Nexus 9 Q&A, Help & Troubleshooting] daniii88:
Hi, replace the original android_winusb.inf file with this modified one in your google usb drivers folder. Right click on it and select install.

Modified it for myself right now, because I had exactly the same problem like you.

Please let me know if it was successful...
[Nexus 9 Q&A, Help & Troubleshooting] bobjbain:
Thanks for trying but it doesn't work for me, when I try to install I get an error dialog :-

"The hash for the file is not present in the specified catalogue file. The file is probably corrupt or has been tampered with"
[Nexus 9 Q&A, Help & Troubleshooting] ForcedZucchini:
I'm also getting this problem. Any solution?
[Nexus 9 Q&A, Help & Troubleshooting] Alcarullo:
I have same problem... waiting for solution....
[Nexus 9 Q&A, Help & Troubleshooting] ManBearBull:
I had the same issue and have now successfully been able to sideload (Windows 8.1).

The original issue seems to be that the latest google driver I downloaded did not have the correct device id in the android_winusb.inf for the nexus 9 when in recovery mode (though the driver did work for issuing adb commands to unlock the bootloader; I guess the hardware id is different when connected in adb recovery mode?). The file daniii88 provided presumably fixes this in the same way I did, by adding the device id reported under device manager to the generic nexus devices listed in the android_winusb.inf file as follows:

%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D001

I did this under both the 32 and 64 bit headers just in case. I made an account just to post this solution, so I can't post links, but searching for "nexus 7 adb recovery driver" shows the same thing happened with the nexus 7 at one point.

Now, with the modified version of the android_winusb.inf file windows won't let the driver install because the driver signature does not match since it's been altered. The trick to forcing windows to use the driver anyways is to reboot windows in "disable driver signature verification" mode. Search for "how to disable driver signature verification on 64 bit windows 8.1 so that you can install unsigned drivers". Once rebooted, reinstall the altered driver under device manager (I did this while the device was in recovery mode waiting for adb sideload). Windows will warn you along the lines of the driver has been tampered with, but will allow you to use it. The driver should successfully install and the device should appear under "adb devices" from the command line. Furthermore, sideload should now work.

Hopefully this helps anyone else encountering this.
[Nexus 9 Q&A, Help & Troubleshooting] ram130:
After you did this. You were able to side load the OTA even with the non upgraded recovery?

Sent from my Nexus 7
[Nexus 9 Q&A, Help & Troubleshooting] ManBearBull:
109

Sorry, should have said I was already on the upgraded (LRX21Q) recovery before going through these steps. The unaltered driver i initially used worked to communicate with the nexus 9 when booted or at the bootloader screen, but not when I was in recovery. Therefore i was able to unlock my bootloader and update the recovery with unaltered drivers, but had to change the driver to get adb to work when in recovery.
[Nexus 9 Q&A, Help & Troubleshooting] bobjbain:
So, the original attachment works properly, it was unsigned driver verification that was stopping it being installed, should have realised that from the start, thanks for pointing me in the right direction.

No, it was telling me my old version isn't what it was expecting. I must be suffering from the recovery not being updated properly "bug".

My build.prop definitely has the right release keys in it.

Once question for those that know, in the update package there is a metadata file which contains :-

post-build=google/volantis/flounder:5.0/LRX21Q/1573789:user/release-keys
post-timestamp=1415397802
pre-build=google/volantis/flounder:5.0/LRX21L/1546449:user/release-keys
pre-device=flounder

Can we just not change the pre-build to that that is in the error message? (flounder:L/LFW73W/1491895:user/release-keys)??
[Nexus 9 Q&A, Help & Troubleshooting] ForcedZucchini:
So I replaced the android_winusb with the file provided and rebooted without driver verification mode. But it is still not working.

Under device manager it still shows the exclamation mark on Volantis. Did I miss a step?
[Nexus 9 Q&A, Help & Troubleshooting] daniii88:
Maybe you have another Device ID... try to follow this procedure http://blog.dantup.com/2012/10/fixing-adb-device-not-found-with-nexus-7-in-recovery-mode/
[Nexus 9 Q&A, Help & Troubleshooting] simmac:
This is Googles fault:

You remember the very first update you received during setup?

Yeah, and Google made a mistake with this update: They updated the system, but not the recovery, which means, there is now a version conflict between the recovery and the system, which prevents OTAs from installing.

You can't do anything about it until Google fixes this with another Update, except flashing the new recovery from the image.
[Nexus 9 Q&A, Help & Troubleshooting] bobjbain:
Have you tried updating the driver in device manager?
[Nexus 9 Q&A, Help & Troubleshooting] cor_mann:
After replacing the android_winusb file and rebooting the PC without driver verification mode, did you go back into Device Manager and update the driver using the modified driver version for ADB? I manually entered the device ID info into the winusb file instead of using the provided file, so I'm not entirely sure that the process is the same, but it seems like it should work.

1. Replace the android_winusb file with the attached version. If that doesn't work, open the file in notepad and manually enter the device id IAW ManBearBull's post;

2. Reboot without driver verification mode; and

3. Go into device manager and update the ADB driver with the modified driver file.
[Nexus 9 Q&A, Help & Troubleshooting] reijndert:
Finally worked, running "R" firmware now. There is not even een factory image available, just this OTA upgrade R-from-Q.

Cannot imagine why the device in recoverymode is not recognised ( unknown device Volantis ) and we need to play "dirty" to install the driver.

Seems so "immature" from Google.
[Nexus 9 Q&A, Help & Troubleshooting] lotrfan18:
Different Hardware ID?

So I replaced the android_winusb and it's still not letting me see the device in adb in fastboot. I can see it when it boots up normally. However, I am seeing that when I boot into fastboot, it gives me a hardware id of USB\VID_18D1&PID_4EE0 and not USB\VID_18D1&PID_D001 that was said in previous posts. Right now in Device Manager it's seeing the tablet as an "Android Bootloader Interface" instead of the CompositeAdbInterface I want. Should I change the inf file to put that hardware id as a CompositeAdbInterface instead of a SingleBootLoaderInterface like it currently is?
[Nexus 9 Q&A, Help & Troubleshooting] bobjbain:
That's because you're in bootloader not recovery, when you go into recovery and then do the "adb sideload" option that is when you get the D001 device ID.
[Nexus 9 Q&A, Help & Troubleshooting] ForcedZucchini:
I was able to resolve my problem, thanks for everyone's help.

I simply went into device manager>update driver software>browse my computer for driver software>let me pick>select "ADB Android Device"

After this I downloaded Minimal ADB and Fastboot from here http://xdaforums.com/showthread.php?t=2317790 and it was able to work successfully.
[HTC Wildfire S] gaga666:
Hi guys.

I am a noob in device flashing and stuff, my knowledge is limited to installing Cyanogenmod following the manual.

So the task is challenging for me: digitizer broke on my Wildfire S and all I want is to backup contacts (there was no sync with google). The device was in pristine state (usb debugging off, usb charge only). So my plan was to install Clockwork recovery, make a full backup on SD card and then fetch the contacts from that image somehow. However, I haven't succeded so far and probably destroyed the data. But maybe there is still a hope!

I was able to flash CWM via fastboot and it went ok. However, the phone won't boot into recovery hanging on htc logo. Probably bootloader is incompatible with CWM? But I haven't found any manuals on bootloader-recovery compatibility. Maybe you guys know how to make a recovery boot?

Thank you!

*** UNLOCKED ***

MARVEL PVT SHIP S-ON RL

HBOOT-1.09.0099

CWM 5.0.2.0-saga

PS the phone boots fine into normal mode but the screen seem a bit wierd: the calendar widget and desktop icons are gone (see attachment).
[HTC Wildfire S] aWFSuser:
From where did you get the recovery?
[HTC Wildfire S] gaga666:
From clockworkmod.com/rommanager, link to image: download2.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.8-marvel.img
[HTC Wildfire S] aWFSuser:
That should work. You can try

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

or

http://xdaforums.com/showthread.php?t=2605331
[HTC Wildfire S] gaga666:
I tried it again and it worked!!

Probably flashing gone wrong the previous time. However, I'm still unable to extract contacts: the database seems to be empty. I opened data.yaffs2.img generated by CWM with Yaffey, exported com.android.providers.contacts/databases/contacts2.db which is 129kb and opened it with sqlite browser. All tables are either empty or consist of 1 row (I checked tables contacts, raw_contacts, data and some more. Maybe HTC stores contacts elsewhere?
[HTC Wildfire S] aWFSuser:
Have you tried this - http://dorimanx.suckup.de/dorimanx-kernel-for-sg2-i9100/howto-sqlite-android-app-databases/

Android may store data in a format not understandable by all browser.
[HTC Wildfire S] gaga666:
Yes, I tried console sqlite3 in Ubuntu as well. Select shows nothing and SELECT count(name) FROM view_v1_phones yields 0
[HTC Wildfire S] gaga666:
I also uploaded the database to dropbox (I'm pretty sure it's empty, just in case someone could point out it's corrupted or it's the wrong database): https://www.dropbox.com/s/2t5sqlefos5717p/contacts2.db?dl=0
[Galaxy Note 10.1 (2014 Edition) General] 22sl22:
17 November 2014:

Goal has been reached and tablet is now in the hands of RaymanFX. Still feel free to support and donate to help him continue to prepare for his upcoming works. You can see his progress at github.com/raymanfx and

http://review.cyanogenmod.org/#/q/status:open+exynos,n,z

Under Christopher Hesse

Hello everyone,

I am creating this thread on behalf of [MENTION=3463426]RaymanFX[/MENTION] , a recognized developer who needs a device to develop for us.

http://xdaforums.com/member.php?u=3463426

He is looking to develop for the P600, WiFi only model and is looking to make AOSP/CM roms and kernels for us.

Here is a previous thread of his: http://xdaforums.com/find-7/orig-development/rom-teameos-revival-nightlies-t2826587

And here is a list of previous threads: http://xdaforums.com/search.php?searchid=319162976

Quote by RaymanFX:

Original thread: http://xdaforums.com/galaxy-note-10-2014/general/galaxy-note-10-1-2014-exynos-developer-t2936508

He is very committed to getting this device and developing for us so let's get him this device. He needs at least $300 so just write below how much you would be willing to donate if the funds were raised for the device. I will update this post with the names and how much people are willing to donate :good:

If at least 30 people donate say $10 for example then we can do this easily. I pledge $10 dollars so lets get this started!!

List of donations so far:

Euro:

22sl22: €10

[MENTION=4400874]r4yN[/MENTION] €20

[MENTION=4728562]benni_1994[/MENTION] €20

[MENTION=6007469]GrimReaper1908[/MENTION] €15

[MENTION=4174709]ollimi1[/MENTION] €10

[MENTION=1112883]henriavelabarbe[/MENTION] €25

[MENTION=4422075]murmlgrmpf[/MENTION] €10

[MENTION=2427660]TOMMY1985[/MENTION] €10

[MENTION=6171066]zazael[/MENTION] €10

[MENTION=5663158]rglebien[/MENTION] €10

[MENTION=6177454]SubZeroEffort[/MENTION] €20

Dollars:

[MENTION=4359006]emilycloud[/MENTION] $20

[MENTION=1869257]mrtoast[/MENTION] $30

[MENTION=3361605]benjamimgois[/MENTION] $10

[MENTION=1625453]talz13[/MENTION] $50

[MENTION=4383296]mikep2323[/MENTION] $25

[MENTION=4711859]buffalo_guy[/MENTION] $20

[MENTION=2196380]bokmob[/MENTION] $25

[MENTION=277409]redbaron[/MENTION] $20

[MENTION=6131626]JosephFeliciano013[/MENTION] $5

[MENTION=6068768]jwjessie488[/MENTION] $20

[MENTION=3432867]aelunyu[/MENTION] $25

[MENTION=1900625]MxCraft[/MENTION] $30
[MENTION=6196460]Googfan[/MENTION] $15

Total so far: Approx.€403/$503
[Galaxy Note 10.1 (2014 Edition) General] r4yN:
20$ from me (sry I'm a poor student :( )

We'll be doing this via PayPal, I assume?
[Galaxy Note 10.1 (2014 Edition) General] 22sl22:
$20 is perfect, any donations are helpful :)

Yes PayPal. If you look at his profile there's a link there. I'll add your name to the list :good:
[Galaxy Note 10.1 (2014 Edition) General] r4yN:
Alright, I've just donated 20€ (which equals ~25$ if I'm not mistaken). It would be great, if [MENTION=3463426]RaymanFX[/MENTION] confirmed the transaction (I've refered to XDA in the transaction note, but if you need the transaction ID, write me a PN) :)

PS: I know I said I'd donate 20$, but I figured since he's german, I could just as well donate 20€ instead :highfive:

And I also know that you usually don't donate until enough pledges have been made, but I have faith that we will make it. And if we don't, well, consider it a donation for the effort, lol :D

Edit: Transaction ID # 89F56830A9644882H
[Galaxy Note 10.1 (2014 Edition) General] sbattosai:
$365 on eBay (refurbished)

http://rover.ebay.com/rover/1/711-...1386122200?pt=US_Tablets&hash=item2a3b7493d8
[Galaxy Note 10.1 (2014 Edition) General] RaymanFX:
Hey, thanks a ton :)

I can cofirm the 20€ (!) donation is now on my PayPal account.
[Galaxy Note 10.1 (2014 Edition) General] r4yN:
thanks for confirming :)

Btw since you're german, THIS might be an interesting offer (although I'm not sure about the warranty)

265€ = ~330$ (free shipping within germany)
[Galaxy Note 10.1 (2014 Edition) General] benni_1994:
I'll donate 20€ at the end of the month! :)

You can add me on the list
[Galaxy Note 10.1 (2014 Edition) General] Pazzu510:
Is there anyway to donate directly from debit card? Paypal has problems with my card and renders the service unusable.
[Galaxy Note 10.1 (2014 Edition) General] 22sl22:
It depends. If you live in Germany it will obviously be easier. If not, it depends from country to country. What country are you in?
[Galaxy Note 10.1 (2014 Edition) General] GrimReaper1908:
Hi there,

nice to see that at least one person is not scared away by the exynos cpu :)

You can count me in for 15€

I have a question though:

How is this handled? Are we donating all at once when enough people have expressed their will to donate?

Or should I already donate so that you can be sure that I'm serious?
[Galaxy Note 10.1 (2014 Edition) General] 22sl22:
The donating is a personal thing. I worded things in the op to be safe. It's just easier if people pledge, say they are gonna donate, and then once the amount has been reached people can actually donate.

Say for example, there are no pledges and we raise 200 dollars that people have already donated in a few weeks and then people lose interest and not a lot of donations come in anymore. I don't want people to be angry if the dev doesn't end up getting the tablet. :good:

Better to pledge but if you want to donate right now that's fine. Either way i'll add you to the list
[Galaxy Note 10.1 (2014 Edition) General] davitox87:
Could you in the title add that this is for the exynos variant. It mislead me into thinking this was for the snapdragon until I read a little.
[Galaxy Note 10.1 (2014 Edition) General] emilycloud:
Ok I'm in for $20. Maybe a little more if we get close! Awesome guys.
[Galaxy Note 10.1 (2014 Edition) General] mrtoast:
In for $30 ?
[Galaxy Note 10.1 (2014 Edition) General] benjamimgois:
I just sent $10... hope that helps !
[Galaxy Note 10.1 (2014 Edition) General] talz13:
I'm in for $50
[Galaxy Note 10.1 (2014 Edition) General] RaymanFX:
Hey everyone,

just letting you know I was donated another 10€ yesterday, so we're at over 200$ now!

That's more than 2/3 of our goal, so there's only 100$ left.

Keep on going, we're almost there now.

Thanks to the community for having so much faith in me and enabling development for this device. :)
[Galaxy Note 10.1 (2014 Edition) General] 22sl22:
Yes, only 100 dollars left now, we are nearly there! This is going really well.

Do you have the name of the person who donated? I can add them to the list :good:
[Galaxy Note 10.1 (2014 Edition) General] mikep2323:
Ill throw in 25 dollars. Would you like me to donate now? If yes I can do when I get home.
[Galaxy Note 10.1 (2014 Edition) General] RaymanFX:
Hey, that was [MENTION=4174709]ollimi1[/MENTION] (post is here.)

As [MENTION=4653206]22sl22[/MENTION] explained earlier, pledging until the needed sum has been collected is the preferred method by many people.

However, some people donated already and I won't make a difference between either ways.

Thank you for your generous support :)

Only 75$ left! This is an incredible community.
[Galaxy Note 10.1 (2014 Edition) General] ollimi1:
Yeah! Thats fast!

Coming from work and wanted to see progress in financing your Note10.1, but now hits me the beat! :good::good:

A few people more and you can take this one from Ebay.de for 310€:

http://www.ebay.de/itm/Samsung-Gala...iPad_Tablets_PCs_eReaders&hash=item4d2798a8ec

Maybe you can get it for 290€. It's a 32gb, white P600, knox 0x0!!!
[Galaxy Note 10.1 (2014 Edition) General] henriavelabarbe:
I'm in for 25€.
[Galaxy Note 10.1 (2014 Edition) General] buffalo_guy:
donation

Just donated 20.00!
[Galaxy Note 10.1 (2014 Edition) General] bokmob:
Donation

Great to see this initiative.

I'll pledge $25... Finish line is close :D
[Galaxy Note 10.1 (2014 Edition) General] redbaron:
Donation

Just send 20$

Hope finish and new firmware in not far :)
[Galaxy Note 10.1 (2014 Edition) General] JosephFeliciano013:
I can pledge $5.00 at the moment.

This is awesome and the donating, pleading method is a great way to about it.