Related
Yet Another Auto Brightness (YAAB)
A small open source application designed to enhance user control over screen brightness. Initially it was developed to make the screen as dim as possible to save battery on old devices. AND to provide a simplest possible user interface without any complicated calibration procedures and so on.
It is Beta version now. It has ascetic interface and very simple in use.
Source code, issue tracker and latest APKs are available here: http://bitbucket.org/gyrussolutions/yaab/
Google Play link: https://play.google.com/store/apps/details?id=biz.gyrus.yaab
Any feedback is highly appreciated, especially from other Android developers
Tester initial impressions
A nice small download and a simple and clean interface. Started service and it immediately started dimming my brightness. A few points to begin with:
The manual slider does not seem to work as there was no change in the brightness.
It doesn't seem to alter the brightness in different lighting (unsure if it is supposed to do this or not from documentation).
It is making my screen too dim, I have a GT-I9300 and the auto brightness on it is excellent and always keeps my screen at the good readable and useable settings.
Will run for an hour or so now and update this with further thoughts then.
---------- Post added at 05:13 PM ---------- Previous post was at 05:06 PM ----------
Ok it's keeping my screen to dim to be usable so have had to uninstall for now. A few further points though:
Application Force Closes when you stop the serverce.
The manual slider does not work.
Handset - GT-I9300
ROM - Paranoid Android 2.51
OK log wouldn't upload, here's a link for it on dropbox.
https://www.dropbox.com/s/mbyfz33b7audtxz/2012-11-02-17-10-36.txt
Good report, thanks a lot.
Looks like the app incorrectly reads light sensor data on your device and thus brings brightness to minimum.
I'm working on the issue now.
andrvo said:
Good report, thanks a lot.
Looks like the app incorrectly reads light sensor data on your device and thus brings brightness to minimum.
I'm working on the issue now.
Click to expand...
Click to collapse
Let me know when you have a new version and will test again for you.
Hi!
IIIIkoolaidIIII said:
Let me know when you have a new version and will test again for you.
Click to expand...
Click to collapse
I did some research tonight and found out that many people have concerns about light sensor behaviour in your ROM.
I wrote a very simple app that shows sensor parameters on the screen and displays all subsequent updates received from the sensor.
APK is here: https://bitbucket.org/gyrussolutions/lightreader/downloads (sources are available there also)
It doesn't require changing settings and it will not attempt to change screen parameters also. Minimal discomfort
Could you please run it on your device and post here its output in a dark room and under strong light?
Thanks.
andrvo said:
Hi!
I did some research tonight and found out that many people have concerns about light sensor behaviour in your ROM.
I wrote a very simple app that shows sensor parameters on the screen and displays all subsequent updates received from the sensor.
APK is here: https://bitbucket.org/gyrussolutions/lightreader/downloads (sources are available there also)
It doesn't require changing settings and it will not attempt to change screen parameters also. Minimal discomfort
Could you please run it on your device and post here its output in a dark room and under strong light?
Thanks.
Click to expand...
Click to collapse
Details bellow, Sensor name - CM36651 Light sensor
Darkened Room:
Accuracy 3, MAX 121240, last 0.0
Bright light:
Accuracy 3, MAX 121240, last 3700.0 (fluctuating around this point)
I've not read much in relation to sensor issues on this ROM, will do some digging myself now. Hope this information is useful to you.
B
---------- Post added at 11:05 AM ---------- Previous post was at 10:48 AM ----------
I have just done some digging and found no Liight sensor issues mention in the CM10 threads or known bug list. There was a light sensor issues back in September for Paranoid Android but this was fixed back then. Where have you seen the information about peoples concerns with the light sensor?
I have attached a link to the CM10 known issues bellow.
http://teamhacksung.org/wiki/index.php/CyanogenMod10:GT-I9300:Nightly:Known_issues
I saw several mentiones of light sensor problems here on the forum, like this: http://forum.xda-developers.com/showpost.php?p=31801837&postcount=2862 or this http://forum.xda-developers.com/showpost.php?p=31801837&postcount=2862
Some other mentiones on other forums/blogs.
But anyway your readings are very good, so the sensor isn't a culprit any longer.
I just had to make sure that the app has valid input data and the problem is somewhere in the algorythms. Because in the log file you submitted yesterday contains very strange values.
Thanks again. I'm going on with my investigation.
andrvo said:
I saw several mentiones of light sensor problems here on the forum, like this: http://forum.xda-developers.com/showpost.php?p=31801837&postcount=2862 or this http://forum.xda-developers.com/showpost.php?p=31801837&postcount=2862
Some other mentiones on other forums/blogs.
But anyway your readings are very good, so the sensor isn't a culprit any longer.
I just had to make sure that the app has valid input data and the problem is somewhere in the algorythms. Because in the log file you submitted yesterday contains very strange values.
Thanks again. I'm going on with my investigation.
Click to expand...
Click to collapse
Yeah those were two months ago and the bug was fixed in a few days, there have been about 10 version updates since then as well.
Let me know when you're new version is available and will test again.
B
Maybe you should restrict app installation to devices that have a light sensor? Because Google Play allows me to install it even tho I don't have one.
HTC Wildfire S (Marvel)
Works as intended on HTC Wildfire S (Marvel) 510e.
Brightness is applied 1/2 secconds after screen is on and with correct levels acording to the external light and manual adjusment seting.
I like the simplicity (pls don't change that) and, so far, I didn't noticed any bad impact on battery life.
I'm curently on custom SENSE 2.1 rom but I switch often so will test this one on them too.
Tnx,
GermainZ said:
Maybe you should restrict app installation to devices that have a light sensor? Because Google Play allows me to install it even tho I don't have one.
Click to expand...
Click to collapse
Will be done, thanks. I don't know how could I have missed that
kobredabre said:
Works as intended on HTC Wildfire S (Marvel) 510e.
Brightness is applied 1/2 secconds after screen is on and with correct levels acording to the external light and manual adjusment seting.
I like the simplicity (pls don't change that) and, so far, I didn't noticed any bad impact on battery life.
Click to expand...
Click to collapse
Thanks for the update.
We are working on automatic/manual "night reading" mode and manual range adjustments now, but we intend to keep the main screen and the defaults in this way, so most of the users would not even need to open menus and dig deeper into the settings.
IIIIkoolaidIIII said:
Let me know when you're new version is available and will test again.
Click to expand...
Click to collapse
I've uploaded current version to the downloads section: https://bitbucket.org/gyrussolutions/yaab/downloads
Check this one please when you have time.
To be honest I still don't know why did it set brightness to minimum on your phone and didn't ever rise it again.
But your log revealed a number of thread synchronization issues that I fixed in this version. I believe there could be connection between these issues and your dark screen.
UI is a bit different, it is my current development version. But start/stop buttons still do the same.
Don't wait long, 10-15 seconds is enough, if it doesn't track ambient light changes right from the beginning - it will not start after some minutes.
Thanks.
Hi andrvo,
Yaab works on my Nexus 7. It is also very easy to use. But I have two remarks.
First the app starts in portrait and I only use me tablet in horizontal view. The app not only starts in portrait, it does also not change to horizontal. This would be nice, if the app would start with mentioning the position.
The other point is, that it only needs one more option in my case. There is automatic and manual brightness. If I can use the manual slider in the automatic mode to set a basic brightness, this would be handy. Hope you know what I mean.
Thanks for your work. Would be nice to find Yaab on Google Play to get updates automatically.
Thanks, checking it out...
benkxda said:
First the app starts in portrait and I only use me tablet in horizontal view. The app not only starts in portrait, it does also not change to horizontal. This would be nice, if the app would start with mentioning the position.
Click to expand...
Click to collapse
Yes, it is my fault. I didn't have enough time to test those layouts on tablets.
I plan creating layouts for tablets from scatch since existing were designed mostly for phones.
benkxda said:
The other point is, that it only needs one more option in my case. There is automatic and manual brightness. If I can use the manual slider in the automatic mode to set a basic brightness, this would be handy. Hope you know what I mean.
Click to expand...
Click to collapse
Well, it works almost as you describe. "Manual adjustment" actually set the base line for the automatic brightness formula.
I'm preparing new release right now, will be available today or tomorrow. New version also allows to limit top and bottom values of brightness, maybe it will fit your need
benkxda said:
Thanks for your work. Would be nice to find Yaab on Google Play to get updates automatically.
Click to expand...
Click to collapse
It is here: https://play.google.com/store/apps/details?id=biz.gyrus.yaab
Test it on Galaxy Note 2
Everything looks working. Closing the sensor with my hand causing the screen light dim.
Not sure what idea I can give though, probably you can check 'smart stay' feature at Samsung S3/Note 2. Although it's not a screen auto-brightness thing but it have same objective about saving battery from screen consumption.
andrvo said:
Yes, it is my fault. I didn't have enough time to test those layouts on tablets.
I plan creating layouts for tablets from scatch since existing were designed mostly for phones.
Well, it works almost as you describe. "Manual adjustment" actually set the base line for the automatic brightness formula.
I'm preparing new release right now, will be available today or tomorrow. New version also allows to limit top and bottom values of brightness, maybe it will fit your need
It is here: https://play.google.com/store/apps/details?id=biz.gyrus.yaab
Click to expand...
Click to collapse
That new release I get then via Play, thanks for that. Delighted me.
jimmod said:
Test it on Galaxy Note 2
Not sure what idea I can give though, probably you can check 'smart stay' feature at Samsung S3/Note 2. Although it's not a screen auto-brightness thing but it have same objective about saving battery from screen consumption.
Click to expand...
Click to collapse
Ok, I'll check it, thanks.
Version 1.6 is rolling out to the Play store.
What's new:
night mode, manual and automatic. The latter will work only on new devices with high quality sensors which are able to provide accurate values in the lower part of the range. Manual works on any device.
range controls added. Now it is possible to shrink the actual range of automatic brightness values.
bugfix (of course)
Beta testing is still going on, all testers are welcome.
Fresh APK is also available here: https://bitbucket.org/gyrussolutions/yaab/downloads
Before my Asus tf700 Infinity, I owned a Samsung Galaxy Tab. I purchased some programs and games for it, and all was well until it was stolen. The problem? Now I've downloaded and used those same apps on my tf700 Infinity, and the orientation is off by ninety degrees on quite a few. It has to do with Android's API and Honeycomb, and how the default base orientation is set in the framework policy. Before tablets, the default orientation for the Android API was portrait, but tablets made landscape defaults a possible better default. Apps not written to accommodate this would have the sensors read 90 degrees skewed for landscape default devices (like my tf700), because the sensor data is being read from landscape (regardless of orientation), but interpreted as portrait by the app. Even though my Galaxy Tab was a tablet, it's default orientation was portrait, so there was no 90 degre skew. I have read enough to know that it's possible to change the Android system default value, but it has to be changed in the framework . . . No easy task, especially if the rom is ODEXed.
So . . . anyone have any advice or fix so my paid apps aren't wasted money? I don't think emailing every single developer is the key, when I could modify a single system value to fix the problem for all apps. Thanks in advance, any help is appreciated.
Doesnt ever gyro-based app/game have a recalibration setting? Have you tried that?
Send From My Samsung Galaxy S3 Using Tapatalk 2
GrayHat137 said:
So . . . anyone have any advice or fix so my paid apps aren't wasted money?
Click to expand...
Click to collapse
You could try Ultimate Rotation Control. It can have an individual setting for each application (Forced Portrait/Forced Landscape/Forced Auto).
ShadowLea said:
Doesnt ever gyro-based app/game have a recalibration setting? Have you tried that?
Send From My Samsung Galaxy S3 Using Tapatalk 2
Click to expand...
Click to collapse
The problem is that the data the app is getting is from the sensors is rotated 90 degrees. For example, if the app assumes the tilt data it is getting is from the left and right: tilt left, go left. On my tablet, it's default boot state is landscape, so if the app is asking for the sensor info the wrong way (a deprecated way - from before the Honeycomb API), it's getting the tilt axis from the top and bottom, so: tilt up, go left. I can calibrate, but I still have to tilt up to go left.
Sounds like badly programmed apps to me. Have you tried asking the devs to update based on the correct APIs?
HeartWare42 said:
You could try Ultimate Rotation Control[/URL]. It can have an individual setting for each application (Forced Portrait/Forced Landscape/Forced Auto).
Click to expand...
Click to collapse
I had hoped it would override the default framework, but apps were still polling the sensors wrong no matter which orientation they were displayed in. The sensor data was rotating the same amount as the app, but the original sensor data was still originally off by 90%.
Thanks for the tip; Ultimate Rotation Control is a good app that solved another issue I had, just not this one.
sbdags said:
Sounds like badly programmed apps to me. Have you tried asking the devs to update based on the correct APIs?
Click to expand...
Click to collapse
Yes, that's the consensus. Some I've asked, others are no longer in active development (nostalgia for holding onto these apps). I stumbled upon a web hit while googling for answers, the solution was about changing a simple setting in the android framework, but I'm a not experienced with ADB, and things like ODEXing and DeODEXing are nerve-wracking while I learn and experiment.
Also, thanks for coming sbdags. Running Xenogenesis since late April, fantastic job! :good:
GrayHat137 said:
Yes, that's the consensus. Some I've asked, others are no longer in active development (nostalgia for holding onto these apps). I stumbled upon a web hit while googling for answers, the solution was about changing a simple setting in the android framework, but I'm a not experienced with ADB, and things like ODEXing and DeODEXing are nerve-wracking while I learn and experiment.
Also, thanks for coming sbdags. Running Xenogenesis since late April, fantastic job! :good:
Click to expand...
Click to collapse
Which part of the framework do you need to change?
sbdags said:
Which part of the framework do you need to change?
Click to expand...
Click to collapse
Navigate to the androidpolicy\com\android\internal\policy\impl folder and open PhoneWindowManager.smali in your favorite text editor (Notepad++ is my favorite)
Search for the method "rotationfororientation"
(Picture of code here)
Make note of the variables (v#) for portrait and landscape (in my case portrait is v5)
Scroll to the end of the method and you should find something like:
"move v2, v5" (make sure it's the last move command before the end of the method)
Change the second variable (in this case v5) to whatever orientation you wish to be default. In my case I have set portrait as the default orientation.
Click to expand...
Click to collapse
There are other steps, but this is the only variable changed. I can't post links yet, and I didn't want to copy all of the text there, but that's it. The attached picture is the picture of the code.
Eureka!
GrayHat137 said:
There are other steps, but this is the only variable changed. I can't post links yet, and I didn't want to copy all of the text there, but that's it. The attached picture is the picture of the code.
Click to expand...
Click to collapse
Dear friends,
As I was also facing the same problem in my Ubislate 7C+(EDGE) tab by DATAWIND. While reading your post an idea struck to my mind. With the help of Root Browser app I navigated to /system/build.prop, opened it in text editor and in "ADDITIONAL_BUILD_PROPERTIES" changed the value of "ro.sf.hwrotation=270" 270 to 180 saved it and rebooted the tablet. Yes! the problem was solved but it created a new problem that the orientation of animation while boot and camera orientation has changed now but in order to rectify it I pulled bootanimation.zip to my computer and after unzipping it changed the orientation of animation files from portrait to landscape. Changed the orientation in 'desc.txt' from 480 800 to 800 400 and zipped both without any compression. Pushed it back to /system/media and changed the permission, user,group to original one with the help of root browser. Then for camera orientation with the help of root browser I navigated to /system/etc/camera.cfg opened it in RB text editor and changed camera orientation from 90 to 0, saved it and rebooted my tablet and now all the games using gsensor tilt are working fine.
Thanks,:good:
rotation gyro off
I had the same problemen, i resolved it by going to setting, location and then status (only GPS) then i started GPS tools , just waited a min or so . now everthing is oké again.
I hope thuis helps you
Hi to all.
I've made a watchface with the stepcount % indicator.
This indicator was fine until it reach the 100%, but if you go over your daily objective the counter became unuseful (I don't know which value it exposes).
Someone else have experienced the same problem?
Thanks
GS
ITALY
PS: what about creating a new section dedicated to the Gear Watch Designe...?
Do you use the "steps counter" or "steps %" ?
For me, the % just stop when the number off steps are done, but when I put the counter, it continue until the end of the day.
Mikoube said:
Do you use the "steps counter" or "steps %" ?
For me, the % just stop when the number off steps are done, but when I put the counter, it continue until the end of the day.
Click to expand...
Click to collapse
The problem is another: I have associated a sequence of images to reproduce a toggle for the step count %.
The gauge is OK, but when I go over the 100% of the daily target, the gauge resets to the initial position and is looks like the 0% of the target.
I think this is a bug of the GWD...
GS
ITALY
Or maybe GWD don't see it as % meter, but count meter and after the defined count of steps, it just restart the count... the good thing to know is : Is it possible to record that reset to put another counter
Do you mean you used "Step Counter"?
jhonjey66 said:
Hi to all.
I've made a watchface with the stepcount % indicator.
This indicator was fine until it reach the 100%, but if you go over your daily objective the counter became unuseful (I don't know which value it exposes).
Someone else have experienced the same problem?
Thanks
GS
ITALY
PS: what about creating a new section dedicated to the Gear Watch Designe...?
Click to expand...
Click to collapse
Do you mean you used the "cumulativeTotalStepCount" of the Human Activity Monitor interface?
If yes, it will give you total steps since you last called "tizen.humanactivitymonitor.start(...)", Irrespective of any "daily objective".
API Reference - https://developer.tizen.org/dev-gui...izen/humanactivitymonitor.html#StepDifference
akhilkedia94 said:
Do you mean you used the "cumulativeTotalStepCount" of the Human Activity Monitor interface?
If yes, it will give you total steps since you last called "tizen.humanactivitymonitor.start(...)", Irrespective of any "daily objective".
API Reference - https://developer.tizen.org/dev-gui...izen/humanactivitymonitor.html#StepDifference
Click to expand...
Click to collapse
Thanks for the answer...
In any case, no, I used the GWD facility that allow to link a series of images to the stepcount %...
I attach an image in order to explain...
The problem is that the percentage seems to go over 100% but there is no option to link a further image when this condition happens...
GS
ITALY
jhonjey66 said:
Thanks for the answer...
In any case, no, I used the GWD facility that allow to link a series of images to the stepcount %...
I attach an image in order to explain...
The problem is that the percentage seems to go over 100% but there is no option to link a further image when this condition happens...
GS
ITALY
Click to expand...
Click to collapse
I have the same problem. i just want to show a simple image when goal reaches 100%
and it does. at 100% it shows. if i walk another stepp its 100.01% and it disappears...
the same here
dahod83 said:
the same here
Click to expand...
Click to collapse
Has anyone tried editing the XML by hand to put in a "ge" (greater than or equal to) operator?
kimvette said:
Has anyone tried editing the XML by hand to put in a "ge" (greater than or equal to) operator?
Click to expand...
Click to collapse
nope
Drbaldini said:
I have the same problem. i just want to show a simple image when goal reaches 100%
and it does. at 100% it shows. if i walk another stepp its 100.01% and it disappears...
Click to expand...
Click to collapse
Is that fixed with an update to GWD 1.0.2 ?
ThinkD said:
Is that fixed with an update to GWD 1.0.2 ?
Click to expand...
Click to collapse
it is at least it says so on release notes
http://developer.samsung.com/release-note/view.do?v=R000000030L
I do it with STEPS - not with %. That works fine! If the step goal is achieved appears a special image and this remains for the rest of the day.
[A530x][A730F]
SaboorROM
PLEASE READ ALL THIS BEFORE DOING ANYTHING
PLEASE KEEP IN MIND THAT THIS ROM IS NO LONGER IN DEVELOPMENT AND I WILL NOT BE ABLE TO HELP YOU WITH ISSUES, SORRY
________________________________________________
NOTICE:
I am not responsible for any happy endings, a nuclear war with your device, your alarm clock electrically shocking you, or your device literally freezing, so dont blame me for my mistakes or yours, or else i will laugh at you
Please backup your device (System, Data, EFS, and Cache, Especially EFS) because you might regret flashing this
________________________________________________
CREDITS:
@prashantp01 for Quantum Kernel
SuperR kitchen to build rom
________________________________________________
FEATURES:
Canada A530WVLU4CSCA base
Debloated
Deknoxed
Rooted
S10 Sounds and ringtones
Screen Recording (check section 2 on post #3 for more details)
build.prop tweaks
Status bar size options (check section 1 on post #3 for more details)
G975F/G975W ODM
ODM mods that add mobile data quick settings tiles etc
Applock
Call recording
Mobile data toggle in power menu
________________________________________________
BUGS:
Freezes on bootanimation and when playing video (sometimes) (i dont think there is with 4/23 build, someone test and tell me ASAP)
Digital wellbeing not showing stats (check section 3 on post #3 for workaround) (DIGITAL WELLBEING NOT AVAILABLE ON 4/23 BUILD I WILL ADD IT ON FUTURE BUILDS LOL I JUST FORGOT ABOUT DIGITAL WELLBEING)
Everything else works
________________________________________________
INSTRUCTIONS:
1. Download the ROM zip, and zip #2 for your model under this section
2. Boot into TWRP
3. Wipe system, cache, and data
4. Flash ROM zip
5. Flash zip #2
6. Boot and setup
7. done! (PLEASE READ THE BUGS BEFORE YOU GO TO THE COMMENTS AND SAY "sar why my phone freeze so much ur rom is stupid")
________________________________________________
DOWNLOAD
ITS BEEN 2 YEARS SINCE I'VE WORKED ON THIS ROM. THIS ROM IS CLEARLY NO LONGER BEING WORKED ON
________________________________________________
How to update from existing version of rom
1. Dont forget to download the zip #2 update too, that zip updates too!
2. Flash ROM zip
3. Flash zip #2
4. Wipe cache/dalvik
5. Wait for device to finish optimizing and updating before reporting any bugs
________________________________________________
XDA:DevDB Information
SaboorROM, ROM for the Samsung Galaxy A8 (2018)
Contributors
587.saboor
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Version Information
Status: Testing
Current Stable Version: 420-11:11AM
Stable Release Date: 2019-04-20
Current Beta Version: 4-23-6:50PM
Beta Release Date: 2019-04-23
Created 2019-04-15
Last Updated 2019-04-23
/////////////////////////////////////////////////////////////////
Click here to join us in the one and only A8/A8+ Telegram group
/////////////////////////////////////////////////////////////////
_____________________________________________
STATUS BAR SIZE
If you see the screenshot below, you'll see the status bar is a bit big (pls don't mind the blank settings page lol)
https://photos.app.goo.gl/wiYKVbJed52t9SiN6
DON'T PANIC BIG STATUS BAR HATERS! THIS IS ONLY OPTIONAL AND THIS EVEN HAS OPTION FOR SMALLER STATUS BAR
How do you get it, you ask?
just follow these steps after installing the rom
1. go to settings
2. developer options (u already know how to turn dev options on)
3. scroll down to "Simulate display with a cutout" and tap it
4. select a size of status bar (this wont add any notch on your phone, this only makes the status bar a bit bigger like on the screenshot)
5. done!
_____________________________________________
SCREEN RECORDER
You can record your screen with sound too
How do you get it, you ask?
just add it to the quick settings menu
_____________________________________________
DIGITAL WELLBEING FIX
Digital wellbeing doesn't show stats but you can make it show
How?
just follow these steps:
1. go to settings
2. search "Special Access"
3. press Special Access
4. scroll down to Usage data access and press it
5. press the 3 dot menu on the top right
6. press Show system apps
7. press Digital wellbeing and enable allow usage tracking
8. done!
_____________________________________________
SCREENSHOTS
https://photos.app.goo.gl/4USaY78w3cm8DG5p9
_____________________________________________
Reserved
..
So
Is this the final, final one? And, that new kernel that popped up in this section, shall I give that a go? I tried it with a Pie back up and that went into a real tight loop of maybe 2 seconds in between boots.
Anyway, thanks. I don't think I'll be doing the upgrade next week and this project is better than what I'd get, AND just saves time adding in extras.. No reason to pretty much downgrade (in my eyes) with the official. Hope that screen freeze gets worked out eventually so I can stop talking to my phone like a puppy when it boots.
k I see you added the kernel. No freezing on boot. Did a couple reboots but nothing weird.. Just got a nice Samsung logo display here and... yup. Welcome screen. Here we go.
Alright! Great work with the ROM and kernel addition. Still getting a bit of the freezes but not even close to as bad as it was a week ago. And if it freezes, it doesn't do it as the S or SA of Samsung starts. A little more crash friendly for the eyes. Really trying to like this update... but when you see the attached images it's almost like someone wants you to hate it. Once that panel fills out the screen there's 2 swipes to put it back, if you want to swipe. Speaking of progress, the stock weather app is coloured like you're not supposed to look at it.
mindlery said:
Is this the final, final one? And, that new kernel that popped up in this section, shall I give that a go? I tried it with a Pie back up and that went into a real tight loop of maybe 2 seconds in between boots.
Anyway, thanks. I don't think I'll be doing the upgrade next week and this project is better than what I'd get, AND just saves time adding in extras.. No reason to pretty much downgrade (in my eyes) with the official. Hope that screen freeze gets worked out eventually so I can stop talking to my phone like a puppy when it boots.
k I see you added the kernel. No freezing on boot. Did a couple reboots but nothing weird.. Just got a nice Samsung logo display here and... yup. Welcome screen. Here we go.
Alright! Great work with the ROM and kernel addition. Still getting a bit of the freezes but not even close to as bad as it was a week ago. And if it freezes, it doesn't do it as the S or SA of Samsung starts. A little more crash friendly for the eyes. Really trying to like this update... but when you see the attached images it's almost like someone wants you to hate it. Once that panel fills out the screen there's 2 swipes to put it back, if you want to swipe. Speaking of progress, the stock weather app is coloured like you're not supposed to look at it.
Click to expand...
Click to collapse
lol there's still a long way to go with this rom, this isnt final
the only way the screen freeze will get worked out is we wait for official pie to come out for a530w and see lol
ye i kinda hate the fact that it fills up the screen and how it wastes space, but you get used to it, the thing i hate the most is the brightness slider location, its the very bottom and i prefer it to be on the top
587.saboor said:
the thing i hate the most is the brightness slider location, its the very bottom and i prefer it to be on the top
Click to expand...
Click to collapse
Yeah what's up with that? I am wondering if there's something bigger in the making because it seems like this is not a complete OS.
Reminds me of getting a new Playstation and EA Sports makes hockey suck again and each year adds in the things they already had from the beginning so you buy it each year. But not with 2 thousand dollar price tags.
No matter what phone, i will not be on an unaltered OS for a while. I got a friend of mine to upgrade one of her S9+ phones and it kinda works for the bigger screen but still crud. Crud on speed. Keep on cookin'!
Battery life good, I think this rom smoother than the stock. Maybe you can add more custom content like that ringtones. Can you add tweak to change screen resolution like in the samsung flagship phone too? To preserve battery life. Great rom it is my daily driver. :good:
mindlery said:
Yeah what's up with that? I am wondering if there's something bigger in the making because it seems like this is not a complete OS.
Reminds me of getting a new Playstation and EA Sports makes hockey suck again and each year adds in the things they already had from the beginning so you buy it each year. But not with 2 thousand dollar price tags.
No matter what phone, i will not be on an unaltered OS for a while. I got a friend of mine to upgrade one of her S9+ phones and it kinda works for the bigger screen but still crud. Crud on speed. Keep on cookin'!
Click to expand...
Click to collapse
yep oneui literally was only here for like idk 3 months so it still needs some improvement
Slightly. The latest, or the one i downloaded last night hasn't had any freezes/reboots yet. Haven't cut out any apps yet but installed a few Magisk modules and usually would have had an issue at boot by now.
The brightness slider can be applied up top but it's bulky... of course.
mindlery said:
Slightly. The latest, or the one i downloaded last night hasn't had any freezes/reboots yet. Haven't cut out any apps yet but installed a few Magisk modules and usually would have had an issue at boot by now.
The brightness slider can be applied up top but it's bulky... of course.
Click to expand...
Click to collapse
lol im starting to think that ur the only one who uses this rom
mindlery said:
Slightly. The latest, or the one i downloaded last night hasn't had any freezes/reboots yet. Haven't cut out any apps yet but installed a few Magisk modules and usually would have had an issue at boot by now.
The brightness slider can be applied up top but it's bulky... of course.
Click to expand...
Click to collapse
Try YouTube that is where you can get freezes.
mchlbenner said:
Try YouTube that is where you can get freezes.
Click to expand...
Click to collapse
lol youtube is like the app where i get the least freezes, instagram or snapchat has more freezes
Hello everyone
Thanks for the effort made
I tried the image for a week
I've had blocks more than once
in addition, the features of the apps are very small
atilla20 said:
I've had blocks more than once
Click to expand...
Click to collapse
did you read the bugs?
587.saboor said:
did you read the bugs?
Click to expand...
Click to collapse
could you explain to me what to do please
atilla20 said:
could you explain to me what to do please
Click to expand...
Click to collapse
no, there's no way to fix it yet so deal with it
atilla20 said:
could you explain to me what to do please
Click to expand...
Click to collapse
Samsung released a buggy Android pie update so until they fix it all pie will have issues.
Yeah i haven't tried any video yet but i am prepared for that to freeze and this is an excellent version as far as an unfinished ROM goes. I didn't flash the module to maintain bluetooth in my vehicle either as of yet, but once again that functions flawlessly if i just accept the pop-up when starting my car. Not a major concern. What's vastly improved and most important is when re-booting it will not freeze at the Samsung logo if installing a module or for any reason... as of yet and hopefully always. Going to purge some apps now and let you know how that goes. Also, for anyone that wants, you can add camera shutter toggle, call recording and remove the security menu from the battery health section (not an uninstall but just omitted).
Here's the 3 entries for the cscfeature.xml described above that are working: I am getting spaces when i post so make sure to fix it.
<CscFeature_Camera_ShutterSoundMenu>TRUE</CscFeature_Camera_ShutterSoundMenu>
<CscFeature_SmartManager_DisableAntiMalware>TRUE</CscFeature_SmartManager_DisableAntiMalware>
<CscFeature_VoiceCall_ConfigRecording>RecordingAllowed</CscFeature_VoiceCall_ConfigRecording>
Most of you probably have them already but it's easier copying and pasting if you don't Be careful as there is a space in the code for some reason.
Also, not really anything required, but you can have a data on your power off menu and take out the auto-spacing in your dial pad entry. These should already be there and only require changing "FALSE" to "TRUE"
<CscFeature_Common_DisablePhoneNumberFormatting>TRUE</CscFeature_Common_DisablePhoneNumberFormatting>
<CscFeature_Framework_SupportDataModeSwitchGlobalAction>TRUE</CscFeature_Framework_SupportDataModeSwitchGlobalAction>
Nothing new, but working if you want them. Still trying to get blank texta but I think it's not able to be tweaked anymore. Not from the mentioned file.
So I damaged my phone screen and got a non-original screen as a replacement. The new screen-space is not as tall and so the top part of the status bar is getting cropped off. Is there a way for me to fix this? Probably something that could decrease the screen space my ROM is using by a few pixels?
Wich phone model and software version are you running ?
You may try changin the dpi to make it fit in , some phones have it inside the developer settings
ThatLatinGuy said:
Wich phone model and software version are you running ?
You may try changin the dpi to make it fit in , some phones have it inside the developer settings
Click to expand...
Click to collapse
I am using an Asus Zenfone Max Pro M1. Android 12 EvolutionX ROM. I will try searching the Developer Options.
EDIT: I did mess up my device and get it into a boot loop by trying to change the display cutout. It's fixed now. But yeah I couldn't find a relevant option. Would be really great if you could give me a bit more precise solution.
The system component that draws the statusbar is SystemUI.apk and, inside it, you will find the images (all the "/res/drawable/sec_stat_sys_*.spr" files) and several XML files that coordinate the overall layout.
xXx yYy said:
The system component that draws the statusbar is SystemUI.apk and, inside it, you will find the images (all the "/res/drawable/sec_stat_sys_*.spr" files) and several XML files that coordinate the overall layout.
Click to expand...
Click to collapse
I sort of understand what you're saying but this would mean some experimentation and since I don't have a backup device. I don't think with my present schedule I'll be able to spend time experimenting with it. Can you provide some more precise help? Is there no option to tweak things?