I want to get back to Screebl this fall and roll version 3.0. I'm going to focus on updating it to make it more 2.3/3.0+ friendly, and try to spend some time on dealing with the variety of issues that come in the form of "I've installed my own custom ROM on my toaster and Screebl doesn't work", which may mean simplifying things a bit. But I digress.
You guys at xda are the most demanding, critical, unrelenting, inflexible, opinionated crowd that I know of. You're also pretty smart. I'm curious to hear what those of you that use the app want to see in a 3.0 release.
dk
Surprised no one has chimed in here yet. First off I would like to say that Screebl is easily my favourite app, even though I mostly forget it is there. Whenever anyone new to Android asks what apps to install, Screebl is at the top of my list. OK, now that the brown nosing is out of the way...
Note: I have a Samsung Epic, currently running the latest leaked build of GB (EH06 as of writing this).
I would like some clarity on the interaction of Screebl and docks. For some reason I can't seem to figure out if it is ever enabled/disabled correctly while docked.
Ever since I started running GB leaks, Screebl has shot to the top of the battery consumption list. This may not be a Screebl issue, but instead something to do with how GB measures battery performance?
I would be nice to include the option to control time between screen off and screen locking.
A slider for choosing the maintained screen brightness, and/or the option to set it to the phone's default.
The option of a 'night mode', with different settings for maintained screen brightness and screen timeout.
Different settings for timeout while on the lock screen vs homescreen vs apps.
Glad to hear you'll get back to this app soon.
Since I updated my Galaxy S to 2.3.4 it stopped working.
I was so sad about this. Now my phone always turns off the screen without me wanting it to..
Wish you good work on it.
Peace
I have a couple of D2Gs running Gingerbread, since the update to Gingerbread the greatest consumer of battery life is the Display, I regularly see 40-60% usage and often only minutes of actual time on.
It seems to be a conflict between the built-in auto brightness and the Screebl low brightness setting. Low brightness is great except when you pull the phone out of your pocket and need to see something at midday...
I discovered that the Juicedefender brightness control manages to keep the brightness at a super low level most of the time, but still auto brightens the screen when required in bright light.
I guess my feature request would be either to have an option to completely remove the brightness control or to take it over with a system that keeps it on minimum brightness but with an user controllable setting to auto increase the backlight when the light sensor detects a particular value.
Thanks for a great app!
I need to update the docs and settings descriptions, but choosing "min brightness" will defer to the phone's sensor generally. That's what I use on my phones.
Dock stuff has been flaky and needs some revamping. I'm planning on redoing the entire loop and eventing framework for the app. It's gotten crazy complicated with all of the device-specific tweaks and conditions involved.
Support for custom lockscreens would be nice. E.g. disable Screebl when MiLocker is in the foreground. Had to stop using Screebl since I started to use MiLocker becuase I can't stand the stock ugly lockscreen.
Just wanted to give those of you that registered interest in Screebl 3.0 a heads up that I've done a ground-up rewrite of the app. It's in beta now -- not pretty, but the underlying engine should be better in many ways, including:
- more compatible with a larger number of devices (moved the accelerometer usage to more modern APIs)
- better with respect to power consumption
- simplified, removed some of the functionality that just didn't work well (like stillness detection)
Still lots of work and polish left to do, but if you want to play with the latest engine, take a look here:
https://market.android.com/details?id=com.keyes.screebl.beta
Let me know what you think!
keyesdav said:
Still lots of work and polish left to do, but if you want to play with the latest engine, take a look here:
https://market.android.com/details?id=com.keyes.screebl.beta
Let me know what you think!
Click to expand...
Click to collapse
I just tried Screebl Beta, and noticed that the proximity sensor is always on, even though the checkbox for it is not checked.
They way I can tell, is that with one of my old phones, the proximity sensor actually glows a faint red light when it's on. To save battery, shouldn't the sensor be off if the checkbox is not checked ?
Firstly, let me say thanks on producing a great app. Always my first installation on any new device.
I've had a small issue on my nexus 5, running 4.4.2 where screebl lite and screebl beta keep turning themselves off. It happens roughly once a day and I have to go into settings and re-enable screebl. Its only a niggle, and not worth uninstallation thankfully.
Good luck on Version 3. :victory:
Related
Most of you guys know about which apps are great but some never share.
So I'm hoping you will share some of those apps you like/love with us and those that visit the site. If you do please write them down and explain what they do and why you like them.
- SMART ROTATOR – Lets you rotate individual apps instead of everything. Some people claim the auto rotate wastes battery life so I’m giving this a shot and I like it. Even if it doesn’t save battery life.
- SETCPU for root users. If you want better battery life set it to max and min to 760. DOES make a difference and speed still OK. Want to see the atrix move even faster? Set max and min to 1000! REALLY NICE.
- DROIDLIGHT LED FLASHLIGHT. I like this one cause you click on the icon and it turns the flashlight on right away. There are others but I like this one better so far. BUT, I have not tried ALL of them yet
- KEYBOARD FROM ANDROID 2.3 (GINGER BREAD KETBOARD). Play with the setting till you get how you like it. Really nice.
- MYLOCK UTILITIES – Lets you set the screen unlock so all you have to do is press the power button and you’re in! No need to SLIDE the buggy screen unlock.
- BRIGHTNESS LEVEL (DONATE). I like this app so much I bought the donate version. It’s simple and fast. Let’s you adjust the brightness of the screen.
- TOTAL SCREEN CONTROL – MUST have app if you use your phone at night in bed. The default “0” setting is way to bright! So I use this to FILTER the screen and works and looks great! Saves battery and your eyes.
JasjarMan said:
Most of you guys know about which apps are great but some never share.
So I'm hoping you will share some of those apps you like/love with us and those that visit the site. If you do please write them down and explain what they do and why you like them.
- SMART ROTATOR – Lets you rotate individual apps instead of everything. Some people claim the auto rotate wastes battery life so I’m giving this a shot and I like it. Even if it doesn’t save battery life.
- SETCPU for root users. If you want better battery life set it to max and min to 760. DOES make a difference and speed still OK. Want to see the atrix move even faster? Set max and min to 1000! REALLY NICE.
- DROIDLIGHT LED FLASHLIGHT. I like this one cause you click on the icon and it turns the flashlight on right away. There are others but I like this one better so far. BUT, I have not tried ALL of them yet
- KEYBOARD FROM ANDROID 2.3 (GINGER BREAD KETBOARD). Play with the setting till you get how you like it. Really nice.
- MYLOCK UTILITIES – Lets you set the screen unlock so all you have to do is press the power button and you’re in! No need to SLIDE the buggy screen unlock.
- BRIGHTNESS LEVEL (DONATE). I like this app so much I bought the donate version. It’s simple and fast. Let’s you adjust the brightness of the screen.
- TOTAL SCREEN CONTROL – MUST have app if you use your phone at night in bed. The default “0” setting is way to bright! So I use this to FILTER the screen and works and looks great! Saves battery and your eyes.
Click to expand...
Click to collapse
last I read setCPU didn't work yet for the atrix due to differences in the atrix's kernel and the xoom. I could be wrong though
Yes, setCPU doesn't seem to work or work well on the Atrix. every time I restart the phone, it will give an error stating that setCPU have failed to start or something like that. I hope they fix it soon so I can OC the phone lol
keyboard from Gingerbread is amazing! Love it; it's so much more accurate than the stock Atrix keyboard and also more responsive.
I'm new to the android world, I need more apps to fill this phone up
circle battery widget
shows battery life in 1% increments rather than 10%
also, you can put it on the home screen so you can quickly check battery life without needing to click on anything
SETCPU work for me. CANNOT OC but it keeps it at 1000 which is very noticeable in speeds. Its also works to UNDER clock as well. You just have to enable profiles than create your own at the speed you want.
Hmm I wonder why setcpu won't work for me then. I've reinstalled it too.
I'll try the circle batt widget. Hopefully it'll work on mine lol
Sent from my MB860 using XDA App
I have a couple of "issues" with the phone. Not sure if its software related or hardware related. Maybe you guys can check on yours too see if it happens. This is all on stock ATT rom
It seems the One has "dynamic contrast" enabled by default. When scrolling on webpages, for example, if I come to an area with a dark advertisement, the brightness adjusts very slightly most of the time. Thats all well and good but the annoying thing is that it does it in steps causing quick blinks of the backlight. Its most pronounced at medium brightness. The same "blinking" happen when autobrightness wants to set the brightness to a very low level . It does it in very discrete steps and it takes a long time for the brightness to settle to its minimum.
If i set my brightness to 50% (most prevalent when the slider is under the "t" in brightness) I get a VERY subtle, but constant pulsating of the backlight. Again, Its a very subtle but my eyes pick it up regardless and its distracting as hell. I wouldn't mind it if autobrightness didn't hit this brightness level, but it does sometimes indoors. The effect is best seen on a mixed white and color screen, like a homescreen with a white widget and most websites. If the brightness goes a bit above or below this level, the pulsing goes away . Anyone else seeing this? maybe it happens at a different brightnesses on different screens.
Thanks
I noticed this when watching a video today. Maybe it only happens if you have autobrightness on?
Sent from my HTC One
It happens with autobrightness off for me. I actually tested it a bit more. I happens on a variety of backlight settings depending on what's on the screen.
At approx. 33% brightness (im using an app called screen adjuster to set the system brightness to a specific value), the screen does heavy pulsating on an all white image. For example, if I go to "about:blank" in the web browser. I can be seen on a desktop screen with a white widget or the settings menu.
Same thing at 40. Worst is 33% though. I have a feeling its dynamic contrast going haywire at certain brightnesses. If you turn the screen off then on, it doesnt do it for a second or 2, but then it will start. I haven't been able to find a demo unit anywhere around me to test this out. So if someone can check this on their device, I would appreciate it. Please use Screen Adjuster to get a definitive reading on the brightness. (Use the slider in "system brightness" to set it to a specific brightbess) and go to "about:blank" in the default browser
hi..
i had the widget set on the third setting, the fourth being the brightest. i had the same problem with my first phone and thought at the time it may have been a backlight problem? or power flow problem? i sent that phone back and the next phone did the same? after posting on here.. i removed the widget and manually adjusted the brightness. i like the screen quite bright, manual adjustment cleared the problem for me. i gotta say yep the flicker was more visible on screens with alot of white, google, facebook, texts? and way way annoying! i can only suggest you try the same as i did? perhaps it is just a quirk with the htc? or maybe the os? you never know, when the update to keylime or whatever it is called comes out the flicker may go totally?
JUST had this on facebook? hope it helps?
HTC One
HTC One : Update Available (1.29.401.12)
HTC is currently deploying an update for the new One
Version: 1.29.401.12 - Size: 229.04 MB
It includes :
- System Optimization
... - Updating Service Location
- HTC Zoe: Optimizing sound quality
- Camera: Optimizing Parameters
- Beats Audio: Sound enhancement
- other fixes
coming soon...
shep98 said:
hi..
i had the widget set on the third setting, the fourth being the brightest. i had the same problem with my first phone and thought at the time it may have been a backlight problem? or power flow problem? i sent that phone back and the next phone did the same? after posting on here.. i removed the widget and manually adjusted the brightness. i like the screen quite bright, manual adjustment cleared the problem for me. i gotta say yep the flicker was more visible on screens with alot of white, google, facebook, texts? and way way annoying! i can only suggest you try the same as i did? perhaps it is just a quirk with the htc? or maybe the os? you never know, when the update to keylime or whatever it is called comes out the flicker may go totally?
JUST had this on facebook? hope it helps?
HTC One
HTC One : Update Available (1.29.401.12)
HTC is currently deploying an update for the new One
Version: 1.29.401.12 - Size: 229.04 MB
It includes :
- System Optimization
... - Updating Service Location
- HTC Zoe: Optimizing sound quality
- Camera: Optimizing Parameters
- Beats Audio: Sound enhancement
- other fixes
coming soon...
Click to expand...
Click to collapse
Thanks for the response. I ended up looking at 4 more devices at 2 different stores and they all had the flicker. The sales associates even saw it. I got tired of doing exchanges and I ended up reversing my upgrade. Im going to wait and see what happens with this issue. Hopefully it gets sorted out with a firmware update, because otherwise its an awesome phone. Its a shame that the $100 trade-in offer is going to end by then and I wont be getting a free medialink device, but atleast i'd be able to get it in black, which is what I originally wanted.
Ive noticed this too and its really annoying me. Ive tried multiple roms including the new asop carbon rom and its even on that.
Mr Sliff said:
Ive noticed this too and its really annoying me. Ive tried multiple roms including the new asop carbon rom and its even on that.
Click to expand...
Click to collapse
In addition to the phones I exchanged, every display model that I've come across has had it. I'm was a bit surprised at first that not many people have come across this. I'm starting to think that maybe the One has a PWM backlighting, which some folks are sensitive to and some don't even notice. I'm in the former category and I think you are too. It a shame really that this problem exist. Besides that, I couldn't find any other faults with the phone. It was perfect in every other aspect
I've run Into the same exact behavior using the HTC droid DNA with both sense 4+ and sense 5 ROMs. I smell tomfoolery afoot.
Screen Flicker
I'm glad I'm not the only one that has noticed this. It doesn't stay that way very long for me, but it is quite annoying. Seems to happen when there's a white or light-colored background the most. So I guess there's nothing specifically wrong with my phone and we'll either have to live with it or wait until someone figures out how to fix it?
I guess most people don't notice this.m it's extremely irrational going between this and my tablet and having the black.ighting flashing in my face when I scroll through webpages.
I'm used to having my Android phones use apps like KinScreen or Gravity Screen to keep my screen on by motion. On my new Mate 10 (ALP-L29 8.0.0.119 (C636) I'm finding that no matter what I do, the phone's setting for display on time always control, even though I've excepted out both apps from battery optimization and from automatic control of their launch (manually set to run in the background). Anyone experience the same issue or have any thoughts? I don't know if this is an Oreo problem or a Miui one. Thx.
I am having the same issues, no matter what, with persistent notification active, the screen does not stay awake with kinscreen. Installed Wakey, seems to be working at least sometimes... Should be based on your eyes watching the screen...
According to TecTiq, the maker of KinScreen, it's a Miui problem. I'm not the only one to report it. Oh well....
One other possibility is to set your default screen timeout to something long, and then install Proximity Service, which seems to work well on the Mate 10 and turns on and off your screen by covering the proximity sensor. Creates a permanent notification, but installing AutoNotification cures that (as well as the other running notifications, like background Android processes, that you don't want).
EDIT: Nope, belay that! Once the phone sleeps, Proximity Service is still killed (even if excepted from Launch and Battery Optimization). Back to the drawing board....
Introducing Pixel Pulse - a simple app to make your Ambient Display pulse when you have notifications!
Choose the interval and select the apps you want you to cause your screen to wake.
Optional paid features let you select different icons and colors for specific apps but the interval and app filter core functionality is all free.
https://play.google.com/store/apps/details?id=com.compass.pixelpulse
If you had previously purchased Ambi-Turner, it has been updated for the new permissions, but because it was written for 8.0 and when Google's ambient display worked differently I decided to leave it as it is. You may however transfer your purchase status of Ambient Display to Pixel Pulse using both apps.
FIRST!
So, I've installed and tested and here are my initial findings:
It works great and looks gorgeous!
If you have your notifications set to display the notification contents, those contents will also flash on the screen.
The default display interval of 60 seconds works perfectly, but when I set it to 30 seconds, it flashed approximately every 10 seconds for some reason.
The notification it chooses to flash doesn't appear to be based on the most recent received or highest priority. Can you explain how the app knows which notification to flash on the display?
So far, there is no way to interact with the notification. Swiping away or double tapping do nothing.
The only way to wake the phone is to press the power button or fingerprint scanner.
This is a great start and I hope you please keep up the great work! I will be donating to the cause!
PuffDaddy_d said:
FIRST!
So, I've installed and tested and here are my initial findings:
It works great and looks gorgeous!
If you have your notifications set to display the notification contents, those contents will also flash on the screen.
The default display interval of 60 seconds works perfectly, but when I set it to 30 seconds, it flashed approximately every 10 seconds for some reason.
The notification it chooses to flash doesn't appear to be based on the most recent received or highest priority. Can you explain how the app knows which notification to flash on the display?
So far, there is no way to interact with the notification. Swiping away or double tapping do nothing.
The only way to wake the phone is to press the power button or fingerprint scanner.
This is a great start and I hope you please keep up the great work! I will be donating to the cause!
Click to expand...
Click to collapse
The times were accurate on my pixel 2, but my pixel 3 which only just arrived, was being stopped. Probably due the aggressive process killing I've read about. So this morning I quickly added a secondary wake to keep it from being killed. I'll sync the times when I get home from work.
It uses the natural order of notifications. A priority option would be a good idea.
No interaction yet, but that's planned. So is a blackout period (don't pulse when you're sleeping for example).
Ignore my comment about the notification priority - that was user error.
Feature request: Can you add an option to have the ambient display stay on (no pulsing) until the user bypasses the ambient display screen? The flashing of the ambient display is a little distracting when the phone is on a desk. This way, we could still tell at a glance when we have a notification waiting, but the screen will go back to all black once we act on it or simply unlock the phone.
I can try but it may not be possible without root.
grokus said:
I can try but it may not be possible without root.
Click to expand...
Click to collapse
No worries - this is xda, root is all we do!
grokus said:
Introducing Pixel Pulse - a simple app to make your Ambient Display pulse when you have notifications!
Choose the interval and select the apps you want you to cause your screen to wake.
Optional paid features let you select different icons and colors for specific apps but the interval and app filter core functionality is all free.
https://play.google.com/store/apps/details?id=com.compass.pixelpulse
If you had previously purchased Ambi-Turner, it has been updated for the new permissions, but because it was written for 8.0 and when Google's ambient display worked differently I decided to leave it as it is. You may however transfer your purchase status of Ambient Display to Pixel Pulse using both apps.
Click to expand...
Click to collapse
I have been working on a similar app, and could not find a way to get this to work while still allowing the device to doze, so the battery life is heavily impacted. Did you solve the battery drain issue?
BLuFeNiX said:
I have been working on a similar app, and could not find a way to get this to work while still allowing the device to doze, so the battery life is heavily impacted. Did you solve the battery drain issue?
Click to expand...
Click to collapse
I haven't noticed a battery drain issue, but I'm hoping xda can help find one if it exists. I'm not actually turning on the screen so doze should remain active.
grokus said:
I haven't noticed a battery drain issue, but I'm hoping xda can help find one if it exists. I'm not actually turning on the screen so doze should remain active.
Click to expand...
Click to collapse
Ah, I see. I have not actually run your app. I did not realize that your were pulsing the notifications themselves -- that's clever! For my own implementation, I am animating a fake LED that fades in and out, which obviously requires the screen to be on. The AOD has a way to doze with the screen on, but I have not found a way to expose that functionality to an app without root.
Anyhow, I see you are using setExactAndAllowWhileIdle to schedule your pulses. I wonder what the battery (and timing) impact is compared to setAndAllowWhileIdle?
Nice work on this!
I originally went down the road of doing a custom screen to mimic the LED until I came up with this idea.
From other threads I've seen some people will prefer that even if it uses slightly more battery.
BLuFeNiX said:
Ah, I see. I have not actually run your app. I did not realize that your were pulsing the notifications themselves -- that's clever! For my own implementation, I am animating a fake LED that fades in and out, which obviously requires the screen to be on. The AOD has a way to doze with the screen on, but I have not found a way to expose that functionality to an app without root.
Anyhow, I see you are using setExactAndAllowWhileIdle to schedule your pulses. I wonder what the battery (and timing) impact is compared to setAndAllowWhileIdle?
Nice work on this!
Click to expand...
Click to collapse
I'm willing to be a tester for you if you need one. Pixel 3, rooted with magisk.
There's now an option to be able to swipe to dismiss and double tap to open the app. I'm working on notification actions next.
grokus said:
There's now an option to be able to swipe to dismiss and double tap to open the app. I'm working on notification actions next.
Click to expand...
Click to collapse
Dude, you're a beast! Keep it up!
I may be able to use the real icons and colors. If so should I just remove the icon customization or would people still find that useful?
Hi mate, i bought your app right away. If you can integreat the original Icons for the famused apps, that would be great.
And can you look at the puls time? I set my time to 20 seconds but it puls every 40 - 50 seconds? Strange.
grokus said:
I may be able to use the real icons and colors. If so should I just remove the icon customization or would people still find that useful?
Click to expand...
Click to collapse
just as it is perfect now, only the repetition time does not work reliably
There is a possibility that the AOD stays on until the message has been read
Been looking for a way to customize the notifications since there's no LED light on this phone. I installed and bought you a coffee, I'll let you know how it goes. Thanks for your efforts.
Hi is this app only usable to Google Pixel phones???
Man this sounds like an awesome app however I'm on an LG V30 (which also doesn't have an LED but this doesn't seem to work. The notification interaction feature alone would be worth the donation.
I'll mess around some more and see if I can get anything
So here's a ROM that i would recommend even tho it's in beta Corvus OS it's android 12 and everything works even the Camera but sadly not the greatness of Sony's Camera app...i personally haven't tried it with the Custom Kernel Kirisakura just yet but i will and report back on here if they place nice together...Magisk also works great with this ROM you just have to be careful what you flash...
Hopefully our device will be fully supported soon.
Just putting down some thoughts here.
Double tap to wake is borked, the setting already hints that it is unlikely to work and I can confirm this.
Forcing native res works rather poorly. On reboot I need to reset the dpi to make the GUI play nice, but some things remain iffy. Such as:
Gesture navigation still thinks preview windows should be the lower res, not native (looks poor, see attached images)
Some random visual glitches that cause a silent crash + restore, it's not critical but you can see it happening
No built-in battery health (as in limiting it), have to use something external (AccA)
Camera quality is way worse compared to stock. I don't mind as much as I don't care a lot, but quality regression is very significant (if I have to quantify it, I would accept 20-30%, but this feels more like 60%)
The GCAM's I've found that don't immediately crash (not many) all have serious bugs
No camera app found that plays nice with front camera, hope you weren't planning on taking pictures with the front camera
Edit: For 6 you can actually use the native app. Performance is super bad though.
To not sound too much like a downer I'll also put in some "niceties" compared to stock.
Holding volume button to seek is now native
OTA work again
Good visual eyecandy for charging, locking and more
No bloatware galore
Much much finer control over lots of little things, especially status bar is very nice
Other things:
The default launcher is a bit lacking, so I installed Nova 7, but this still has some shenanigans with force reloading and short unresponsiveness with gesture navigation. Very annoying, but I'm quite sure this is not the fault of the ROM. Just hoped this was improved (suggestions welcome)
If someone found a good GCAM please share, the ones I've found are either broken or seriously lacking.
It seems that sometimes the phone does not respond to my finger until I press the button. This could be intentional to prevent accidental unlocks / phone being locked for X seconds because lots of "bad" fingerprints detected.
UsernameNotRecognized said:
Just putting down some thoughts here.
Double tap to wake is borked, the setting already hints that it is unlikely to work and I can confirm this.
Forcing native res works rather poorly. On reboot I need to reset the dpi to make the GUI play nice, but some things remain iffy. Such as:
Gesture navigation still thinks preview windows should be the lower res, not native (looks poor, see attached images)
Some random visual glitches that cause a silent crash + restore, it's not critical but you can see it happening
No built-in battery health (as in limiting it), have to use something external (AccA)
Camera quality is way worse compared to stock. I don't mind as much as I don't care a lot, but quality regression is very significant (if I have to quantify it, I would accept 20-30%, but this feels more like 60%)
The GCAM's I've found that don't immediately crash (not many) all have serious bugs
No camera app found that plays nice with front camera, hope you weren't planning on taking pictures with the front camera
Edit: For 6 you can actually use the native app. Performance is super bad though.
To not sound too much like a downer I'll also put in some "niceties" compared to stock.
Holding volume button to seek is now native
OTA work again
Good visual eyecandy for charging, locking and more
No bloatware galore
Much much finer control over lots of little things, especially status bar is very nice
Other things:
The default launcher is a bit lacking, so I installed Nova 7, but this still has some shenanigans with force reloading and short unresponsiveness with gesture navigation. Very annoying, but I'm quite sure this is not the fault of the ROM. Just hoped this was improved (suggestions welcome)
If someone found a good GCAM please share, the ones I've found are either broken or seriously lacking.
It seems that sometimes the phone does not respond to my finger until I press the button. This could be intentional to prevent accidental unlocks / phone being locked for X seconds because lots of "bad" fingerprints detected.
Click to expand...
Click to collapse
Yeah this is the only ROM that i found that legit decided to be custom and not just copy/pasta of Pixel Experience without the GCAM and a different name.....for what I use my phone for it's 100% functional...but it's far from being perfect for everyone rn...
Ainz_Ooal_Gown said:
Yeah this is the only ROM that i found that legit decided to be custom and not just copy/pasta of Pixel Experience without the GCAM and a different name.....for what I use my phone for it's 100% functional...but it's far from being perfect for everyone rn...
Click to expand...
Click to collapse
Yeah, this is why I've been very hesitant to install to install GSI ROMs, all the issues I've mentioned are because the X1 III is not the same as most other devices.
Wake to tap? Device specific thing.
Native res issues? X1III specific.
No built in battery health? Not device specific, devs pls
Camera issues? Device specific.
I think I'll drop the higher res as that will remove the most jarring of issues. The camera is whatever as it will not improve by switching to PE and double tap to wake is meh. Annoying at worst.
UsernameNotRecognized said:
Yeah, this is why I've been very hesitant to install to install GSI ROMs, all the issues I've mentioned are because the X1 III is not the same as most other devices.
Wake to tap? Device specific thing.
Native res issues? X1III specific.
No built in battery health? Not device specific, devs pls
Camera issues? Device specific.
I think I'll drop the higher res as that will remove the most jarring of issues. The camera is whatever as it will not improve by switching to PE and double tap to wake is meh. Annoying at worst.
Click to expand...
Click to collapse
True that...but hey it's there Incase people get bored lol
UsernameNotRecognized said:
Just putting down some thoughts here.
Double tap to wake is borked, the setting already hints that it is unlikely to work and I can confirm this.
Forcing native res works rather poorly. On reboot I need to reset the dpi to make the GUI play nice, but some things remain iffy. Such as:
Gesture navigation still thinks preview windows should be the lower res, not native (looks poor, see attached images)
Some random visual glitches that cause a silent crash + restore, it's not critical but you can see it happening
No built-in battery health (as in limiting it), have to use something external (AccA)
Camera quality is way worse compared to stock. I don't mind as much as I don't care a lot, but quality regression is very significant (if I have to quantify it, I would accept 20-30%, but this feels more like 60%)
The GCAM's I've found that don't immediately crash (not many) all have serious bugs
No camera app found that plays nice with front camera, hope you weren't planning on taking pictures with the front camera
Edit: For 6 you can actually use the native app. Performance is super bad though.
To not sound too much like a downer I'll also put in some "niceties" compared to stock.
Holding volume button to seek is now native
OTA work again
Good visual eyecandy for charging, locking and more
No bloatware galore
Much much finer control over lots of little things, especially status bar is very nice
Other things:
The default launcher is a bit lacking, so I installed Nova 7, but this still has some shenanigans with force reloading and short unresponsiveness with gesture navigation. Very annoying, but I'm quite sure this is not the fault of the ROM. Just hoped this was improved (suggestions welcome)
If someone found a good GCAM please share, the ones I've found are either broken or seriously lacking.
It seems that sometimes the phone does not respond to my finger until I press the button. This could be intentional to prevent accidental unlocks / phone being locked for X seconds because lots of "bad" fingerprints detected.
Click to expand...
Click to collapse
Alright some more shenanigans and needing to do a clean install further I do know some more things now.
1. is still broken, I'll try flashing a different kernel perhaps.
2. It's actually not so bad. It will remember and auto apply on reboot after a couple seconds. Gesture and notification bar may be slightly borked, but that's fixed fast by reloading system UI and switching between gesture and button navigation. The thing about recents has been resolved by switching to a different launcher with it's own quickswitch (lawnchair).
3. Acca works fine.
4/5/6 Nothing.
Another update.
2 is fine. Just don't use the built in launcher while forcing 4k. Just use lawnchair or something (+ quickswitch).
On another note, automatic brightness does NOT appear to work. This is quite the massive issue. I'm honestly a bit baffled how I haven't noticed until today.
AOD is also quite broken, while the phone is on the wireless charging and being ratiod to 90% it will continously blink. That's super annoying as I normally use AOD to check if I got a message, if it blinks it takes my attention, effectively defeating the entire purpose of AOD. *Groan*
These issues are really starting to stack up by now, I'm seriously considering reverting to stock. I'm really worried something else won't be working once I need it in the future.
UsernameNotRecognized said:
Another update.
2 is fine. Just don't use the built in launcher while forcing 4k. Just use lawnchair or something (+ quickswitch).
On another note, automatic brightness does NOT appear to work. This is quite the massive issue. I'm honestly a bit baffled how I haven't noticed until today.
AOD is also quite broken, while the phone is on the wireless charging and being ratiod to 90% it will continously blink. That's super annoying as I normally use AOD to check if I got a message, if it blinks it takes my attention, effectively defeating the entire purpose of AOD. *Groan*
These issues are really starting to stack up by now, I'm seriously considering reverting to stock. I'm really worried something else won't be working once I need it in the future.
Click to expand...
Click to collapse
No autobrighness may be caused by not having an overlay. I've also been annoyed by that on Pixel Experience. Can you create a fresh overlay for this phone and do a pull request with phhuson's repo? (I assume that's what must done)
thatguy222 said:
No autobrighness may be caused by not having an overlay. I've also been annoyed by that on Pixel Experience. Can you create a fresh overlay for this phone and do a pull request with phhuson's repo? (I assume that's what must done)
Click to expand...
Click to collapse
Well, sort of.
[Kernel][12.04.2023][Android 13] Kirisakura 3.0.1 for Sony Xperia 1 III aka "Sagami"
Kirisakura-Kernel for the Sony Xperia 1 III Hello everyone, To keep it short: Here is Kirisakura - Kernel for the Sony Xperia 1 III aka Sagami. Sagami is the internal codename for this years development platform of Sony Mark III devices. Please...
forum.xda-developers.com
Issue is that the "official" info provided by Sony seems to explicitly disable double tap to wake.
This makes absolutely no sense as double tap to wake works fine in the vanilla ROM.
Maybe someone can confirm this? It's been some time.
UsernameNotRecognized said:
Well, sort of.
[Kernel][12.04.2023][Android 13] Kirisakura 3.0.1 for Sony Xperia 1 III aka "Sagami"
Kirisakura-Kernel for the Sony Xperia 1 III Hello everyone, To keep it short: Here is Kirisakura - Kernel for the Sony Xperia 1 III aka Sagami. Sagami is the internal codename for this years development platform of Sony Mark III devices. Please...
forum.xda-developers.com
Issue is that the "official" info provided by Sony seems to explicitly disable double tap to wake.
This makes absolutely no sense as double tap to wake works fine in the vanilla ROM.
Maybe someone can confirm this? It's been some time.
Click to expand...
Click to collapse
It's available in stock but it has never worked correctly. The proximity sensor doesn't disable it! There's a "Prevent accidental operations with screen off" setting as the world's dumbest work-around. That puts a keyboard and alert on the screen while you're walking. It stops emergency butt-dialing but the battery still runs down.
kevinmcmurtrie said:
It's available in stock but it has never worked correctly. The proximity sensor doesn't disable it! There's a "Prevent accidental operations with screen off" setting as the world's dumbest work-around. That puts a keyboard and alert on the screen while you're walking. It stops emergency butt-dialing but the battery still runs down.
Click to expand...
Click to collapse
A what now? I do recall the proximity sensor not working really well with dt2w but at least it worked and I didn't notice some significant battery drain.
I did see some things about dt2w being disabled because the touch interface is powered when the screen is powered and this can't be decoupled. I'm not sure if this applies to this phone though.
Regardless, it shouldn't really matter as the X1 III is an OLED screen anyways. So as long as it's full black it should be fine(?)
I'm not asking for the perfect solution and if battery drain slightly increases that's a worthwhile investment to me. At least provide the option. Don't decide what I want because it has potential side-effects (just warn or something lol).
Actually I'm going out on a limb and stating that dt2w should be enabled by default if the device's screen is an OLED screen. Overlay and device specific things be damned.