yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] cobyman7035:
How bouut engadget app?

Via Google voice Δ |\|€×u$™ 7 FHD on Tapatalk²
[Nexus 4 Original Android Development] Andre_Vitto:
What I meant by govornor settings is the three settings under ondemand govornor.. sampling_down_factor, sampling _rate and up_threshold..

I guess sampling down factor is how fast the freq scales down as ondemand will up to the max when there is any load (Read that from the govornors explained thread in xda)... but still I dont understand the what 4 means in its value.. also the other two things..

and regarding the app lag.. zzzz... burrr.. Misunderstood.. Read before this line..
[Nexus 4 Original Android Development] zephiK:
XDA app is actually based off Tapatalk and has been updated to be based off of Tapatalk 4. I personally don't have any lag using Tapatalk 4, I bought it during its promotional period of $1.
[Nexus 4 Original Android Development] spider623:
Don't know if any one reported this but the app downloads the JSS kernel for Paranoid Android, PA uses JWR kernels
[Nexus 4 Original Android Development] Geordie Boyo:
Where is the download link for the r185 release please?
[Nexus 4 Original Android Development] Andre_Vitto:
Hurr-Durr

http://xdaforums.com/showthread.php?p=45930268
[Nexus 4 Original Android Development] hooliganx:
thanks man.

thread is really big, and search for "test" or something like this doesn't help. ;)

maybe one host with test versions is more simple.

N4*Slim.b.1.2.JSS.4.3*SlimKernel.JWR.RC.1.3*TWRP.2.6*Radio.0.84
[Nexus 4 Original Android Development] santeana:
I used to love the xda app but then I stopped using it when I realised that a lot of posts don't even show up! That is to say, they seem to be truncated. If you look at the OP you'll notice it's considerably longer using Tapatalk 4 than it is if using the xda app. (which is essentially a custom version of Tapatalk anyway lol).
[Nexus 4 Original Android Development] alanwyl:
I was using the old xda free app and now the paid tapatalk4. Maybe I was comparing the old thing. Haven't tried the new xda app.
[Nexus 4 Original Android Development] Andre_Vitto:
My question was totally related to kernel gov settings and cores not showing online.. Not which forum app is better (or worse).. if you have any insight on the ondemand gov settings or issue with cores online on touch please be so kind as to share..
[Nexus 4 Original Android Development] santeana:
Your question was about lag in xda app. And you were told several different ways that that app lags. Period. Change your governor to performance and hotplug high load threshold to 10. That's about the best you're going to get out of your phone but it will still lag on xda.
[Nexus 4 Original Android Development] Andre_Vitto:
Lol.. You know more about the question I want to ask than i do? Please do not reply to me and clutter the thread with unnecessary debate..

If anybody know more about the three settings of ondemand gov in gov control.. Please do share..

Also when I select cores online on touch to 4, the system monitor in FKU does now show cores 3 and 4 online.. Anybody can throw some light on this?
[Nexus 4 Original Android Development] alanwyl:
Try performance, see if it works for you, if it doesnt work, use a browser. Not any settings in governor can help you.

---------- Post added at 08:15 PM ---------- Previous post was at 08:14 PM ----------

Four cores online doesn't mean anything. Tapatalk may not use all four cores.
[Nexus 4 Original Android Development] :
Your original question, you were asking of a way to reduce lag in the XDA app by changing governor settings. Just create a per-app power mode for XDA app and put high load threshold at 0, four cores will be online and it should eliminate the majority of lag you're experiencing. I'd suggest you also use Interactive governor it is tweaked to perfection, can't go wrong with it
[Nexus 4 Original Android Development] occtec:
Any reason display control does not hold settings after reboot? I'm on psx v7.1
[Nexus 4 Original Android Development] GForceXIII:
The app's performance is crappy.

I don't think even using performance governor will help with the lag.

Have you tried turning the screen off then on after the reboot?
[Nexus 4 Original Android Development] Bobtehblob:
Franco, input boost freq resets on boot for both my nexus 4 and 7 (2013). Cpu settings and governor control are both set on boot from within the app.

Sent from my Nexus 4
[Nexus 4 Original Android Development] arlenwoot:
Doesn't reset for me. Try clearing app data.
[Nexus 4 Original Android Development] Bobtehblob:
Hmmm, that's odd. I thought that might be the issue so I cleared app data on both and it still resets it self... strange.

Sent from my Nexus 4
[Nexus 4 Original Android Development] zephiK:
I never had any lag problems on my Nexus 4 in general with tapatalk. Not currently on Franco right now but never experienced any lag either.

I do have force 2d on gpu under development settings if that changes anything at all. Worth giving it a try to see if makes a difference at all?
[Nexus 4 Original Android Development] dmourao:
Had another random reboot today.

I'm using r184 jwr on Slim Bean, but the rr also happened on Cataclysm.

last_kmsg is attached. :good:
[Nexus 4 Original Android Development] Bill Gamble:
"hw_reset"... Not much he can do about that.
[Nexus 4 Original Android Development] giovaorama:
Try to save a default per app setting.

In my case it didn't keep the interactive governor until i made this.

Inviato dal mio Nexus 4 con Tapatalk 4
[Nexus 4 Original Android Development] Andre_Vitto:
okey.. I am sorry.. i somehow confused you all.. what I want to know is

Someone please explain me the meaning of these values..

sampling_down_factor

sampling _rate

up_threshold..

Thanks a lot in advance..
[Nexus 4 Original Android Development] Bobtehblob:
I don't personally use per-app power modes but making a default one still doesn't completely fix the problem. It's only being set once the default power mode kicks in. Disabling per-app power modes causes it to default upon boot again. So still not on boot unfortunately :( I know Franco is redesigning the whole app, with the way set on boot is handle being one of they key changes. So it doesn't really matter for the time being!

Sent from my Nexus 4
[Nexus 4 Original Android Development] ashishv:
http://xdaforums.com/showpost.php?p=19846297&postcount=2
[Nexus 4 Original Android Development] jamel_tza:
Try flashing SuperSU. When I was using ROMs that had the built-in superuser FKU wasn't playing so nice. Since I've been using SuperSU I haven't had any problems. Make sure you update the binaries when you do flash it.
[Nexus 4 Original Android Development] gpvecchi:
Unluckily, no. I still have both apps and no root... May someone help, please, or is this too OT?

Thanks!
[Nexus 4 Original Android Development] Savant:
I would reflash your ROM and start clean because it sounds like something is borked in your install.
[Nexus 4 Original Android Development] drawde40599:
Your on cm right? did you install it like I explain to you when you're asking yesterday? And do u have root access set to apps and adb in dev options?
[Nexus 4 Original Android Development] occtec:
Yes I have?

---------- Post added at 07:24 AM ---------- Previous post was at 07:10 AM ----------

I am currently on PSX ROM using this kernel and have flashed super su v1.65 using display control. When I load a custom profile all is good after screen of then on again, colors are applied BUT the minute I reboot I lose the profile even after screen of and on again. I do see display control been granted super su permission but still does not apply the custom color profile I had chosen :(

---------- Post added at 07:25 AM ---------- Previous post was at 07:24 AM ----------

I am currently on PSX ROM using this kernel and have flashed super su v1.65 using display control. When I load a custom profile all is good after screen of then on again, colors are applied BUT the minute I reboot I lose the profile even after screen of and on again. I do see display control been granted super su permission but still does not apply the custom color profile I had chosen :(
[Nexus 4 Original Android Development] zorginho:
Is normal that with ondemand on flu in governor control all the values are empty?

Inviato dal mio Nexus 4 usando Tapatalk 4
[Nexus 4 Original Android Development] franciscofranco:
Sorry for being MIA, been working hard on r185 and FKU. r185 is still not finished. I didn't read the last 10 pages, sorry, no time.
[Nexus 4 Original Android Development] Luigiesin:
Take your time brother... So far your last build is pretty solid!
[Nexus 4 Original Android Development] mohitgalaxy3:
Franco was on stock kernel, flashed r184 today and got 2 reboots while playing game.

Tell me what is the path to get the logcat, I will attach it.
[Nexus 4 Original Android Development] franciscofranco:
Current status of double tap to wake:

- Functionality is close to perfect - double taps need to be done within 1 second after the first touch or it will be reset (previous: 2 seconds)

- The second touch needs to be in a 100px range of the first touch. If the x axis and/or the y axis is 100px off the first reported touch double tap resets

- Works perfectly if the device is not deep sleeping

Current problem

- When the phone starts the process of entering deep sleep the Kernel has a functionality to suspend the registered devices, in this case this device goes through the i2c driver. i2c is a Kernel driver where low speed hardware devices go through. Anyway, when the Kernel goes through that suspend path the touchscreen ultimately goes to suspend. The touchscreen itself is powered on but going into suspend the Kernel tries to disable the hardware interrupts (IRQ) and I'm relying on a IRQ to send a message to the touchscreen with the touch inputs. So unless I find a reliable way to stop this touchscreen device to go into deep Kernel suspend I don't know what else I could do besides relying on a Kernel wakelock and I don't want to do that. So if anyone as a remote idea of what I'm talking about and have any idea how to remove a device (in device I mean the touchscreen device only) from the suspend path let me know, I'm all ears.
[Nexus 4 Original Android Development] franciscofranco:
/proc/kmsg... first post.
[Nexus 4 Original Android Development] franciscofranco:
Hey guys I was just reading the datasheet for the speaker amp and I realized stock Kernel already gives out a sysfs path for increasing the gain output of the amp. There are other registers available that are not exposed to sysfs (thats what faux speaker amp thingy does, just exposes the sysfs registers), but after reading the datasheet I'm not sure they are any valuable for user experience. I can expose them anyway if I get enough people wanting me to. The datasheet is here: http://elcodis.com/parts/5883249/TPA2028D1.html#datasheet - TI's open hardware documentation is fabulous, I had a good fun reading all of it.

Default is 12 and max is 30.

echo X > /sys/devices/i2c-0/0-0058/fixed_gain

Using 30 might distort the sound a little bit on higher volume, so if you want to enable some compression you can do it like this for a 2:1 compression ratio:

echo 1 > /sys/devices/i2c-0/0-0058/comp_rate

4:1 compression ratio

echo 2 > /sys/devices/i2c-0/0-0058/comp_rate

8:1 compression ration

echo 3 > /sys/devices/i2c-0/0-0058/comp_rate
[Nexus 4 Original Android Development] Mercado_Negro:
Do you have any info about attack and release times of this compression or are they material dependant? If they behave like opto devices or have a feedback signal path then it's probably better to set up the ratio before adding gain through the amp (unless this app is at the output stage).
[Nexus 4 Original Android Development] franciscofranco:
ATK_time These bits set the attack time for the AGC function. The attack time is the minimum time

between gain decreases.

REL_time These bits set the release time for the AGC function. The release time is the minimum time

between gain increases.

http://datasheet.elcodis.com/pdf2/79/40/794029/tpa2028d1.pdf
[Nexus 4 Original Android Development] :
With this new touck wake development, the Touch Control is going to lose appeal.. and its developer. :D

Sent from my Nexus 4
[Nexus 4 Original Android Development] Mercado_Negro:
Thanks for the datasheet, it's pretty interesting.

In this case, the attack time should be something around 30ms or above. And the release time above 500ms. For complex material like mastered songs with high loudness levels they shouldn't go below these values to avoid more distortion. The THD is pretty high on this as far as I can see which makes things worse. Appling compression before adding gain would counteract this, in theory (and according to the signal flow diagram).

Can you expose these values as well?
[Nexus 4 Original Android Development] ben_pyett:
although possibly not while it takes out a kernel wake lock? Do we know how the alternative touch to wake approach do it and does it hold a wake lock?
[Nexus 4 Original Android Development] drawde40599:
Yes please do, faux's app works great with your kernel been using it since it came out with no issues, there really isn't any distortion at highest level phone handles it just fine, i own a automotive shop so its loud all day long the higher volume makes big difference, and to have it built into your app would be nice
[Nexus 4 Original Android Development] franciscofranco:
Sure guys! I'm a complete ignorant on these settings, so don't ask me whats better or worse, although the datasheet says everything that there is to know.

There is no touch to wake alternative. I've been working on a double tap to wake for a week and so far I don't use any wakelock to make this happen. Read my post a few posts back.
[Nexus 4 Original Android Development] leandronb:
Hey guys, I flashed the latest nightly of Franco today but I want to know if my battery life is normal or not. Also my CPU temperature is above normal. I was just using feedly and chrome and CPU was at 58 Celsius. And chrome is using more battery than screen itself. Is it normal?

And look at CPU frequency, 46 minutes in 1.5ghz looks not normal. I am at stock jwr66y.

Enviado de meu Nexus 4 usando Tapatalk 4
[Nexus 4 Original Android Development] Mercado_Negro:
I was suggesting some default values if you plan to add this to FKU :)
[Nexus 4 Original Android Development] :
I observed that after flashing, the first battery cycle is kinda like this. You may erase battery stats, then restart the device. This fixes my problem all the time.

Sent from my Nexus 4
[Nexus 4 Original Android Development] prembox:
AFAIK since 4.2.1, Battery Stats are erased by default when the device is rebooted....
[Nexus 4 Original Android Development] Andre_Vitto:
Guys...

How do I reset my voltage setting in FKU to default after I have messed up with it.
[Nexus 4 Original Android Development] arlenwoot:
They are not erased when the device is rebooted, but they are whenever the battery is above 90% and unplugged from the charger.

https://plus.google.com/u/0/105051985738280261832/posts/FV3LVtdVxPT

---------- Post added at 01:40 AM ---------- Previous post was at 01:38 AM ----------

Reset app data, or put 384MHz back to 850mV and everything will be back to default values.
[Nexus 4 Original Android Development] franciscofranco:
Uncheck set voltages on boot and reboot...
[Nexus 4 Original Android Development] HamsterHam:
How do I set the recommended colour settings on boot?
[Nexus 4 Original Android Development] prembox:
Yeah...you are actually right....I meant to say the same but wrote something else altogether....thanks mate!
[Nexus 4 Original Android Development] ben_pyett:
sorry, had read your post, and what I meant was how does the sweep to wake module approach work that everyone has been asking about in this thread for the last few months.
[Nexus 4 Original Android Development] arlenwoot:
Had a random reboot today using the latest touch to wake test kernel but with touch disabled at the moment.

Here's the last_kmsg http://pastebin.com/fbQaCuML
[Nexus 4 Original Android Development] sordna:
Does this mean that you may need more than 2 taps to wake the phone? Or that the phone doesn't respond to taps at all ?

I'm running the latest test kenel, and can always wake the phone by tapping it, even after an entire night of the phone sleeping (and without connected to a charger) although it might need 3-4 taps in that case, which is not a serious problem.
[Nexus 4 Original Android Development] jmudrick:
Not normal. I'm consistently in the 2-3% range on 1.5GHz. Wipe app data and flash again. If you're using Chrome beta switch.
[Nexus 4 Original Android Development] gpvecchi:
Yes, it seems that Superuser can't be removed as part of CM framework...
[Nexus 4 Original Android Development] mohitgalaxy3:
I cannot open that file, it's corrupted.
[Nexus 4 Original Android Development] bar-aka:
Hey, I had the same problem with SlimRom/FK. 1-2 reboots a day and last_kmsg also had hw_reset.

I tried it on Slimrom build 1 (stable) and on build 1.2 (weekly). I was just about to give up and go back to CM, but then the 1.4 weekly came out and after flashing it, I haven't had a reboot in the last 51 hours.

So if you haven't tried it on the 1.4 weekly, I suggest you do. If it still reboots, then I'm afraid there's no clear solution. :(

EDIT: GOD DAMN IT! what a way to jinx it. 10 minutes after posting this, I had a reboot :)
[Nexus 4 Original Android Development] myfluxi:
Told you so, I completely gave up on the double tap feature months ago because hammering the screen until it finally decides to wake up is useless :) I'm afraid this is a dead end.

I you want to improve something over Showp's implementation, you want to look into a proper internal reset function. Presently you can reliably reset the device by writing "soft" to the sysfs /reset node. I didn't get it to work directly from the kernel, the whole ts code is so hacky and racy.
[Nexus 4 Original Android Development] TheDarkDefender:
Use this app to pull the last kernel log

https://play.google.com/store/apps/details?id=com.tortel.syslog

This is what i use and it's good

Sent from my Nexus 4
[Nexus 4 Original Android Development] mohitgalaxy3:
So i am attaching the last log https://db.tt/ysy1TaA5
[Nexus 4 Original Android Development] kenkiller:
How did you make the faux speaker app work with Franco's kernel? All the advanced features are disabled.
[Nexus 4 Original Android Development] jmudrick:
Reborn90's modified Franco+ kernel is Faux Sound compatible.
[Nexus 4 Original Android Development] Shardzmi:
Who is showp and where can we test his implementation of touch to wake for mako (if he did it for mako)?
[Nexus 4 Original Android Development] spupuz:
sorry for newbie question, which are best setting for battery saving maybe using undervolt to have better battery consumption?
[Nexus 4 Original Android Development] fozzie:
The default settings are best.

Under-volting might help reduce heat but it won't improve your battery consumption.

---------- Post added at 12:52 PM ---------- Previous post was at 12:51 PM ----------

Just copy it to your sdcard using any root capable file explorer.
[Nexus 4 Original Android Development] spupuz:
ok and which are your suggestion?

what about governor and scheduler for best battery saving?
[Nexus 4 Original Android Development] drawde40599:
Not advanced

---------- Post added at 04:26 AM ---------- Previous post was at 04:25 AM ----------

I no, U don't need to remove it, guess i don't no what your trying to do, good luck

---------- Post added at 04:27 AM ---------- Previous post was at 04:26 AM ----------

I no, U don't need to remove it, guess i don't no what your trying to do, good luck
[Nexus 4 Original Android Development] kenkiller:
Thanks but no thanks....

Sent from my Nexus 4

---------- Post added at 08:39 PM ---------- Previous post was at 08:39 PM ----------

I see. Oh well....

Sent from my Nexus 4
[Nexus 4 Original Android Development] drawde40599:
Ya, i just like that i can double the volume i run it at 27 in the shop, stock is 12. Don't no y google made volume so low, what's nice about it is u dont have to flash hokey hacks that mess with framework and install forced apps ;)
[Nexus 4 Original Android Development] kenkiller:
Here's looking forward to Franco doing his own FauxSpeaker thingy..... with advanced features as well if possible. :D While it might irk faux, but having to choose between kernels just because of such features is irritating for end users like me - many times I asked myself, should I abandon FKU for fauxclock? :D
[Nexus 4 Original Android Development] myfluxi:
The double tap algorithm is easy. It's about the low level driver issues.

I saw that CM abandoned the feature for the HTC One device. Most of it was based on https://github.com/showp1984.

[MENTION=470754]Franco[/MENTION]: Maybe an investigation in the gpio pins will help. Instead of pulling the pin down during suspend it had to stay in it's previous state.
[Nexus 4 Original Android Development] ImperatorShade:
Guys, what settings for great battery and good performance?
[Nexus 4 Original Android Development] Andre_Vitto:
Ha ha ha.. That's the secret...
[Nexus 4 Original Android Development] sordna:
I'm actually very happy with what Francisco has done in the test kernels, been using the tap feature from the first day, and only 2 or 3 times (out of hundreds) I had to actually push the power button.
[Nexus 4 Original Android Development] farris:
My first reboot since I have my N4, the telephone freezes and it reboots.

Link to kmsg: https://dl.dropboxusercontent.com/u/11020819/kmsg.txt
[Nexus 4 Original Android Development] franciscofranco:
Its pretty simple. When we touch the display it sends a hardware IRQ, but we're going through suspend like every 5 seconds. Yes Mako has a problem since the beginning that it goes through the resume-suspend path every 5 seconds because of the HSIC modem. So instead of staying in deep sleep forever until woken up, either by an IRQ or by user request it just loops there forever. You can power up adb and do cat /proc/kmsg after the device has been down a while and you can see the eternal loop. So since we're going through suspend all the time when we send a touch IRQ it generates a pending IRQ wakeup event that won't cancel the suspend routine until we spam it by touching numerous times. If we, by luck, double tap while the device finished the suspend routine (which can happen like 20 times a minute) if will wakeup. Its a huge clusterfúck.

Yes, its all about the low level driver issues of Mako. I've thought about the gpio pins thingy, but before going that I tried a bunch of things. I tried a pm_wakeup_event, no dice. Tried resuming the irqs before doing anything else, no dice. Tried to force the suspend->wake path, no dice. I didn't know showp did something like this, but I imagine it also has its own irks. My double tap x, y touches detection works just great, its only the problem of the i2c driver being suspended, and then it cannot generate IRQ wakeups to abort the suspend routine (when the device is going through the deep sleep path) and wake the device up. I even tried to forcefully NOT suspend the IRQ in the IRQ driver, but also no dice.

What is strange is that in the latest Kernel preview I can 95% reliably wakeup the device with 2 taps, but when I started to calculate the x, y deltas directly from the ts driver data it stopped working reliably during deep sleep.

Hey there is no such thing as me doing the faux speaker thingy. I'm just going to expose the hardware registers to sysfs because on stock they did not expose them. There is no magic in this. faux did the same, he probably read the datasheet, realized not all registers are exposed and he just did that. Its no magic, no coding skills, no nothing, just exposing **** that's already there for the taken. I'll do that because users asked and I'm not going to release any third party app to control it.
[Nexus 4 Original Android Development] thebryceee:
Lolololo
[Nexus 4 Original Android Development] leets4uc3:
Says watchdog reset so from my understanding something got messed up and it rebooted in safety for the device. Not a kernel problem.