yashsingh1/xdaforums huggingface dataset:
[One (M8) Q&A, Help & Troubleshooting] henderjr:
I have had a Vivosmart since the week they came out. I had a lot of the BT issues the first few months (mainly due to their software being released before it was really production ready) but has been fine since. I'm rooted and have ran a few different roms without an issue. Currently I'm using SkyDragon's Sense 7 rom. I haven't had to pair to my phone due to disconnects for at least a couple months. Are you pairing from with-in the Connect app? At one time the pairing was done via the regular android BT devices but they got rid of that and now pair from the app only. So technically your Vivosmart shouldn't ever show up on the list of installed/connected BT devices because it's only paired from the Connect app. I'm sure you've been on the garmin forum but if you haven't or someone else reading this hasn't it's here https://forums.garmin.com/forumdisplay.php?478-vivosmart. I've seen posts over there about m8 users having problems but don't remember reading if anyone was able to get the problem fixed and what they did. It doesn't make sense that it works for some (like me).
[One (M8) Q&A, Help & Troubleshooting] Semi666:
Hello,

I have same problem with Garmin Fenix 3. Apparently there is some bug in HTC ONE M8 Android 5.0.1

I am able to connect and connection is quite stable but watch wont reconnect automatically.

Usually it will reconnect once you reset BT on phone and than on watch. But its quite annoying so I am also looking for solutions. Any idea? Ive tried to add watch to trusted device under smart lock but its not working either. I know most Garmin devices worked on previous version of android on HTC ONE M8 but with Lollipop its bugged..
[One (M8) Q&A, Help & Troubleshooting] great_lumbuey:
G'day wakers,

I have had exactly the same problem with my m8. I also have only used insertcoin rom which may be part of the problem as I have an identical m8 with stock lollipop (never unlocked or rooted) and it has no problems with the vivosmart or Garmin Fenix BLE connection.

I have since sold my m8 and traded up to an m9, which is still stock, but I'm reluctant to flash custom Rom as the Bluetooth works perfectly... On the other hand, stock roms drive me mental with bloatware and ads.

If you try another Rom I'd be very interested to hear how you go...as it may give me some confidence to unlock my brand new m9.

Cheers.
[One (M8) Q&A, Help & Troubleshooting] wakers:
Cheers for the reply i might try a few different rom's i presumed that lollipop was the issue from what your saying maybe not then i'll let you know...
[One (M8) Q&A, Help & Troubleshooting] fivemarcus:
I have any M8 stock lollipop and vivosmart. When vivosmart go out of range lose connection. When vivosmart come Back near smartphone, if I want to connect it, i must switch off Bluetooth and switch on manually.

It is not auto.

Can you help me?

Thank you

Inviato dal mio HTC One_M8 utilizzando Tapatalk
[One (M8) Q&A, Help & Troubleshooting] Samyterje:
I'm experiencing an even worst problem with no pairing at all with my fenix 3 and Garmin Connect with Cyanogenmod 12.1 .

I've done the test with a Samsung SII, Oneplus X and Oneplus One. All pairing fail and all with Cyanogenmod 12.1

It's working well with a Samsung Galaxy S5 ! So if one Cyanogenmod developper is reading this, can you please let us know if this bug is known, or if you can log it, and i can help some troubleshooting as well.
[One (M8) Q&A, Help & Troubleshooting] Samyterje:
Solution found on my side by realizing that one dialog box is not scaled in Garmin Connect and so the "yes" button is not visible in material design. I've understood this by rolling back to Cyanogenmod 11 and see the process.

Workaround is to use a language with shorter words like english. My initial set was in French. So if it can help somebody else with Garmin Connect, use it :o
[E 2015 Original Android Development] squid2:
Squid TWRP

I also have a TWRP build that uses my kernel, compiled from source with the OmniRom tree. Links for it are it are on the main download tab. My device tree for it is on GitHub. My device tree is based off Cybojenix's TWRP tree for this device, but it uses a special stripped down version of my kernel instead of the prebuilt stock kernel. That is why my TWRP is 4 MB smaller than the Cybojenix version.

The latest build of my TWRP shows the correct time and includes hardware encryption support (thanks [MENTION=5650314]vlcdsm[/MENTION]).

UPDATE: I've made a separate thread for this TWRP.
[E 2015 Original Android Development] squid2:
Installation Instructions

The r11e version is the latest for Lollipop 5.1 ROMs. CM12.1 users and LPI23.29 stock users should use the version posted here. Users of the new LPI23.72 stock 5.1.1 should use the osprey version instead. See squid_kernel_r11e-osprey-stock.zip

For CM13 and similar Marshmallow ROMs, use my latest version (r12 at the moment).

My suggested install procedure:

Boot into TWRP (make sure you have a suitable ROM installed)

Flash my kernel zip.

Reboot into Android.

After following these steps, you will be running my new kernel. You can verify in Settings->About phone->Kernel version. If the ROM behaves strangely on first boot, reboot the phone. It should be stable after the second boot.

Attention 5.0 Stock ROM Users:

The latest versions of this kernel (r6 and up) are only for 5.1 ROMs. I suggest that you update to 5.1 if possible. If you need to stay on 5.0 and want my kernel, you will need to use the old r5 version.
[E 2015 Original Android Development] squid2:
Lionfish and Recommended Settings

My new Lionfish governor combines traits of the conservative, ondemand, and interactive governors. It is designed to maximize battery life without noticeably impacting performance. It responds quickly to heavy loads (similar to ondemand and interactive) while staying within the region of optimal CPU performance per watt. With moderate loads, it periodically votes to raise, maintain, or decrease the frequency. When there are enough votes to change the frequency, it is ramped up and down gradually. The voting mechanism reduces frequency jitter compared to ondemand and conservative. My testing had found that this governor uses moderate frequencies (where efficiency is optimal) more effectively than interactive, ondemand, and conservative. This improved frequency distribution results in a moderate reduction in CPU power consumption while maintaining responsiveness comparable to the interactive governor.

IntelliPlug is enabled by default in this kernel. The default governor is still interactive. For optimal performance and battery life, I recommend using the fiops IO scheduler, Lionfish governor, and lowering the CPU idle frequency to 400 MHz (from the default of 800 MHz). The combination of IntelliPlug, Lionfish, undervolting, and reducing idle to 400 MHz should result in a CPU power consumption reduction of around 20% compared to the stock kernel. This will typically correspond to 8-15% increase in battery life compared to the stock configuration.
[E 2015 Original Android Development] torch2424:
Well my phone is acting up, and I need to go ahead and start testing roms and things, but this seems like a great way to go! Anyone try this yet? Or will I be the first one? Thanks for your work dev!
[E 2015 Original Android Development] pixiebob:
squid: your kernel is already interesting, developement sound promising.

report:no problem hang or bootloop during boot,

---------- Post added at 09:30 PM ---------- Previous post was at 09:19 PM ----------

wifi not working unable to turn on,

but camera seems to works definitely even with root.
[E 2015 Original Android Development] squid2:
Hmm, WiFi works fine for me. My kernel requires signed kernel modules, but I do provide a Pronto WLAN driver signed for my kernel in the zip. Could you post the output of dmesg right after your phone boots up? Maybe that would give me a hint as to the cause.

Is anyone else having WiFi issues?
[E 2015 Original Android Development] torch2424:
Alright! everything working great! Everything works on my end, but I did notice a SLIGHT slowdown on the device with this kernel, but hey it's totally worth it for the root and everything working :D

My Steps:

I came from a fresh device (Moto E 2015 4g Unlocked GSM) which I never took the time to do anything so here's what i did

1. Unlock Bootloader using this: http://xdaforums.com/moto-e-2015/development/tool-moto-e-toolkit-one-click-unlock-t3047150

- Just follow the step and it worked fine for me! however, It wouldnt allow me to flash the recovery, it would just crash so...

2. Install TWRP from this thread: http://xdaforums.com/moto-e-2015/orig-development/twrp-moto-e-2015-recovery-t3049726

- I had to boot into fastboot (Hold Power and volume Down) and boot into my linux (ubuntu) to run the commands and successfully install the recovery

3. Boot into recovery, and BACKUP BACKUP BACKUP!

- To boot into recovery, I boot into fastboot, then use the volume keys until the little Dialog says recovery, the press power. I made a backup with twrp, Forgetting this step sucks, never forget...

4. Flash the kernel

- I flashed the kernel from twrp first to see if it had root pre-installed but it doesn't (Didnt check, but there was no supersu so I'm assuming so). Also, didnt check camera at this point

5. Install superSU/Root from here: http://download.chainfire.eu/696/SuperSU/ . Thank you to spblinux for this post: http://xdaforums.com/showpost.php?p=59761431&postcount=46

- I flashed the zip through twrp, and everything is working fine, and this is where I am now!

Thanks to the dev for his work. I will report back with more usage and thoguhts later!

Edit: Sorry for the typos, I'm a lazy typer. And Dont forget to hit the thanks button to the devs, and also me if I helped you out!

Edit:Edit: The download link is in the first post, there's some tabs at the top that link to it! (Took me a while to fins it haha)
[E 2015 Original Android Development] pixiebob:
here dmsg log, good luck
[E 2015 Original Android Development] torch2424:
Same here, no wifi issues for me! Thanks for the hard work!
[E 2015 Original Android Development] squid2:
I looked through your dmesg log and didn't see anything too noteworthy. I saw one potentially relevant message (below) that came from a piece of code that I added.

<3>[ 21.821810,1] subsys-pil-tz a21b000.qcom,pronto: wcnss: Failed to load blob wcnss.b11. Retrying. ERR -2

In my testing, I had encountered a race condition that caused WiFI firmware blobs to sometimes fail to load. I implemented a hack to retry loading firmware blobs if the initial loading failed. Quite often, at least one blob seems to fail to load the first time through, but it always works on the second attempt. The same thing happened on your end, as wcnss.b11 failed to load the first time through, but it successfully loaded on the second attempt. Anyway, I don't think this blob is the problem.

Have you tried rebooting and checking if WiFi works after that? I've never had any WiFi issues with my kernel, but I just want to rule out a race condition being the cause of your issue.

One more thing: Could you post the output of "cat /proc/modules" when WiFi is not working?
[E 2015 Original Android Development] squid2:
CDMA Variant Support

On the Q&A thread, bzo22 reported that the Boost Mobile version (XT1526) fails to read the SIM card when running this kernel. I did some preliminary investigation and found that the ramdisks differ. All Canadian variants of the XT1527 (Telus, Videotron, Rogers, and Wind) have the same CID and run the exact same software, free of carrier crapware, bloatware, or spyware. The unlocked variants sold on Motorola's website in the US should also be crapware free, though they have a different CID. However, the Boost Mobile variant is full of carrier specific stuff.
[E 2015 Original Android Development] squid2:
Test Kernel for CDMA Variant

Alright Boost Mobile people, I've made a test kernel for the CDMA variant. I don't know if it will work. Try it out and let me know whether or not your cellular connectivity works.

For some reason, XDA is giving me an "Upload Error: 500" when trying to post it to the downloads section, so I am attaching it to this post instead.

Reminder: THIS TEST KERNEL IS FOR THE LTE CDMA VARIANT (XT1526) ONLY! For the LTE GSM version (XT1527), use the normal version in the downloads section.
[E 2015 Original Android Development] bzo22:
Confirmed new kernel is working with cmda variant and yes camera is working
[E 2015 Original Android Development] pixiebob:
sorry but it does nothing:

adb shell

$ cat /proc/modules

cat /proc/modules

---------- Post added at 02:43 PM ---------- Previous post was at 02:24 PM ----------

i keep the kernel all the day and it is stable.

concerning wifi i try multiple time to reboot but always unable to turn on

i set minimal frequencie at 200 mhz but the kernel seem unable to reach this minimal ,i think undervolted is the reason of this difficulty being stable at lower frequencie,it is bad for battery life .
[E 2015 Original Android Development] squid2:
It looks like the kernel refuses to load modules on your phone. Rather strange, as the provided signed modules seem to work fine for everyone else. What happens when you do this on the phone:

su
insmod /system/lib/modules/pronto/pronto_wlan.ko

As for the 200 MHz step, I don't think undervolting has anything to do with it. It's probably the governor's fault. Try switching to the ondemand governor. I'm fairly confident that all frequencies will work. With that said, I found that setting the base frequency to 400 MHz gives a smoother experience without hurting battery life noticeably.
[E 2015 Original Android Development] pixiebob:
i obtain this on su:

insmod /system/lib/modules/pronto/pronto_wlan.ko

insmod: init_module '/system/lib/modules/pronto/pronto_wlan.ko' failed (Required key not available)
[E 2015 Original Android Development] squid2:
You must have a module version mismatch. This shouldn't happen, as the correct modules are provided in the zip. Which recovery did you use to flash my kernel? Did you use the TWRP linked in the first post, a different TWRP, or a different recovery altogether? When you go into the Settings->About Phone, what does it indicate as the kernel version?
[E 2015 Original Android Development] pixiebob:
oh sorry i understand my mistake, i fastboot flash only boot.

i will install zip.file containing wifi driver.
[E 2015 Original Android Development] pixiebob:
we have a kernel fully fonctionnal now ,wifi too, you seem to resolve issue camera when it's rooted
[E 2015 Original Android Development] thrasher194com:
I Flashed this rom last night... /w lionfish and fiops kernel mods ... good job building this rom. :good:
[E 2015 Original Android Development] thrasher194com:
I've had 3G data all day.. WiFi tethering works! LTE isn't working yet.
[E 2015 Original Android Development] squid2:
LTE has been hit and miss on custom ROMs for the CDMA variant. Some have had it working, others have been having issues.

You can try flashing this patch: https://drive.google.com/file/d/0B46DbOH2IgChRndzVmhqd1BQZ0U

I think it is by [MENTION=456243]SuperR[/MENTION] or [MENTION=4658982]starkly_raving[/MENTION]. They know more about the CDMA variant than I do.
[E 2015 Original Android Development] starkly_raving:
That fix gets LTE "working" but the issue is deeper. Its something to do with telephony and provisioning because the 3G network shows as "00000" and LTE shows as "Sprint" which its just reading off the UICC card I'd guess. I've reached out to a couple developers in various forums(that had solved the issue of other devices) and haven't had any luck contacting them.
[E 2015 Original Android Development] thrasher194com:
That's fixed LTE , thanks guys
[E 2015 Original Android Development] rmpcunha:
Mates, i've been mentioned many times about this but it's a mistake.... I don't even know what this is about.... ?
[E 2015 Original Android Development] thrasher194com:
I installed LTE Discovery, it has detected band 26 (LTE)
[E 2015 Original Android Development] starkly_raving:
I'm on 41...
[E 2015 Original Android Development] thrasher194com:
http://i1244.photobucket.com/albums...creenshot_2015-08-13-21-33-34_zpsuktktfxf.png
[E 2015 Original Android Development] Filz0r:
I'm having battery drain overnight and throughout the day, and it is taking 1h of screen on time since last build...

Here are some printscreens of the battery use on this link
[E 2015 Original Android Development] thrasher194com:
What I/O schedule and Governor are you using?
[E 2015 Original Android Development] Filz0r:


Lionfish and fiops with min clock speed at 400mhz because on 200mhz the drain was more noticeable
[E 2015 Original Android Development] thrasher194com:
Have you calibrated your battery stat after flashing new ROM?
[E 2015 Original Android Development] Filz0r:
No i haven't, because on this device nobody ever talked about calibrating the battery after flashing a new ROM. Could you give me a method to do it then?
[E 2015 Original Android Development] squid2:
That's the optimal configuration (lionfish, fiops, 400 MHz idle), but you are getting much less battery life out of it than I am. On a full charge, I get 5-6 hours screen on time spread over 3-4 days. I don't have gmail syncing enabled though, so that saves a lot of battery life.

Do you get similarly sub-par battery life on a clean install? It's usually installed apps that eat up battery life rather than the kernel.

EDIT: I looked at your screenshots of battery stats.

The idle drain seems much higher than what it is for me. When I don't use my phone much, it lasts for 10+ days on a charge with 2 hours SOT. It looks like the Nabu X utility is a battery hog. Have you checked for wake locks? Also, check your CPU stats using an app like CPU spy. Is the CPU on time much greater than the screen on time?

Also, what is your screen brightness set at? I usually use auto brightess with the slider set to about 1/3 on the scale.
[E 2015 Original Android Development] thrasher194com:
Search in playstore for battery calibration by nema...

Charge device 100% hit calibrate unplug power. Os regenerated new battery stat.
[E 2015 Original Android Development] Filz0r:
I've updated the files on my drive folder with a few screenshots from CPU spy, while my phone is on 84% battery.

I also don't have sync turned of and my brightness is set manually but its normally at 50% except when I'm outdoors, then I set it to 100%.

Indeed nabu x utility is having a lot of wake locks, and I've got greenify installed also to try and prevent these wake locks I'll try and force sleep on the nabu x app to see if there is any improvement. And also when my battery is at 1% I'll update my gdrive folder with some prints off CPUs spy
[E 2015 Original Android Development] EB20XY:
Would be great to add governor InteractiveX and scheduler SIO here. :p
[E 2015 Original Android Development] thrasher194com:
Hey is there flash able mod for 12.1 for lionfish and fiops im 8/17 cm12.1
[E 2015 Original Android Development] squid2:
Now that scritch's CM12.1 has been upgraded to using 5.1 blobs, I can make a standalone flashable kernel. It will probably be a couple days before I get time to post a new build though that works with scritch's CM.
[E 2015 Original Android Development] squid2:
Squid Kernel r7

I have a new release that merges in the latest changes from everywhere (Linux, Qualcomm, and Motorola). The new release also adds a few extra WiFi driver features. Furthermore, I added in CPU touch booster support, configurable via /sys/module/cpu_boost/parameters/

Users who were having WiFi issues should try the new build and see if it fixes anything.

The two builds I've posted today (squid_kernel_r7.zip and squid_kernel_r7-CDMA.zip) are for the GSM and CDMA stock ROMs respectively. I don't yet have a CM12.1 kernel ready, but I'll try to post one tomorrow if I get time.

I haven't had time to switch over to AnyKernel yet, so for now, the stock GSM, stock CDMA, and stock CM12.1 kernels will have different zips. In the future (hopefully r8), I will have a unified zip that works on all ROMs.
[E 2015 Original Android Development] dwane3:
Thanks,please made the new build cm12.1 with new kernel.
[E 2015 Original Android Development] starkly_raving:
[MENTION=6485916]squid2[/MENTION] CDMA r7 didn't boot for me, was stuck at the boot animation. ADB didn't recognize the device so couldn't get a kmesg... :-/
[E 2015 Original Android Development] squid2:
I had tested it on the LPI23.29 stock ROM for XT1527 (GSM) and it worked fine for me. I hadn't changed anything specific to the CDMA model, so I don't yet know what broke it. Is anyone else having issues? Or is it working fine for others?
[E 2015 Original Android Development] starkly_raving:
Cleared cache and dalvik and reflashed it and its fine....
[E 2015 Original Android Development] squid2:
Squid Kernel r7b

I have a new build of r7 that features a redesigned universal flashing script. This new build should work on any variant of surnia (GSM, CDMA, Dual Sim etc). It will also work on scritch's latest CM12.1 build (20150817 build 39) and any other new custom ROM that supports enforcing SELinux. The download is up on the downloads tab.
[E 2015 Original Android Development] Fedray:
All working good bro, amazing job. Your best choice of governor/scheduler is lionfish and fiops right?

Enviado desde mi MotoE2(4G-LTE) mediante Tapatalk
[E 2015 Original Android Development] thrasher194com:
Flashed r7b on cm12.1 8/17 and running awesome. Only thing where did my scheduler go?
[E 2015 Original Android Development] EB20XY:
Squid Kernel r7b

It works fine. :good:

Thanks a lot !! :highfive:

Great ! :victory:
[E 2015 Original Android Development] grofweg:
+1, Strich's surnia 39 and this kernel are a very nice couple.
[E 2015 Original Android Development] Filz0r:
I've flashed your latest kernel over your previous CM build. But sensors and camera do not work, I'll try and flash strich's 39th build to she if it works, thanks a lot for your work!

EDIT: After dirty flashing the latest cm build with the new kernel build cameras and sensors are working again, and so far I haven't seen any problem except a minor nova launcher and aoso keyboard crash but it was only right after booting so maybe it has nothing tondo with this
[E 2015 Original Android Development] squid2:
Squid Kernel r7c

I've posted a new build that has updated WiFi drivers. This combination of WiFi drivers and configuration has been working well for osprey (3rd Gen Moto G) users on CM12.1, so hopefully these new WiFi drivers will fix the DHCP issues that certain surnia users have been having on CM12.1. WiFi has worked fine the the whole time with my router, so I don't know if they fix anything for sure.
[E 2015 Original Android Development] Filz0r:
I've never had any problem with WiFi on previous builds but after flashing your kernel with the latest build of CM And I'm having WiFi problems with your kernel flashed, its probably the ROM
[E 2015 Original Android Development] dwane3:
Thanks for the hard work!May be you rebuild cm12.1 with fixes?Thanks.
[E 2015 Original Android Development] starkly_raving:
The WiFi issue is with the ROM (for those of us having it). I've found a fix that works perfectly...

Download this zip...

https://drive.google.com/file/d/0B46DbOH2IgChUGN1X1ZyRXczRUk/view?usp=docslist_api

Extract it with an archiving tool/file explorer. Copy the files from the extracted wlan/prima to root/etc/firmware/wlan/prima and set permissions to 0644.

Reboot and profit...
[E 2015 Original Android Development] diafero:
I am currently running the r7 build (and build 39 of scritch's CM), and I am still having some trouble with WiFi: The device is not automatically connecting to new networks while being in stand-by. This morning, I arrived at work, waited for 1-2 minutes with the device in WiFi range, and then turned on the screen - to see that the device was not connected to WiFi. 10-20sec later, the connection was successfully established.

On Monday, I can report whether r7c fixes anything here. Or is this probably a ROM issue? I used to have the same trouble with scritch's kernel, but didn't try again with build 39.