yashsingh1/xdaforums huggingface dataset:
[Sprint HTC One (M7)] D3luSi0n4L:
Hey, randomly- I can't really remember exactly when it happened but my capacitive keys no longer vibrate. Any where to check to ensure it's not a hardware problem? I'm not rooted or anything. I checked "Sounds" and "Vibrate on touch" is still checked. I toggled it a couple times and still nothing. Any and all help is greatly appreciated!
[Sprint HTC One (M7)] phat78boy:
Any chance your power save mode was on?
[Sprint HTC One (M7)] winsettr:
What is your battery level? At a certain point (20%?, 15%?) the phone goes into power save mode, with disabling vibrate among the settings.
[Sprint HTC One (M7)] youkosnake:
Probably this. Power save has an option for haptic feedback as well.
[Sprint HTC One (M7)] D3luSi0n4L:
Bingo! It's been on for two days lol thanks a bunch guys!
[MDA II, XDA II, 2060 General] Nickpes1805:
Good morning

I have a QTEK2020 ,with ROM 1.66.00WWE. I use on it a BTGPS receiver but I have the following problem. The moment my position is locked, the QTEK phone ability is disabled,as the GPRS connection also. I can't receive or make any calls. When I close my BTGPS connection,the phone still doesn't work and I have to do a soft reset.

What might the problem be?

Thank you in advance

Nikos
[MDA II, XDA II, 2060 General] edsub:
I would advice to upgrade to a 1.72 ROM version.

Most recent are the O2 based 1.72.18x & T-Mobile based 1.72.190

roms.

I use my own cooked (also published here) 1.72.903 ROM which is based on the T-Mobile 1.72.190 ROM plus 'some' extras.

This rom works flawlessly with Bluetooth GPS's
[MDA II, XDA II, 2060 General] Nickpes1805:
Thx,is there a link to the 1.72 ROM ? Which will fit better on QTEK2020?
[MDA II, XDA II, 2060 General] edsub:
Next time: PLZ use search.

I can personally recommend the 1.72.903 rom, but then: I am the creator of it.

You can find that rom via http://xdaforums.com/viewtopic.php?p=69940#69940

DO READ the instructions because you dont have a T-Mobile device.

If you, after flashing, dont like the pinkish T-Mobile Themes (and who does . . .), you can easily change back to the default theme (via settings/today) and reset the WM2003 dialer skin via a cab in the extended rom.
[Nexus 4 Q&A, Help & Troubleshooting] 309041291a:
Hey! I've recently switched to Franco but want to switch back to Trinity. One problem... Franco gives me deep, amazing colors that I cannot leave...

Is it possible to take the presets I have for Franco kernel and port them to match Trinity color settings so that it looks the same on Trinity...

Here are the settings

- RGB MULTIPLIERS

Red:230

Green: 225

Blue: 240

- GAMMA SETTINGS

Red/Green/Blue (all the same):

Greys(0), Mids (87), Blacks (119), Whites (0)

Misc Gamma Settings:

Contrast(6), Brightness(0), Saturation(87)
[Nexus 4 Q&A, Help & Troubleshooting] snak3ater:
Try 'Trickster mod' App
[Nexus 4 Q&A, Help & Troubleshooting] klvnhng:
I've been using fku colour control with trinity, works great.

Sent by carrier pigeon
[Nexus 4 Q&A, Help & Troubleshooting] 309041291a:
I found a way to or the colors but can you link Mr to fku
[Nexus 4 Q&A, Help & Troubleshooting] klvnhng:
https://play.google.com/store/apps/details?id=com.franco.kernel&hl=en

Sent by carrier pigeon
[Nexus 4 Q&A, Help & Troubleshooting] 309041291a:
Ahhh that's what you meant, I already own FKU and TKT :P, but the kernels use different methods to set gamma (kind of). Luckily Trinity and Franco have very similar color settings it was easy to bring over my current colors

Just to clarify I wasn't looking for an app to set this stuff. I wanted someone to port over the Franco colors I was using over to settings that would match for Trinity settings
[Nexus 4 Q&A, Help & Troubleshooting] klvnhng:
Oh, I see. Yeah, I don't think there would be a way to directly convert Franco values into trinity, you'd have to just experiment. But I do find that franco_my_profile (if I remember correctly) looks really good on Trinity too, even if it it doesn't look identical to what it does on Franco kernel.

Sent by carrier pigeon
[Verizon Samsung Galaxy Note II] DHO:
I just had a thought,...

I used PBJ 20130218_t0ltevzw_kernel. This is labeled as a 4.1.1 kernel

I compiled from 4.2.2 source, though the propriety binaries may still be 4.1.1

So, I would recommend having your favorite most recent kernel on your SD incase you want to flash it over the included one.
[Verizon Samsung Galaxy Note II] Clarkkent434:
I ran team vanir on my gnex. So glad to hear that you are coming to Note 2 family. Downloading now.

Sent from VZW Note 2
[Verizon Samsung Galaxy Note II] dmbfan13:
So I assume this is an AOSP ROM? Any different features than the other versions?
[Verizon Samsung Galaxy Note II] DHO:
Yes AOSP base, same features as all other Commotio/Vanir versions.
[Verizon Samsung Galaxy Note II] RemnantKing2:
Getting a failed when I try to flash the ROM
[Verizon Samsung Galaxy Note II] evolving:
Failed here to
[Verizon Samsung Galaxy Note II] DHO:
Ugh

Took link done

Can you elaborate on the error? is it in CWM?

edit,... i think it is just a CWM error, easy fix....
[Verizon Samsung Galaxy Note II] andrewjt19:
Awesome. I used this on the Gnexus and would def. Give it a shot here again. Can't wait:thumbup:
[Verizon Samsung Galaxy Note II] RemnantKing2:
TWRP 2.5.0.0

E: Error executing updater binary in zip ' /extern (cuts off after here)

Error flashing zip '/external_sdcard/B51-Commtio (Cuts off after here)

Hopefully that's enough.
[Verizon Samsung Galaxy Note II] DHO:
I think so working on it now.

For safety I label each install script with the board to prevent someone from trying to install a maguro ROM on a i605.

But the i605 uses several repos... i605 to t0ltecdma to smkd to smkd-qcom.

I think that I need to change the board to t0ltecdma or maybe just delete the check.
[Verizon Samsung Galaxy Note II] DHO:
Okay going to sleep, but 1 last attempt

http://www.emccann.net/dho/9-Experimental-physics-lab/
[Verizon Samsung Galaxy Note II] xlxfoxxlx:
Would love to try this its when ya get it giing
[Verizon Samsung Galaxy Note II] RemnantKing2:
Stuck at Samsung logo, it wont go any farther than that.
[Verizon Samsung Galaxy Note II] Psychotic Penguin:
Looking forward to dine Vanir totally dug it on my GNex. Happy to give it a go!

SPen'd from my Galaxy Note II
[Verizon Samsung Galaxy Note II] Chance77:
Tw kernels usually do not work with aosp...as far as i know..please correct me if wrong. I hear matrix is working well with aosp bases
[Verizon Samsung Galaxy Note II] JamesPumaEnjoi:
Awesome guys I ran Commotio on my GNexus now on my Note 2?!?!?! Say wha? Lol thank you guys for bringing this over to us!!!
[Verizon Samsung Galaxy Note II] DHO:
Cool thanks for the heads up. I will rebase and release a new version shortly
[Verizon Samsung Galaxy Note II] JamesPumaEnjoi:
Stuck at Samsung screen its probably just the kernel
[Verizon Samsung Galaxy Note II] ahjee:
There is one for the 15th but not the 16th
[Verizon Samsung Galaxy Note II] DHO:
I weill start a nightly script now,

Are there any lingering bug? I have not had a definite report in a couple days... hopefully everything has been exercised.
[Verizon Samsung Galaxy Note II] ahjee:
sorry I have strayed away for the last 3 nightlies. I haven't had time to play. I will try to flash the latest nightly when i get home and do some testing.

I would like to say however that Neak kernel is a great choice for a kernel to have baked in, either Neak or Devil as they both run very very smooth. I sound like a broken record but with the AOSP roms on our note 2 there has been graphical glitches since day one but with the two kernels i mentioned those glitches are at their most minimal if not gone completely
[Verizon Samsung Galaxy Note II] TheLoonyRebel:
7/17 build is up! I tried the 7/13 build. Very nice ROM. The only thing missing for me is MHL/HDMI but that's expected with AOSP based ROMs at this point. Will keep using this as my daily AOSP driver for sure. :D
[Verizon Samsung Galaxy Note II] TheLoonyRebel:
Going to double post here just to mention that the 7/17 build is VERY solid. If you are looking for an AOSP JB 4.2.2 ROM to try that's lightweight, fast, and efficient then try this one. You'll be very happy!
[Verizon Samsung Galaxy Note II] flyinj54:
Running 7-17. While turning torch on in the status bar toggles it kicks the light on and then back off. Only bug i can find. Great job and thanks for the support on this phone!
[Verizon Samsung Galaxy Note II] funnief13:
Hey Guys what Gapps are running on this?? IS IT THE LATEST ONE from Goo manager 4.2.2??
[Verizon Samsung Galaxy Note II] flyinj54:
Also the incall volume is unusable. I tried adjusting through device settings which doesn't seem to change the in-call volume at all. It's very very low. Just trying to help you at least know what the bugs are since it sounds like your building blindly without the device. Thanks again for the Rom!

---------- Post added at 12:23 PM ---------- Previous post was at 12:21 PM ----------

2013/03/01 gapps
[Verizon Samsung Galaxy Note II] asacado:
The only real problem I see is low volumes. I've tried multiple kernels and tweaks but it remains too low.
[Verizon Samsung Galaxy Note II] ahjee:
mmm...you could try Volume Booster or Volume+ from the Play Store if you haven't already...and I assume since you tried all kernels you tried the latest Plasma kernel and used Stweaks to adjust the volumes? the kernel recently added sound control in place of VooDoo.

DHO, I am about to flash the latest nightly, I will report back tomorrow
[Verizon Samsung Galaxy Note II] TheLoonyRebel:
7/19 build is up!
[Verizon Samsung Galaxy Note II] DHO:
Thanks could you elaborate on MHL/HDMI feature? Not sure what your referring to,..

Torch can be tricky on different devices, log pls?

I always rec my Gapps. On any of my servers

Volume. Hmm okay,... is it any better than the previous ones? I tried boosting the volume quiet a bit in hardware setttings, but I guess fell short. I will explore this some more.
[Verizon Samsung Galaxy Note II] DHO:
I think I found the issue

One of the repos I borrow from CM has the default max call audio set to 10. I believe this is out of 100, as all other values in the hardware are set x/100. Most values for this phone are set between 65 and 85. I put it at 75 for now, which is inline with the samsung value, with the default at 35 (may be low, but you can override, I want to be careful to prevent blowing out an ear drum :p )

I must warn you, be careful with the audio in today's nightly!!!! In addition, for best results, you will likely need to tweak the audio levels in advanced settings (I would rec trying first with the default kernel to ensure it is actually do something)

If this doesn't work, I am going to revert a bunch of CM related audio tweaks.

This nightly will be up in the mid-afternoon
[Verizon Samsung Galaxy Note II] DHO:
Nightly is up :)
[Verizon Samsung Galaxy Note II] asacado:
Looking forward to testing out this nightly. I got a new 64gb sandisk class 10 to upgrade from my 32 since I am nandroiding 3 different roms right now. Problem is, AOSP has yet to give birth to an exfat kernel, so chances are, your rom may have my 32 all to itself :P
[Verizon Samsung Galaxy Note II] TheLoonyRebel:
At this point it's an issue on 4.2.x ROMs period so it's not specific to this ROM. Anytime you try to use an MHL adapter or even the multimedia dock with HDMI on any 4.2.x ROMs the phone freezes up requiring an battery pull to reboot. Beyond that I'm clueless.
[Verizon Samsung Galaxy Note II] DHO:
Sounds like a binary issue,... maybe trying to mount to location that changed between 4.1.2 and 4.2.2,...
[Verizon Samsung Galaxy Note II] TheLoonyRebel:
That sounds like it could be the issue. No idea myself on how to fix it however on my own end here. :crying:
[Verizon Samsung Galaxy Note II] DHO:
Once volume is squared away, I will look into fixing,..

I bet if we can identify the proprietary lib (a logcat would help alot,..), can swap out that lib with a 4.2.2 samsung device (preferably using the same HW). Maybe the S4 or something else.

Any reports on the audio?
[Verizon Samsung Galaxy Note II] ahjee:
I been binging on flashing, I will download this latest nightly and report on audio. Last build I tried, I believe it was the 19th, I had kernel problems as usual and it seemed worse than it normally is. Dang thing wouldn't even boot most the time and it kept black screening. I would assume that flashing a kernel other then the baked in one would ruin the what you got going as far as audio changes, no?
[Verizon Samsung Galaxy Note II] DHO:
The audio issue was low, incall audio.

Flash away with another kernel if that makes it stable,... I have not done any major ROM updates. Maybe there was a kernel update.
[Verizon Samsung Galaxy Note II] ahjee:
So I booted up no problem at all this nightly, as usual the Rom is screaming fast and buttery smooth with zero graphic artifacts so far (the graphics thing is my biggest issue). I haven't tested all audio but usually the only place i notice it being to low is while on speaker phone...not even regular in-call just speaker and I can live with that.

I'll do some more testing and poking around to see if there is anything worth logging
[Verizon Samsung Galaxy Note II] ahjee:
So I just received my first call and I have no in-call audio out. I can hear them when I put them on speaker but if I don't then it's a no go. I'm going to adjust the in-call volumes and see if tinkering with them will help me out.
[Verizon Samsung Galaxy Note II] ahjee:
Even flashing a few different kernels wouldn't bring back the in call audio...once that is working again this will be my DD as this and Eclipse are the only AOSP roms that I don't have graphic artifacts on, great work here as usual DHO. I hope the next nightly works better for me. only the incall audio isn't audible unless on speaker but all is perfect titties other than that
[Verizon Samsung Galaxy Note II] DHO:
New nightly up with a bunch of reverts aimed at hopefully fixing the audio.
[Verizon Samsung Galaxy Note II] ahjee:
Props on your devotion and work either bruh bruh. You stay on this, like a cat slangin on the corner to get his jordans. Now I am torn, between you and Nitro I am always torn on who to stick with because you two are the only one's who seem to have squashed that graphic artifact problem that bothers me more than any other issue or bug or anything period...I will download and flash even though I just set up Eclipse! Damn you DHO! but...THANK YOU DHO lol. MY NICKA, BEASTIN iT
[Verizon Samsung Galaxy Note II] ahjee:
I am unhappy to say that once again I could not hear the folks on the other end, they could hear me but me no hear them haha. Like the last nightly I could hear them on speaker but that's it...and as usual other than that this rom is damn perfect, i love the stability and no graphic artifacts....I was actually content with the audio how it was before, the only one that seemed low to me was speaker phone
[Verizon Samsung Galaxy Note II] asacado:
Having followed every single build despite not like AOSP that much, Audio is still a minor issue. I will report I am testing it thouroughly with every kernel on the market in attempts to tweak the audio.

I'll report back with the 23rd's build and let you know my findings. Keep up the amazing work DHO, I want this to be my DD.
[Verizon Samsung Galaxy Note II] ahjee:
the 23rds build has no audio, none at all.

Flashed neak kernel and didn't help but Plasma and Devil bring audio back but in call audio still doesnt work
[Verizon Samsung Galaxy Note II] asacado:
The audio issue have been a problem since I can remember beta testing. I carry all kernels fully updated and test out any tweaks I can, but I can't make the phone calls volumes increase at all.
[Verizon Samsung Galaxy Note II] ahjee:
there is a 4.3 nightly up! DLing...even though i just finally went back to a TW rom and got it allll set up...damn, i love having awesome Devs who get awesome phones and share their awesome work

---------- Post added at 02:20 AM ---------- Previous post was at 01:47 AM ----------

Hey DHO, tried the latest nightly and upset to say that it would not install, kept failine g. I am going to retry then download....where are the Gapps we should use? anyone know of a set of working 4.3 gapps?
[Verizon Samsung Galaxy Note II] TheLoonyRebel:
4.3 version of gapps can be found here:

http://xdaforums.com/showthread.php?t=2378992
[Verizon Samsung Galaxy Note II] ahjee:
I am still getting a fail when flashing :crying:

---------- Post added at 02:30 AM ---------- Previous post was at 02:29 AM ----------

thanks brotha
[Verizon Samsung Galaxy Note II] TheLoonyRebel:
Fail error details:

Then it followed up with "error executing update binary" and "error flashing zip" messages that linked to where the ROM is stored on my micro SD card.
[Verizon Samsung Galaxy Note II] ztotherad:
did you try to take out the "assert failed" part? and i wonder if switching out the binary with the newly dropped cm10.2 binary. i haven't tried it yet, but i will try that later
[Verizon Samsung Galaxy Note II] ahjee:
Downloading the new nightly to test
[Verizon Samsung Galaxy Note II] TheLoonyRebel:
Still getting the same issue as the 8/1 build. I attached the recovery.log so maybe this could help figure out the issue.
[Verizon Samsung Galaxy Note II] TheLoonyRebel:
Any luck getting it to work for you?
[Verizon Samsung Galaxy Note II] ahjee:
about to flash in a few minutes, if it doesnt work i am gonna try and unzip it, replace the boot.img from the cm10.2 zip...or maybe just flash the cm first and then vanir over it, just to try it out for the hell of it
[Verizon Samsung Galaxy Note II] TheLoonyRebel:
Let me know if anything works for you. I just spent the past two hours doing just about every edit I can think of to both build.prop and updater-script with no luck. I did get one semi successful install after swapping the update-binary and updater-script from the CM10.2 build to the Vanir 8/2 build. It "failed" after nearly finishing install but I was able to boot up and get launcher and stuff working. I tried to then install the 4.3 Gapps I have but it would boot loop after getting to the start of the setup.

So I dunno.... there is something weird going on but I can't seem to figure it out.

Cutting to the chase on the recovery error info I posted a bit ago this is what the error message I'm getting says:
[Verizon Samsung Galaxy Note II] ahjee:
hmm, well i am sure DHO will get it sorted, he's probably a bit focused on a another device at the moment, I'm sure he cycles through all the devices and gives each dedicated time so once he gets back around to us being the primary focus again he'll get everything booting and running insanely smooth and solid.
[Verizon Samsung Galaxy Note II] ahjee:
okay, attempt 3 of trying vanir 4.3

fingers crossed fella's
[Verizon Samsung Galaxy Note II] Psychotic Penguin:
Didn't work for me
[Verizon Samsung Galaxy Note II] ahjee:
nah me either, i am wondering if DHO is even checking the thread haha, maybe he's just letting the builds go on their own and everything and he's just currently fixated on one particular device (don't mean this in a disrespectful manner either). I am sure things will be up and cooking soon enough
[Verizon Samsung Galaxy Note II] TheLoonyRebel:
Yeah it's the same issue from the past few days. Hopefully DHO will check in on this thread soon. I know this is repeating things but here's the info from recovery.log from the 8/3 build - same info but worth repeating.
[Verizon Samsung Galaxy Note II] ahjee:
yeah i get the same
[Verizon Samsung Galaxy Note II] TheLoonyRebel:
I normally don't do stuff like this but I sent an PM to DHO in hopes of getting his attention on the install fail issue(s). This looks to be an updater-binary issue which sadly I have no idea on how to fix at all. I've tried everything from using the updater-binary from the CM 10.2 build, changing things around in build.prop and update-script, etc etc etc. Hopefully DHO can figure out what's going on and can get this fixed.
[Verizon Samsung Galaxy Note II] TheLoonyRebel:
8/5 build up. Same issue as before.
[Verizon Samsung Galaxy Note II] asacado:
Yup, cannot do much without a working rom to test bugs. But a failed load is a bug in its own since Vanir transitioned to 4.3. Hopefully this slight OS upgrade is worth all the trouble since 4.2.2 was just starting to look fully stable IE working bluetooth, mms/gps/camera/keyboard/clock not FC'ing to death and requiring thirdparty apps to bandaid the effect. Will continue to monitor thread in hopes to upgrade from 4.1.2.
[Verizon Samsung Galaxy Note II] Naddict:
Thread cleaned, keep the drama out of development.

If users cannot get along, there is a neat feature, click on user name, click on "add to ignore list" - then, you are not tempted to be disrespectful at all, because, if you are disrespectful, you get infracted by XDA staff for violating XDA posting rules.

Lets contribute to development, if you can't do that, log off and go elsewhere for drama.
[Verizon Samsung Galaxy Note II] TheLoonyRebel:
8/7/13 build with install issue fixed (2nd build now up).

http://d-h.st/a1A

From the bit I had this running there are still some issues going on. Media mounting doesn't work at this point. While wifi does work mobile data aka Verizon does not. Other expected stuff from 4.3 isn't working either like Bluetooth calling and the like. But here ya go folks.

Double posting here but the issue ended up being i605 got referenced several times in both the build.prop and update-binary where it was expecting t0ltecdma instead. Took me I dunno how many hours to figure that little bit of info out but that's what happens when you are learning stuff, right? Sometimes obvious things don't jump out at you right away.

Final Edit: I'll try to look into the mounting issues tomorrow at the earliest. No idea if I can fix them but I'll give it a shot. Dead tired however. Need some sleep.
[Verizon Samsung Galaxy Note II] veloct:
Looking forward to trying out Vanir 4.3

Sent from my VZW Note II from xda premium
[Verizon Samsung Galaxy Note II] ahjee:
could you upload your build prop and update binary so we could use them to make it well again
[Verizon Samsung Galaxy Note II] TheLoonyRebel:
If you take the build.prop and update-script from the fixed build I uploaded and place them in the new build it'll give you the same fix. Don't extract the zip just simply use a program like WinRAR to replace the files in the zip itself.
[Verizon Samsung Galaxy Note II] ahjee:
thanks bruh bruh
[Verizon Samsung Galaxy Note II] TheLoonyRebel:
By the way it looks like the mounting issue with micro SD is kernel related. I'll get a catlog up in a little bit using the stock kernel from 8/7 as I'm testing the 8/7 fixed build of mine but with the CM10.2 8/8 build's kernel which works with my micro SD card.
[Verizon Samsung Galaxy Note II] DHO:
Thanks guys for all the support

Sorry I have been in hiding, just working on the ROMs since 4.3 dropped. We are finally getting most devices stable and fixing the i605 is high priority.

I am reading over the last few pages and working on a nightly as we speak. I need to correct the prop issue. I am not sure where that taint was introduced, but will be fixed today.

As always logs are the best way to get things fixed.

Thanks guys and I'm back on this forum
[Verizon Samsung Galaxy Note II] TheLoonyRebel:
Hey DHO,

First of all welcome back.

If you look at the build.prop and update-script in the fixed version for the 8/7 build I have already gotten the install issue resolved. The current issue with mounting/using the micro SD card however is beyond me on how to fix at kernel level. I tried the 8/7 build with the CM 10.2 kernel which got the micro SD to work so I'm assuming it has to do with perhaps how its routed at kernel level? Also mobile data does not work.

Any other issues like Bluetooth are also on CM 10.2 right now.

Let me know what I can to do help test things on the upcoming build.