yashsingh1/xdaforums huggingface dataset:
[Samsung Gear 2] bitstra:
[MENTION=803006]biktor_gj[/MENTION];

first results from testing the ts_always_on_disabled_kernel:

1.)

Seems the touch_event_handler consumes/remembers a touch when watch is in (deep)/sleep.

My watch was 'dark' for about 5 mins.

I've touched the screen - it stayed 'dark'.

I've pressed the home button - the watch awakes and goes immediately to System - Launcher -Menu...

Tried this several times - same result...

Can reproduce it forever...

2.)

In some situations I can touchwake the watch after long 'dark' periods...

but mostly it is not touchwakeable!

3.)

The screen brightness behavior when watch awakes is now better than before (with original kernel in ROM)!

Before it flashed with full brightness when awaked and dimmed down to chosen brightness level (after short flashing).

Now it wakes up with chosen brightness level as it should! :good:
[Samsung Gear 2] Darth Ziggurat:
Any chance of checking how many fps are actually drawn? I am seeing screen tearing so It very much looks like it is not drawing frames at native speed, not surprising if it runs at 120hz. I am thinking like if it only makes about 30fps there is no need to run it at 60hz at all. But if it can make 60fps then it sounds very reasonable for 60hz normal and 30hz in ambient mode.
[Samsung Gear 2] McGuigew:
Thanks for the credit ;)

The original DPI is actually 280. Then I changed it to 200 and thought it was really good. Then Gabri thought 240 was better and made a whole new tutorial for some reason...:confused:
[Samsung Gear 2] jeffc83:
Good catch...numbers just weren't my thing yesterday;) I went back to 200dpi this morning but this time, I increased the font.

Testing always on disabled kernel too...brightness speed setting is MUCH better now:D
[Samsung Gear 2] Gabri98:
My tutorial is for install apk , driver google , and modify to 240dip .

And i putted good tutorial simple and fast for new user of gear.

I think it's important not uneless (for me) :) because i want to help the people.
[Samsung Gear 2] jeffc83:
EDITED POST: I am experiencing the same exact symptoms as [MENTION=2981094]bitstra[/MENTION]
[Samsung Gear 2] McGuigew:
Weird, I just flashed disabled kernel and I have no change... touchwake works and always on screen goes dark and then totally black after maybe 10 seconds and then I get the bug screen and I'm obliged to reboot... I was supposed to flash that in the AP tab right?
[Samsung Gear 2] jeffc83:
You selected the correct option in Odin. The screen did wake once or twice for me after touching it but did not crash at all. Are you sure you didn't flash the always on enabled by mistake? You do have always on off under settings, correct? (that still doesn't work yet)

EDIT: I just disconnected my Gear 2 from the phone to switch back to my Urbane and the screen woke at the lowest setting when I did and never returned to my actual setting (brightness at 3) until I turned the screen back off and on. No big deal since it has only happened when disconnecting from the phone.

EDIT 2: It appears that the tilt to wake screen is working sporadically with the "disabled" kernel. A restart fixes it but it just stops working after "X" amount of time/wakes. (was able to duplicate it once so far)

Is anyone testing the "enabled" kernel? We need testers!!!
[Samsung Gear 2] McGuigew:
Oh OK, I misunderstood, I thought we were testing the always on screen. Thank you. However, touchwake seems to be working... didn't wait 5min yet, I'll let you know how it goes when I wait :laugh:
[Samsung Gear 2] daroota:
Not sure if its been mentioned.

Tried to power off and charge the watch but it wants to power on from off every time while power is supplied.
[Samsung Gear 2] jeffc83:
^^ It hasn't been mentioned yet but all wear devices turn on/boot up when charging. (at least the LG G Watch, LG Urbane and Gear Live do) It's a wear feature but not a good feature to users if you will.

On the disabled kernel, touch to wake is now working for me after a reboot. (it can be very slow to turn the screen on but it has every time so far...one test, it took about 5 seconds to wake the screen) Still testing but I am positive touch to wake is working! Okay, after MORE testing, it can take up to 15 seconds for the screen to come on after touching it...now that's an interesting delay, lol.
[Samsung Gear 2] Alxoom33:
That always is the case for me, also
[Samsung Gear 2] bitstra:
Here is the DL-Link for my Gear2-IR-remote-for-wear app.

If you want to have a look into UI and how to use the app - BUT WITHOUT REAL IR REMOTE FUNCTION - as long as we don't have access to consumer_IR_HAL.

DL-Link at AFH: https://www.androidfilehost.com/?fid=24052804347770116

- Install via adb

- at first start you get a message "OOPs - your device has no IR transmitter" and the app closes

- from second start the app runs without message in "normal mode".

Feel free to test it and report back what you're thinking about...
[Samsung Gear 2] biktor_gj:
I need to fix a good bunch of things on the touchscreen driver before it actually suspends the right way... I found out the always screen on disable is trying to suspend and waking it up again. For now stay with the always on enabled kernel to keep the watch stable

Not all are bad news! I got like a 5% working the screen always on feature! ;)

Now the screen goes black like it does on every watch, then it shows garbage as always, and then it shows the ambient mode! Then, every minute or so, it blanks the display, and the process starts again. I think I need to get the low power mode work across the LCD, the controller and the framebuffer so it finally stops crashing...

But the next kernels will come back from the crash while setting it up, so it's not that bad actually

By the way, suspend and resume in low power mode for the LCD are working now (a little less battery drain) ;)

Slow but steady!
[Samsung Gear 2] jeffc83:
This is great news, thank you Biktor! Switching over to enabled kernel right now;)
[Samsung Gear 2] McGuigew:
Just did as you asked, Lord commander of the nice watch :laugh:
[Samsung Gear 2] Gabri98:
Sir, do not worry we appreciate the work he is doing now .. do not worry we are there to support it! In a few days the gift a 3 beers for the big works and for the gentleman respect all user and reply to all and that does not boast as some of XDA Recognized developer :highfive:
[Samsung Gear 2] alirey:
Dear biktor_gj,

thank you for your fantastic work!

One question/suggestion:

In cinema mode I lost only 10% battery live in 12h and the messages are also send to the watch without display turning on and vibration.

Wouldn't it be possible to "modify" the cinema mode to activate the display and vibrate for incoming messages as long as the kernel issues for the normal LCD mode exists?

Thanks in advance...
[Samsung Gear 2] gyuri81:
hello! You can phone the gear2? android how many days it will go? Battery? How stable in everyday life?

Tapatalk-kal küldve az én SM-N9005-el
[Samsung Gear 2] Darth Ziggurat:
I do no't know if I know what you mean, but I will try

You can not use the Gear 2 to call people like you can in Tizen.

About 2 days

Very stable, just a few missing features. Will only crash if you use the feature "Always on Screen: YES"
[Samsung Gear 2] menissalt:
Please use the Q&A forum for this.
[Samsung Gear 2] Gabri98:
Re quote 2 days battery life is excellent for me :D
[Samsung Gear 2] biktor_gj:
NOTICE: All these files that I post outside the first post ARE MEANT FOR TESTING. They will have problems, they might lock your watch, and can cause more battery drain to the phone too.

These files are helpful for debugging the issues that are being worked on.

Now, to the point. My watch and I have an agreement. He does strange things while the screen is in always on mode, and I don't punish it in excess.

I've removed a lot of code from the S3C Framebuffer, patched some things to the clock suspend/resume functions in it, and some other things that I don't even remember.

This kernel won't get stuck with the always screen on mode, and it will more or less work. I still haven't found where does it blank, wrongly clear the framebuffer, and redraw when getting out of the low power mode and/or refreshing.

The question is, how does battery life react to this? Of course it will last less with the screen in always on mode.

On a LG G Watch R, this is about a 40% in 6 hours moving at random times (with screen on), so you have a reference.

On the Gear 2 it will last less, but I don't know if it's a lot or not.

I also don't know if it will affect the normal mode (screen always on== off)

Want to take a look? Just flash this via Odin as usual:

http://www.mediafire.com/download/y49sow0h92iswwm/alpm_s3csuspend_clockgating7_nopoweroff.tar

By the way, touch wake is enabled, so you can compare to previous kernels.

Let me know how it goes!
[Samsung Gear 2] jeffc83:
I just peed myself a little, LOL! Awesome as usual sir, testing as we speak:D
[Samsung Gear 2] bitstra:
Hi [MENTION=803006]biktor_gj[/MENTION],

thank you for this!

Just flashed - and hey a step forward - good job!

The fb-glitch when changing from ambient to normal screen is acceptable for me. Well done!
[Samsung Gear 2] molesaied88:
Just out of curiousity, if the gear 2 is AMOLED and the G Watch R is P-Oled, wouldn't the drain from Alway On screen mode be nearly similar? And correct me if I'm wrong, but doesnt exynos processors typically use less power than the snapdragon 400 found in the G watch R?
[Samsung Gear 2] jeffc83:
Well, I wouldn't go that far because it could cause seizures if you stare at it...lol;) HUGE step forward though!
[Samsung Gear 2] biktor_gj:
It's a really good question, on a physical level where all things are equal yes... But it is software side here, and grass is really greener on qualcom land.

Exynos kernel source is baaaad code most of the time. I might have deleted like 800 lines of code on the framebuffer alone which weren't in use, ir were colliding with other things. So there is a lot of redundant code everywhere, and more importantly, in my kernel and since lollipop release I've noticed that bluetooth, for example, takes the watch out of suspend almost every minute.

That means that, every 45-90 seconds, the second cpu core is activated, along with bluetooth, sensors, audio, camera, ir, everything, and then goes back to sleep. That is an enormous waste of power. If you add that the screen, and the screen controller staying always on, or waking up to redraw, it might get us 8 hours from 100 to 0%.

I'm trying to learn enough of linux's power management to modify the bluetooth and display driver (both mipi and lcd) to allow it to not wake everything up when it needs to do something little, but I don't know if that'll work

For now, make things work first, then try to make them waste as little power as possible :)
[Samsung Gear 2] molesaied88:
I wish I had the words to express how much I'm sure we all appreciate your efforts Biktor. What you're doing is seriously awesome and impressive. This definitely isn't an easy project and you seem to be flying through it. I'll be donating again as soon as I can!
[Samsung Gear 2] emuandco:
Yeah, nice progress indeed. The watch hops into always on mode and stays there for a while. Then it goes black, then very randomized colorful (FB mess?) and then back to always on in row. Buuut stable and it seems to drain way less power than I imagined. :D OK, will try tomorrow for a whole working day and then I will compare the power usage
[Samsung Gear 2] Alxoom33:
I flashed the new kernel, noticed that after going into the low power mode the screen flashes from a dark watch face to the dotted screen of death and then back to the low power watch face again, over and over again. Wakes up when shaked or if the screen is touched. I have screen brightness at 2, looks good!
[Samsung Gear 2] daevoq:
[MENTION=803006]biktor_gj[/MENTION] ...have u planned to fix "shazam issue" (or other apps that use mic)?
[Samsung Gear 2] biktor_gj:
Audio out I've already fixed it. Now I'm worried that it is too loud and may break the speaker at some point, but sounds nice.

Wear recorder seems to be working but shazam doesn't find anything, though I don't know what is the issue because it doesn't work with my g watch either.

Those changes will be in the next full update!
[Samsung Gear 2] jeffc83:
Shazam doesn't work on any of my smartwatches either...
[Samsung Gear 2] flatherskevin:
I posted a much more detailed account of my situation on the Q&A, but no one has responded yet and I have searched both forums entirely. I currently can't get wifi to work at all, and maybe I am doing something wrong, but bluetooth tethering doesn't seem to be working properly, and I am not sure how else I am supposed to get internet access on my Neo. I am not sure if this is a bug or not, so I posting here more as a bug report, and the Q&A has all my questions and detailed account. So I would presume that my questions be answered there unless it is a development related topic.
[Samsung Gear 2] jeffc83:
Our device does not support WiFi but bluetooth tethering has been working flawlessly for me when using the wear browser. (I am currently running wear on the Neo only for now) Anyone else having issues?
[Samsung Gear 2] bitstra:
Because it's summertime - some AirConditions controls will be added to IR-Remote wear(!) ;):
[Samsung Gear 2] mettercomputers:
Great Work

Great work best thing to happen to my T-Mobile Note 4. Looking forward to next update:D
[Samsung Gear 2] biktor_gj:
Nice one ;)

Can any of you guys tell me if this does even boot?

I don't have the watch at hand right now but I'm eager to test my reworked suspend/resume functions just in case I have fixed the screen problems...

It's probable that it will crash just as the screen dims, but who knows!

http://www.mediafire.com/download/5vxbtd5fwd2v546/kernel_blind_test.tar
[Samsung Gear 2] emuandco:
SO, some results with screen always on. Started at 100% today @ 08:30 and now 10 hrs later we reached 44%
[Samsung Gear 2] bitstra:
Donloading right now - will test it and report back

thanx!
[Samsung Gear 2] jeffc83:
Downloading and testing now as well! Thanks:)
[Samsung Gear 2] jeffc83:
^^ He beat me to it;) Same thing happens here.
[Samsung Gear 2] akelon:
the audio.tar file is no longer needed in the last full flash package? Not found audio.tar file

Enviado desde mi SM-N910F mediante Tapatalk
[Samsung Gear 2] rperezan:
You are right :) After the screen dims, garbage on screen and no way to return to the watch... Flashing back last one ;)

EDIT: I though I was the first :)
[Samsung Gear 2] biktor_gj:
Oh... okay... Then just one thing then,

Run with the screen always on, and once it crashes, connect it to USB, run this, and pass me the output (they should be small, if you get a big table with a lot of numbers no need to copy that):

adb shell

dmesg | grep s3c-fb

dmesg | grep s6e63j

Copy the output, reboot the watch and try with screen off and do the process again

Maybe I messed up with some switch setting or something... it looked so pretty :crying:
[Samsung Gear 2] a4t:
you dont need to download audio.tar if you already have the full flash (Wear_511_07_05_2015.tar)

Biktor already update that latest tar *with audio
[Samsung Gear 2] akelon:
Thanks [emoji106]

Enviado desde mi SM-N910F mediante Tapatalk
[Samsung Gear 2] DAGr8:
www.pastebin.com they are a lot of alternatives if that one is blocked at work try one of these :

http://www.moreofit.com/similar-to/pastebin.ca/Top_10_Sites_Like_pastebin.ca/
[Samsung Gear 2] alvaromartinezb:
Hello guys! I need help... I flashed the latest kernel yesterday and everything worked flawlessly... But today when I turned on my watch, I constantly received "android wear has stopped" message on the watch, I wasn't home any more so I didn't give any importance to it ... But later in the day, it was almost impossible to wake the device. So I decided to turn it off.... A few minutes later, it booted itself to download mode with an additional "factory mode" message... I turned it off and now its not booting AT ALL... As soon as I get home I will connect it to power... Perhaps it died (although it had like 50% yesterday)

Edit: I finally got home and plugged it in... It booted, I will keep digging into the issue.... If you want to have any loggs, just tell me how to get it!

Sent from my Nexus 5 - Android M developer preview 1
[Samsung Gear 2] tooandrew:
Edit: I was a ****. Try to pull a logcat
[Samsung Gear 2] alvaromartinezb:
I say it here, because it's not a question... The Q&A thread is for questions, what I'm doing is some sort of massive bug report... Believe me I'm the first one to say people (KINDLY!! ) to make the questions on the Q&A.

Sent from my Nexus 5 - Android M developer preview 1
[Samsung Gear 2] menissalt:
Guys can we start using the hide tag to prevent the wall of text?

Example:
[Samsung Gear 2] biktor_gj:
I know I sent you a PM but leaving this here in case someone else catches the same fault type (and now that I've read it again I'm sure of what you saw). That screen you saw shows up when there is a hard kernel failure. From the errors you saw before the crash, I think something started leaking memory in the kernel until it crashed badly. There are a couple of functions set by samsung in the kernel to debug these kinds of errors, and make it reboot to a special mode in the bootloader so you can download memory regions and check what happen ed before overwriting it. A simple press and hold until it reboots and everything should come back

One more question though, how long it was since you hadn't shutdown/reboot the watch?
[Samsung Gear 2] DAGr8:
Guys use pastebin to post logs. Thx
[Samsung Gear 2] akelon:
I have installed the rom toiiki is based on stock for gear 2 neo, need to back to rom samsung official stock before flashing this rom?

Enviado desde mi SM-N910F mediante Tapatalk
[Samsung Gear 2] tnbx:
Hello everyone , can anyone tell me how to conect the watch after a factory reset on the watch ?

I dont know what i did but the screen btightness got really low with the brightness settings on max i didnt know how to fix it so i made a factory reset now the watch is being stuborn to conect back was hoping to sinc my apps back to the watch but its not conecting any tip ?
[Samsung Gear 2] McGuigew:
When I have issues, I just reboot both devices and then it works... but your question goes in Q&A not here
[Samsung Gear 2] flatherskevin:
Please read forum rules before posting. It is rude to put Q&A material on the development thread. Please ask there.

On another note, I know that there are still some bluetooth tethering issues, minor but still present, but im getting network access on apps specifically made for wear and not at all on any sideloaded, fully functional apps. Is this a permanent issue or something that currently has been place behind IR blaster, camera, and screen always-on? If fixable, is it possible to write a code to trick the device the believe the bluetooth tether is an actual hardware wifi connection?
[Samsung Gear 2] jeffc83:
I didn't get the chance to answer your question in the Q & A last night. Push the apks to the /system/priv-app folder on the watch and chmod 644 all apks with adb/terminal or change permissions to rw,r,r and change the owner to System and the group to System with file manager. That should give you networking but I haven't messed with apps such as Pandora/streaming music apps but I do know Chrome worked. Have fun!
[Samsung Gear 2] McGuigew:
Chrome on the watch? Holly Molly!! How well does it work?
[Samsung Gear 2] menissalt:
Pandora crashes fyi
[Samsung Gear 2] jeffc83:
My apology, I have too many smartwatches...lol. Chrome may not work on Gear 2 due to the lack of WiFi but I do know that it will run well if it can get to the internet. (with my Urbane, I had to force it into Airplane mode to get networking and it worked fine except for the cut off screen)

[MENTION=980912]menissalt[/MENTION] - Thanks, I will take that off my list to test:) Hopefully ONE of the music streaming apps will work.
[Samsung Gear 2] tnbx:
Thank you for ur reply i ended up making another wipe and paired the watch again and sinced all the apps again so cool , tizen what is that ? Lol

Thank u biktor far making ouer watch so much better

Thanks for the reply McGuigew
[Samsung Gear 2] andrew.mackew:
So we can finally say that this is a daily driver, right guys? :good: Thanks for your excellent work [MENTION=803006]biktor_gj[/MENTION]
[Samsung Gear 2] jeffc83:
Absolutely! The screen always on feature wasn't even an option in Tizen so the only lost features are the IR blaster, Camera and calling from the watch. It has been stable for me the entire time:) Wear kicks Tizen's ass;)
[Samsung Gear 2] jbach44:
can you load apps from the android wear app on the phone?
[Samsung Gear 2] biktor_gj:
4382138325th test with the screen always on...

Working better. It's still not complete, but now it doesn't get too stuck, it just blinks every minute or so...

http://www.mediafire.com/download/njm5mde1m34i3aj/1107_2015.tar

For me it's usable now, except for the battery drain.

When it's in that mode, screen updates at 15Hz, but it doesn't seem a big change in battery life...
[Samsung Gear 2] jeffc83:
[MENTION=803006]biktor_gj[/MENTION], I'm sure you're probably getting sick of all the thank you's from me but thanks again for all your work, it sure is paying off:D Testing new kernel now, looking MUCH better so far!

EDIT: Just an FYI, for the first 5 minutes, the screen would wake itself up every so often for about 10-15 seconds then go back to ambient/dim mode. (seems like it was every third loop...the other two times, it would go black, wake for less than a second then go back to ambient/dim mode) Now it is just briefly flashing black exactly every minute to update the time and is definitely usable!!! I know you're getting close biktor because it is updating the screen as expected;)

EDIT 2: I'm going nuts staring at the screen now;) Every several minutes, it goes back to waking itself up for exactly 17 seconds, but only happens once then does it again within the next few minutes. (also shows garbage for 5-10 more seconds too) On the third loop, it woke itself up for exactly 6 seconds then displayed the garbage for 15 seconds. In other words, it is not very consistent but it DOES loop like that.
[Samsung Gear 2] biktor_gj:
To be fair, I feel like I'm killing power management a bit more with every change...

I'll show you:

PM SUSPEND on the frame buffer:

static int s3c_fb_suspend(struct device *dev)
{
struct platform_device *pdev = to_platform_device(dev);
struct s3c_fb *sfb = platform_get_drvdata(pdev);
int ret = 0;
u32 vidcon0;
#ifdef CONFIG_FB_HIBERNATION_DISPLAY_CLOCK_GATING
struct display_driver *dispdrv;
#endif
printk("s3c-fb: Suspend called\n");
mutex_lock(&sfb->output_lock);
flush_kthread_worker(&sfb->update_regs_worker);
vidcon0 = readl(sfb->regs + VIDCON0);
/* see the note in the framebuffer datasheet about
* why you cannot take both of these bits down at the
* same time.	*/

if (vidcon0 & VIDCON0_ENVID) {
vidcon0 |= VIDCON0_ENVID;
vidcon0 &= ~VIDCON0_ENVID_F;
writel(vidcon0, sfb->regs + VIDCON0);
sfb->power_state = POWER_DOWN;
printk ("s3c-fb: Video is down, shut down the display\n");
#ifdef CONFIG_FB_HIBERNATION_DISPLAY_CLOCK_GATING
dispdrv = get_display_driver();
call_block_pm_ops(dispdrv, clk_off, dispdrv);
#endif
} else{
dev_warn(sfb->dev, "ENVID not set while disabling fb");
printk("s3c-fb: Display was active when trying to suspend!\n");
}
pm_runtime_put_sync(sfb->dev);
mutex_unlock(&sfb->output_lock);
return ret;
}

Problem is, even with the display on, the suspend function gets called and thinks that the display is blanked. If I override everything on the PM suspend function the display crashes and doesn't come back. If I leave it as it is it does this sh** but at least comes back ;)

In the blind test what I did was keeping track of the blank mode on the framebuffer when entering suspend. If it was 0, it would do nothing (display active), if it was 4 (blanked/suspended) it would suspend...

What happened with that is when it was suspended it would come back, and when it was active it died until reboot... will keep thinking about it :)