Database Users

Possible bug with smartassV2 and Semaphore kernel 1.9.0

Hello everyone, it turns out that took a few days testing the module in different roms listilloV2 and talondev kernels 5.2.5 and semaphore bigmem bigmem also 1.9.0. Anyway, I've noticed these last few days especially with the kernel semaphore when it is off screen not receive calls as if in deep sleep and not wake up because when I burn to the screen to get the typical message that a number has called me. Also if I try to display on call from another number if it works perfect. Trying another module as ondemand works seamlessly with screen off. Anyone else happened?

Hello again, well just wanted to say that apparently I have been testing the module and is not smartass v2, but the thunderbolt script I had. I have changed to the latest version and so far I have not had any problem receiving calls.

Sorry, but another problem arises I am intentanto googlemaps update from the market and will not let me, reads "The package file is not signed correctly." I've downloaded from a link, I tried to install and tells me that the application is not installed. Any solution? Thank you.

I think its a Market issue. Try again later. A few other people also experienced this.

ok, thanks I'll prove it.

Well continue with my research in particular. I thought it was fixed the issue I receive calls but no, because even if you upgrade to the latest version of thunderbolt is the kernel semaphore v2 smartass had it in September but was still in ondemand CPU with what was normal to receive calls, but if you switched to v2 smartass anymore. At the end change the kernel to Talondev 2.5 and 0.5 .. still doing the same smartass v2. Already that the solution is not to use this governor but was very fluid mobile behavior. Have proven to with OndemandX and InteractiveX and to come I have to put them fluids voltages not so aggressive. Which of the two recomendais? My voltages are:
1000 ---- 50
800 ------ 75
400 ---- 100
200 ---- 125
100 ---- 150
and interactiveX ondemandX or simply have removed 25 at each frequency:
1000 ---- 25
800 ---- 50
400 ----- 75
200 ----- 100
100 ----- 125
Another thing about the market. I think that ultimately goes wrong? I do not let me install the latest version of Googlemaps 6.0, and that that changing the kernel thought that maybe was solved. Today I said I have another update Spy CPU and when I upgrade just to let me open it or uninstall or because there acutalizacion. .... Not that rare.

Another thing, for more information, I have the rom Innovation V14 F1, and so far had not had any problems.

snapx said:
Well continue with my research in particular. I thought it was fixed the issue I receive calls but no, because even if you upgrade to the latest version of thunderbolt is the kernel semaphore v2 smartass had it in September but was still in ondemand CPU with what was normal to receive calls, but if you switched to v2 smartass anymore. At the end change the kernel to Talondev 2.5 and 0.5 .. still doing the same smartass v2. Already that the solution is not to use this governor but was very fluid mobile behavior. Have proven to with OndemandX and InteractiveX and to come I have to put them fluids voltages not so aggressive. Which of the two recomendais? My voltages are:
1000 ---- 50
800 ------ 75
400 ---- 100
200 ---- 125
100 ---- 150
and interactiveX ondemandX or simply have removed 25 at each frequency:
1000 ---- 25
800 ---- 50
400 ----- 75
200 ----- 100
100 ----- 125
Another thing about the market. I think that ultimately goes wrong? I do not let me install the latest version of Googlemaps 6.0, and that that changing the kernel thought that maybe was solved. Today I said I have another update Spy CPU and when I upgrade just to let me open it or uninstall or because there acutalizacion. .... Not that rare.
Click to expand...
Click to collapse
Don't understand your English. Sorry
snapx said:
Another thing, for more information, I have the rom Innovation V14 F1, and so far had not had any problems.
Click to expand...
Click to collapse
F1 includes ThunderBolt!

Sorry for my English, but I use google translator. Well because I think this solved everything. In reviewing the system folder / etc / ini.d faltavan me and S98screenstate_scaling S98system_tweak files. Perhaps without realizing it clear it but everything works normally. Rom that already incorporates thunderbol Innovation F1 but I wanted to update it if it were a problem. So far it seems that everything is resolved. Thanks anyway for everything.

delay between Ringtone and Screen

Hi All,
I have a weird issue.
When someone is calling me, there is a delay (several seconds) between the ringtone sound and the number appearing on the screen.
Its occur especially after at least 5 minutes of not operating the phone.
Any help?

Yeah me too facing same issue. it takes 1-2 secs to wake up while ringing.

are you using Abyss kernel and under clock CPU to minimum 100mhz ?
I had this problem with Abyss Kernel and set minimum speed of CPU to 100mhz.
using CF-Root kernel now, this problem is gone.
could be 100mhz wake up latency.

Does it work with Rocket v20?

wireless.tech.expert said:
Does it work with Rocket v20?
Click to expand...
Click to collapse
not sure, you can consult with the peeps in the Rocketrom thread, sure they can help you .

Currently on darky rom. not seeing this

[Q] [KERNEL] KT-SGS4 - MJ7 - KTweaker (too much BUS&L2 OC)

Hi,
first of all, gratulations to ktoonsez for his fine work.
Unfortunately I think I found a showstopper: If I start the Zombie Demo (or the jungle Demo) from MOBILEGPU MARK from play . google .com/store/apps/details?id=jp.co.siliconstudio.MOBILEGPUMARK i get almost instandly an app crash. (with default CPU/GPU Speed and Voltages. e.g. Dead Trigger 2 runs on my device for hours with 1890MHz/-100mV and 600MHz GPU/-75mV) Only if I reduce the maximum frequency to 1782MHz, the MOBILEGPU MARK demos run without problems. So I came to the conclusion that BUS/L2 overclock may be the reason for the crashes.
I'ld be glad if anyone would help to investigate the case. Thanks in advance...

*push*
(problem still remains, with latest KT-SGS4 Kernel)

buggynotme said:
Hi,
first of all, gratulations to ktoonsez for his fine work.
Unfortunately I think I found a showstopper: If I start the Zombie Demo (or the jungle Demo) from MOBILEGPU MARK from play . google .com/store/apps/details?id=jp.co.siliconstudio.MOBILEGPUMARK i get almost instandly an app crash. (with default CPU/GPU Speed and Voltages. e.g. Dead Trigger 2 runs on my device for hours with 1890MHz/-100mV and 600MHz GPU/-75mV) Only if I reduce the maximum frequency to 1782MHz, the MOBILEGPU MARK demos run without problems. So I came to the conclusion that BUS/L2 overclock may be the reason for the crashes.
I'ld be glad if anyone would help to investigate the case. Thanks in advance...
Click to expand...
Click to collapse
Sorry for the delay. Have you looked into this thread for better assistance? Would gladly help you out here but figured I refer you there since we already have a thread for such discusion on the kernel. There's a great group of people there more than willing to help.
http://forum.xda-developers.com/showthread.php?t=2393708

[GUIDE] No Audio Glitches on CM12 based roms by fosseperme

And after correcting the bug audio of Nexus 5 and lags software of LG G3, I return this time with a bugfix against glitches and metallic sounds on music players in CM 12 roms.
The team cyano did a bad job on the kernel of CM12, since it was discovered that the cause of the glitchs was the non use of hotplugg with two cores always active in standby. Even Franco with his kernel solved the problem with the latest release r37, but the kernel has bad performance compared to stock kernel.
With this short guide you can activate the two cores for ever, to eliminate audio glitches on CM12 base roms!
1) Download from playstore the app called "CPU Performance Control Free" of mugich (requires root).
2) Open the app and in profiles select "add new profile" that provides:
Core 0 in "Core always enabled" (Min 300 Max 2457 MHz) and set it as Interactive
Core 1 in "Dynamic core hotplug" (Min 300 Max 2457 MHz)
Core 2 in "Dynamic core hotplug" (Min 300 Max 2457 MHz)
Core 3 in "Core always enabled" (Min 300 Max 2457 MHz) and set it as Conservative (because you can t change this value)
Now save your rule with a name, and after re edit the saved profile and change Core 3 from Conservative to Interactive (now you can change the value, it s a bug of app!); resave the rule.
Now select the profile saved and go in settings and check "apply active profile on boot".
Reboot the phone and enjoy your music glitchs free !!!

Could disable offload for audio in build.prop as an alternative.

I don't like that there is always icon for root access visible.
Sent from my A0001 using XDA Free mobile app

Is this the glitch that sounds like a sample of the audio gets repeated for a fraction of a second when screen is off at random times? I've noticed this with almost every player, only Apollo and the player that comes with CM12 don't have this issue, and it never happens when screen is on.

fards said:
Could disable offload for audio in build.prop as an alternative.
Click to expand...
Click to collapse
That dont remove all the glitches

gonna try this out, thanks!

My question is, why does 2 cores need to be on always to stop audio glitches? It worked fine with one core on kk. Why is it different on lollipop?
Sent from my A0001 using Tapatalk

That's a bit outdated. Not sure when this was done but I see two cores staying online. The CPU cores aren't related. Cyanogen is working on improving audio and getting it to work with nuplayer and enable offloading. There will be issues in the porting process.
Don't compare nightlies of cm12 to a stable near last build of cm11s. That's like apples to oranges. Their builds use hotplugging - mpdecision - not sure where your info is from.

worked for me

Worked for me too. Thank you!!

I cannot set to Min 300 mhz. any issues keeping as it is the default value? thanks

Going to try this .....Thanks for sharing..

In my case the audio shuttering while playing on my car stereo still remains although the duration between them is now long.
Sent from my A0001 using XDA Free mobile app

This seems to help quite a bit but doesnt solve all the issues when using with Bluetooth.
Here's my situation, using todays Nightly and stock CM12 kernel (or any for that matter):
wired headphones - everything works great.
bluetooth with screen on - stutters/laggy/distortion
bluetooth with screen off - everything works great.
I dove a bit deeper and also found this:
Bluetooth with car strereo (Subaru Impreza 2013 Sport Limited) -- stutters like crazy when screen is on.
Bluetooth with stereo headset - works great all the time.
Bluetooth with wireless speaker (Tango TRX) - works great all the time.
Bluetooth with Belkin BT stereo adapter - works great all the time.
So, my current conclusion is that this only has issues when using with my car stereo. This happens to be the only paired device that displays song/artist/album info on display. The others do not have this feature. I also have BT drops when using my car stereo answer phone calls.

danieldmm said:
That dont remove all the glitches
Click to expand...
Click to collapse
I've had this problem on a Galaxy S4 GPE Lollipop ROM, in that ROM's changelog:
-Turn off experimental NuPlayer by default - Should help fix some audio stuttering issues once and for all.
Worked for me. You can change this in developer settings. In my experience it's a combination of kernel issues and this setting.

This actually made things a hell of a lot worse for me!
Before I had pops every couple of seconds, enough to make me stop listening to music and only listen to podcasts and audiobooks.
After following your instructions to a tee I now get some bizarre time-stretching effect on bluetooth: everything gets pitched up with tons of audio 'holes' to make up for the contraction of the sound. Just tried to listen to Simon Mayo interview Colin Firth - it was like listening to Pinky and Perky MCing over breakcore.
I wonder if audio is ever going to work on lollipop on this damn phone...

nuplayer is the culprit
just disable nuplayer in developer options and no audio glitches
eViLsTieFel said:
nuPlayer is definatelly not the cause of the issue for me.
Disabling it on 20150131 nightly and the glitches are the same.
Click to expand...
Click to collapse
Use the latest temasek linaro build it works for me

nuPlayer is definatelly not the cause of the issue for me.
Disabling it on 20150131 nightly and the glitches are the same.

nikhil18 said:
Use the latest temasek linaro build it works for me
Click to expand...
Click to collapse
Wow, back-in-time-quoting, this sure as hell won't be confusing to anybody .
I just ended up installing franko's kernel r37 yesterday, fixed the issue for me.

Besides disabling nuplayer kills the ability to play web based videos entirely...
Sent from my A0001 using Tapatalk

Random Restarts of Moto G4 Plus

Hello Developers..
I have been using Moto G4 Plus from last 1 weeks with Oreo stock rom. Later I came to know to about 64 bit Pie build on xda. I flash latest 64 bit TWRP and Arrow OS Pie build. Everything seems fine but whenever I play Call Of Duty mobile, the phone get freeze and Restarts randomly. I disable heads-up notification as per one thread but problem was not fixed. So I flashed different 64bit android pie build available on xda but problem still persist. So does anybody knows it's fix or could it be possible for developer to bring this fix in future updates.

So after long research online i found fix for random reboots.. Its cause by high cpu frequency (ie 1651 MHz)kept by default in looney kernel settings. Its fix by lowering frequency by 1516 MHz and below. According to device specs its highest frequency is 1561 MHz and overclocking it can cause reboot issue due to high cpu temperature.