Related
I've created an app that does what "socket84" was talking here on the forum ( http://forum.xda-developers.com/showthread.php?t=734151 ), which basically is a way to change the default home screen when the user presses the Home button. This works with a hidden setting from TouchWiz. I posted it on Market with the name "SGS Screen Changer".
NOTE: You'll ROOT and BusyBox for the app to be able to do it's work.
http://www.cyrket.com/p/android/com.pedronveloso.samsunghsc/
I've only tested it with the European, Samsung Galaxy S so far.
I've tested with various different firmwares ( JM2, JG5, JM6, JM7 and JM8 ) and it's working ok. Also I've coded a backup mechanism in case things don't work as expected, and later you can restore the file to it's initial state, from the the restore button within the app, or manually by issuing the command "cp /system/default.propBackup /system/default.prop", but verify first that you have the backup file.
> Doesn't work on Froyo yet! The configuration files have changed in those releases, and I've not fixed it yet.
Also, it would be great if people could post the contents of their "/system/default.prop" file in here, along with their firmware number, so I can fix it for different non functioning firmwares. Thanks
Let me know if you've any questions, and all feedback it's appreciated. Also remember this is the first public version, so don't expect it to look pretty, I've focused on functionality and correctness first.
Change-log:
Beta 2 ( 20-08-2010) :
* Bugfixes
* Fixed screen numbering as reported by Limality ( thanks )
Beta 1 ( 18-8-2010 ) : First release
IMPORTANT NOTE: Everyone who had installed the first beta should update it from the Market and set the screen to whichever they want, even if the app did work to them before. People who said it wasn't working, and the ones who said it didn't leave the 4th screen should update and select the screen they want and reboot. All those problems should be fixed in this release. I'll be waiting for further feedback on those ones to confirm if this solved their problems
pedrodh said:
I've created an app that does what "socket89" was talking here on the forum ( http://forum.xda-developers.com/showthread.php?t=734151 ), which basically is a way to change the default home screen when the user presses the Home button. This works with a hidden setting from TouchWiz. I posted it on Market with the name "SGS Screen Changer".
NOTE: You'll ROOT and BusyBox for the app to be able to do it's work.
http://www.cyrket.com/p/android/com.pedronveloso.samsunghsc/
I've only tested it with the European, Samsung Galaxy S so far, but I'm guessing it will work on the American version as well, but I would apreciate feedback on that.
I've tested with two different firmwares ( JM2 and JG5 ) and it's working ok, but I'll probably work for every new firmware out there. Also I've coded a backup mechanism in case things don't work as expected, and later you can restore the file to it's initial state, from the the restore button within the app.
Let me know if you've any questions, and all feedback it's appreciated. Also remember this is the first public version, so don't expect it to look pretty, I've focused on functionality and correctness first.
Click to expand...
Click to collapse
tested! working. great job. dont need any nice UI. this will do
tested with rooted JM5.
not configurable. always get me to screen 4 despite setting it to screen 3 or so on.
"Restore to original settings" doesn't work after reboot it's still screen 4.
Any ideas?
Note: screen 4 is only good for 7-screens SGS. since I've 5 screens I want to make default screen 3
thanks in advance!
Sweet, thanks for this, will give it a ry now
truemagic said:
tested with rooted JM5.
not configurable. always get me to screen 4 despite setting it to screen 3 or so on.
"Restore to original settings" doesn't work after reboot it's still screen 4.
Any ideas?
Note: screen 4 is only good for 7-screens SGS. since I've 5 screens I want to make default screen 3
thanks in advance!
Click to expand...
Click to collapse
the settings to set the homescreen starts at 0 meaning that:
0 = Homescreen 1
1 = Homescreen 2
2 = Homescreen 3
3 = Homescreen 4
4 = Homescreen 5
etc...
Not working here on JG4 Aussie firmware
Limality said:
the settings to set the homescreen starts at 0 meaning that:
0 = Homescreen 1
1 = Homescreen 2
2 = Homescreen 3
3 = Homescreen 4
4 = Homescreen 5
etc...
Click to expand...
Click to collapse
Regardless what I set (tried homescreen 1,2,3,4..) still when pressing "HOME" button it takes me to screen 4...
nice app!
might wanna just add 1 to all the screen numbers just so everyone gets it .
starting at 0 while the numbers shown in touchwiz are starting at 1, is kinda weird
\
so screen 0 = 1 and screen 1 = 2
edit: hmm not working here either on JM5 always gives the last screen as home screen, if i do it myself it works..
Not work with DXJG4
Maybe "One click lag fix 2.3" could be a cause ?
tommy34 said:
edit: hmm not working here either on JM5 always gives the last screen as home screen, if i do it myself it works..
Click to expand...
Click to collapse
cool....mind to share how did you "do it yourself"?
thanks~
truemagic said:
cool....mind to share how did you "do it yourself"?
thanks~
Click to expand...
Click to collapse
here : http://forum.xda-developers.com/showthread.php?t=734151
Thanks for everyone that tested it, your feedback it's apreciated .
Not work with DXJG4
Maybe "One click lag fix 2.3" could be a cause ?
Click to expand...
Click to collapse
No, I've lagfix myself and I'm using MoDaCo ROM and it worked. Did you reboot after setting it? You must reboot for changes to take effect.
the settings to set the homescreen starts at 0 meaning that:
0 = Homescreen 1
1 = Homescreen 2
2 = Homescreen 3
3 = Homescreen 4
4 = Homescreen 5
Click to expand...
Click to collapse
That's easely fixed, I really though it was otherwise because on mine it worked. I'll retest. Humm..Could be that some fimrwares accept 1 as first and others as 0 ? Has more people post I'll find it out. Thanks for reporting that
"Restore to original settings" doesn't work after reboot it's still screen 4
Click to expand...
Click to collapse
The backup it's stored in /system/default.propBackup , you just have to do "cp default.propBackup default.prop" in some terminal as root in case to restore it manually, if the restore button fail's to do it's job.
work's perfectly on my JG5, thank you Pedrodh!
Sent from my GT-I9000 using XDA App
work's perfectly on my JG5, thank you Pedrodh!
Click to expand...
Click to collapse
Nice to know . By the way, you have BusyBox installed from the Market, or you had it bundled with your ROM ?
IIRC, some firmwares (i.e. DXJG4) have a different /system/default.prop and hence will not work.. Cant change manually either
I have installed busybox 1.17.0 when i put mimocan fix
IIRC, some firmwares (i.e. DXJG4) have a different /system/default.prop and hence will not work.. Cant change manually either
Click to expand...
Click to collapse
Would be useful to have the data regarding which firmwares work, and which doesn't. If I did I could check it while executing the app and notify the user properly. Also, I'm in doubt if people who install busybox from the market have a different setup from the ones who doesn't. I'm issuing the linux commands like "echo" , but if the busybox from the market doesn't update the system Path I'll have to pass the entire path when issuing the command. I'll be waiting for more feedback from the users and begin sorting this out.
So far it seems that everyone who has MoDaCo and/or JG5 has been able to use this.
OK, updated the app. I found out what was wrong, should now be fixed.
IMPORTANT NOTE: Everyone should update it from the Market and set the screen to whichever they want, even if the app did work to them before. People who said it wasn't working, and the ones who said it didn't leave the 4th screen should update and select the screen they want and reboot. All problems should be fixed in this release. I'll be waiting for further feedback on those ones to know if it solver their problems
Wish I could test it for you, but currently my phone is bricked.
Default screen is maybe the only option I am missing in TW.
However when I tried this hack in JPJG8 it didn't work, so if your app is just editing the /system/default.prop file, most chances are it won't work either.
Ok, I got a report that the fix did in fact work.
I was developing on another T3 device and come across some things that might come in handy for the one x specifically build.prop.
Within build.prop I found this:
debug.nfc.fw_download : Currently set to false but can be enabled by setting to true
debug.nfc.se: Set to false, debugging, to do with tegra3 built in security engine (se)
media.tegra.max.out.channels: ?
mediea.tegra.out.channel.map: ?
net.qtaguid_enabled = 1/0, self explanatory
persist.sys.NV_FPSLIMIT = 35 (change to 60, for 60fps ui?)
persist.sys.NV_POWERMODE = 1
persist.sys.NV_PROFVER = 15
persist.sys.NV_STEREOCTRL = 0
persist.sys.NV_STEREOSEPCHG = 0
persist.sys.NV_STEREOSEP = 20
persist.sys.ui.hw = true (hw accelerated UI(Should already be set to true on ICS))
persist.tegra.NV_FPSLIMIT = 0 ? (unsure why there's 2 of them)
persist.tegra.nvmmlite = 1 (Unsure)
power.saving.mode = 0
ro.bootmode [unknown]
ro.factorytest = 0
ro.bootloader [unknown]
Persist.sys.fw.camera.status = 1
Persist.dmesg.mode = split
Persist.dmesg.rotate = 1
Drm.service.enabled = 1/0
Enjoy
shaky156 said:
persist.tegra.nvmmlite = 1 (Unsure)
Click to expand...
Click to collapse
Just so you know, changing this to 0 breaks the camera. No idea what it actually does though
I added everything else in your first post to my build.prop and all that seemed to change was that my quadrant score dropped by about 700 (4900 or so, to 4200). Actual phone speed didn't seem to drop, but I'll have a play around with them some more and see what happens
Improvements ?
Hi,
Thanks for the information.
Could you please let us know what are the improvements we can expect after this.??
Regards,
mahesh_9j said:
Hi,
Thanks for the information.
Could you please let us know what are the improvements we can expect after this.??
Regards,
Click to expand...
Click to collapse
I havent tested modifying those, i cant test them lol, but changing fps limit should change ui fps, afaik its currently set to 35fps
Changing nvpowermode to 0 might stop the lower freq clks when batterys lower
Sent from my Desire HD
shaky156 said:
I havent tested modifying those, i cant test them lol, but changing fps limit should change ui fps, afaik its currently set to 35fps
Changing nvpowermode to 0 might stop the lower freq clks when batterys lower
Sent from my Desire HD
Click to expand...
Click to collapse
The "persist.says.NV_FPSLIMIT" works nicely! Set it to 10 or so to make the UI almost unusable! Only works for the phone UI though, doesn't alter application fps.
Not sure how to measure how fast it can go though.
Sent from my HTC One X using xda premium
Meltus said:
The "persist.says.NV_FPSLIMIT" works nicely! Set it to 10 or so to make the UI almost unusable! Only works for the phone UI though, doesn't alter application fps.
Not sure how to measure how fast it can go though.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Best to set it to 60
Sent from my Desire HD
shaky156 said:
Best to set it to 60
Sent from my Desire HD
Click to expand...
Click to collapse
Is it already in HOX's build.prop or should we just add the lines that we want?
mach0boi said:
Is it already in HOX's build.prop or should we just add the lines that we want?
Click to expand...
Click to collapse
It's already in build.prop, just search and edit the value to 60.
double_ofour said:
It's already in build.prop, just search and edit the value to 60.
Click to expand...
Click to collapse
Naduduling na ko.
Tried and tried still can't find it. There's only a few lines in here that starts with "persist.". BTW, i'm on insertcoin.
mach0boi said:
Naduduling na ko.
Tried and tried still can't find it. There's only a few lines in here that starts with "persist.". BTW, i'm on insertcoin.
Click to expand...
Click to collapse
If its not there
Add it in, im sure all chefs will add it in when updating their roms
Sent from my Desire HD
shaky156 said:
If its not there
Add it in, im sure all chefs will add it in when updating their roms
Sent from my Desire HD
Click to expand...
Click to collapse
Already did. IDK if it's a placebo or have a real effect on the UI. Well i guess having it in here won't hurt
mach0boi said:
Already did. IDK if it's a placebo or have a real effect on the UI. Well i guess having it in here won't hurt
Click to expand...
Click to collapse
Few post above youra, Meltus tested the nvfpslimit, it works
Sent from my Desire HD
mach0boi said:
Already did. IDK if it's a placebo or have a real effect on the UI. Well i guess having it in here won't hurt
Click to expand...
Click to collapse
Have you tried lowering the value down? lets say like 10 if it slows down the UI? if not then maybe that line has no effect at all..
s-off ka pre? ineedit mo directly sa /system/? hehe.. or paflash2 ng script sa recovery?
shaky156 said:
Few post above youra, Meltus tested the nvfpslimit, it works
Sent from my Desire HD
Click to expand...
Click to collapse
well.. that answers our question.
double_ofour said:
Have you tried lowering the value down? lets say like 10 if it slows down the UI? if not then maybe that line has no effect at all..
s-off ka pre? ineedit mo directly sa /system/? hehe.. or paflash2 ng script sa recovery?
Click to expand...
Click to collapse
PM
10 chars
Ill update this soon
Sent from my Desire HD
mach0boi said:
Naduduling na ko.
Tried and tried still can't find it. There's only a few lines in here that starts with "persist.". BTW, i'm on insertcoin.
Click to expand...
Click to collapse
to search use terminal app... then type the command
getprop | grep "thing to search"
or if you're sure of the exact key and just want to check the value use
getprop "exact.key"
double_ofour said:
It's already in build.prop, just search and edit the value to 60.
Click to expand...
Click to collapse
Consider the fact that upping UI FPS from 30 to 60 doubles the GPU workload and results in battery hit.
this value definitely works in controlling the launcher FPS
persist.sys.NV_FPSLIMIT = 60
however the line is not there by default, so it might be already 60fps default
placing the file with low value will cap the FPS
Shaky any idea how to force Tegra full quad performance mode?
hamdir said:
this value definitely works in controlling the launcher FPS
persist.sys.NV_FPSLIMIT = 60
however the line is not there by default, so it might be already 60fps default
placing the file with low value will cap the FPS
Shaky any idea how to force Tegra full quad performance mode?
Click to expand...
Click to collapse
Might have an idea, ill let you know once im abit more free
Sent from my HTC Desire HD
I have 2.3.4 and sense 2.1. Everything works fine except the lock screen is very unresponsive. I literally have to punch the screen with my finger a few times before it wakes up. I was wondering if the newer versions of sense fix the lock screen?
I have the same problem from time to time. Restarting my phone normally sorts it out.
I wish that was my answer but Its not. At least not for me.
Others have found this post useful and it seems it is similar to your issue. ;-)
I've tried that several times. Infact it helped me calibrate my touch screen after I broke the original. I've honestly had the same issue even with the original screen.
Cataulin said:
I have 2.3.4 and sense 2.1. Everything works fine except the lock screen is very unresponsive. I literally have to punch the screen with my finger a few times before it wakes up. I was wondering if the newer versions of sense fix the lock screen?
Click to expand...
Click to collapse
If you aren't adamant about Sense, you could try flashing a Sense-less ROM. In my experience, it improves much on performance.
When i bought my WildfireS i had the same problem , stock came with 2.3.3 . But when i updated to the official 2.3.5 problem solved. U Can try different rom also .
Sent from my Wildfire S using XDA
sorry for taking so long to get back to you guys.
I've got a VM Wildfire S thats CDMA and well.....None of the other roms seem to work. I;ve tried Wildchild but its not picking up my service. Simonsense3.5 seems to be okay but things like music crash every now and again. I do still have the unresponsive screen issue but its not as bad with simonsense. I do seem to have a deadzone on my screen for the I key. Specificly the I key. if I switch into that horrible swipe the screen does not track any inputs exactly on or bordering that specific letter. Anyway I can fix that?
Also what else should I be doing now that i've been able to get this phone in a better rom?
Set the minimum overclock limit in No frills to something lieke 245 Mhz or above until it solves.
It worked for me when I used sense roms.
Hope it helped..
Try editing your build.prop
With the touch responsive tweak.
It worked for me
Sent from my HTC_A510c using XDA
cpie20 said:
Try editing your build.prop
With the touch responsive tweak.
It worked for me
Sent from my HTC_A510c using XDA
Click to expand...
Click to collapse
And which tweak are we talking about here? My lockscreen gets quite unresponsive as well. Tried reverting to the slide lockscreen off earlier versions but didn't help either. Tried the solution mentioned on the other thread (Post#4) and neither did that. I have a hunch it has something to do with the sensor, atleast on mine. I've noticed it acts crazy especially under low-light areas, or say if it had been in my pocket for ages. Ah well, hoping to find a solution soon.
spit_fire said:
And which tweak are we talking about here? My lockscreen gets quite unresponsive as well. Tried reverting to the slide lockscreen off earlier versions but didn't help either. Tried the solution mentioned on the other thread (Post#4) and neither did that. I have a hunch it has something to do with the sensor, atleast on mine. I've noticed it acts crazy especially under low-light areas, or say if it had been in my pocket for ages. Ah well, hoping to find a solution soon.
Click to expand...
Click to collapse
This worked for me.
#Helps Scrolling Responsiveness windowsmgr. .performance.tuning=1 Video.accelerate.hw=1
Sent from my HTC_A510c using XDA
spit_fire said:
And which tweak are we talking about here? My lockscreen gets quite unresponsive as well. Tried reverting to the slide lockscreen off earlier versions but didn't help either. Tried the solution mentioned on the other thread (Post#4) and neither did that. I have a hunch it has something to do with the sensor, atleast on mine. I've noticed it acts crazy especially under low-light areas, or say if it had been in my pocket for ages. Ah well, hoping to find a solution soon.
Click to expand...
Click to collapse
Did you try turning off Settings -> Sound -> Quiet ring on pickup & Pocket mode & Flip for speaker?
As cpie20 also stated you can try doing the following to your build.prop to help speed things up.
CHANGE:
Code:
view.touch_slop = 2
ADD:
Code:
# Force Launcher into Memory
ro.HOME_APP_ADJ = 1
# Enable Graphic Processor Unit
debug.sf.hw = 1
# Improve Overall Touch Responsiveness
debug.performance.tuning = 1
video.accelerate.hw = 1
# Improve Scrolling Responsiveness
windowsmgr.max_events_per_sec = 150
Thanks for that. I did switch off the Sound settings as you mentioned earlier. Apart from that, I noticed that most of the tweaks were already present on the build.prop I'm currently running on. Just changed the following:
Code:
view.touch_slop = 2 [COLOR="Red"](Was 15)[/COLOR]
# Force Launcher into Memory
ro.HOME_APP_ADJ = 1 [COLOR="red"](Wasn't there)[/COLOR]
# Improve Scrolling Responsiveness
windowsmgr.max_events_per_sec = 150 [COLOR="red"](Was set on 120)[/COLOR]
So yeah, will see how that helps and report back later.
EDIT: Seems to work great upto now. The build.prop tweaks seem to have finally fixed it. Will report back if I head into any issues but seem quite unlikely.
help
Sorry but I didn't know where to add the other code
so I have to add them at the end ... or after the code:
view.touch_slop = 2
& with thanks and respect
Hi,
is there any way to change brightness to lower level? My previous phone, Xperia Mini, could decrease brightness to absolute black (I didn't need it, but still...). But my Xperia M is still pretty shining in dark even in the lowest level. It burns my eyes. All I could find were some stupid filters. Is there any better solution (root or not, I don't care).
Thanks.
dave_lister said:
Hi,
is there any way to change brightness to lower level? My previous phone, Xperia Mini, could decrease brightness to absolute black (I didn't need it, but still...). But my Xperia M is still pretty shining in dark even in the lowest level. It burns my eyes. All I could find were some stupid filters. Is there any better solution (root or not, I don't care).
Thanks.
Click to expand...
Click to collapse
Click
Gravitybox has some brightness abilities to reassign lux-brightness pairs. Don't know if it can go under normal brightness though...
FindYanot: That's exactly what I don't want. I want something on HW level (lower led (or what they use) intensity), not just transparent black layer.
KoenGo: Do you think, it can work? I don't have root yet (I want do it, if I find solution), so I can't try.
Nobody faced this problem? Everyone is happy with light intensity?
Yes it's too much but if you lower that level screen will probably start flickering which is much more annoying than just too bright screen. This is common, hw related issue that can be found on other devices with low quality lcd.
I'm trying but it's kinda hard to tell if there's any difference since you have to reboot after applying new minimum. I would say there isn't much difference. I'll retry in the dark some time.
Doesn't crash or flicker or anything though, so that's the good news
Personally, I would not root just for this and just use the filters. What is your problem with them? That it uses more battery than a hardware method would, or just that it's impractical? In the second case, lux might be worth looking into. I've never tried it myself since it isn't free, I just use the filter u hate
Tried it in the dark and I believe there is a difference, although very small (barely noticeable) and imho definitely not worth rooting and installing framework.
OK. That's bad, but thanks for your time
Well I rooted my phone and I tried gravitybox and I don't think there is a difference. But still thanks.
My setup now is that I can (de)activate the filter app by swiping over the navigationbar. It's still a filter so it doesn't prolong battery life or anything, but it is a convenient way to enable or disable it.
If you would ever come across something better, please let us know
dave_lister said:
is there any way to change brightness to lower level?
Click to expand...
Click to collapse
Yes, but you need root.
Execute in Terminal or run attached file as script via Root Explorer / GScript:
Code:
#!/system/bin/sh
su
echo 5 > /sys/class/leds/wled/brightness
Minimal stock value 27, we change it to 5 or any other you want.
Maximum value: 255
Bug: backlight will be flickering.
Thank you. It really works! (I rewrite it manually without any script or terminal)
Just one thing. The brightness file is used for current state and when I change intensity in options (or select auto), it's rewritten. So, is there any way to change minimum level permanently (minimum on bar or 0 lux = 5 or something instead of stock 27)? Or is it possible to make some shortcut to rewrite the file with one click? Or use some tasker for it?
But it doesn't matter much. Even this way, without any shortcuts, is awesome. I'll test it in night, but even now (during a day), I can see a difference.
dave_lister said:
So, is there any way to change minimum level permanently
Click to expand...
Click to collapse
Yes, but only by editing file in kernel, it requires recompiling.
Then pulled slider to the left will set really minimal value.
Here commit from ElixER kernel for 4.1.2, originally this trick comes from there.
dave_lister said:
Or is it possible to make some shortcut to rewrite the file with one click? Or use some tasker for it?
Click to expand...
Click to collapse
Yes, GScript app, as far I know can create shortcuts.
Or in Tasker create task with only one action "Run shell" (tick Root) and then create shortcut in launcher.
iks8 said:
screen will probably start flickering which is much more annoying than just too bright screen. This is common, hw related issue that can be found on other devices with low quality lcd.
Click to expand...
Click to collapse
Always was interesting what exactly causing this flickering at hardware side. Led's controller?
Please can you provide any information and example devices with same issue?
Bonoboo said:
Always was interesting what exactly causing this flickering at hardware side. Led's controller?
Please can you provide any information and example devices with same issue?
Click to expand...
Click to collapse
For example galaxy tab 2 (I have one), on the lowest brightnes level it flicker a lot (especially annoying when it's displays white surface), my sister's asus memo pad 7 hd has this issue too but less noticible. Yes, it's somehow related to device's power managment, in galaxy tab 2 forum people saies that it's flicers more when wifi signal is low so as I understand: low signal -> device need more power for wifi -> device gives less power for leds -> screen is more flickering but I could be wrong since I'm almost total electroinc noob I will test that later
p.s.
This issue is really common, even s4 has this problem according to this https://www.youtube.com/watch?v=5yZaQRr76f8 So Sony has done good move with setting so high the lowest brightnes level (at least this hides unusable levels). Really my eyes hurt when I'm using my gtab2 at night although xperia does the same thing but in different way xD
Tested your method and at least in my device, the LED flickering was barely noticeable and only appeared when I set very low values (like 1). Setting as 3 and onwards gives zero flickering here (or I'm just blind, not noticing it)...
You're right. Values about 3, 4, 5 are quite ok.
I made the GSscript shortcut and I¨m finally happy.
I think the flickering is caused by pwr regulation with low frequency. But I'm not electrician either.
Hi,
I'm using Bliss-v14.10-x86_64-OFFICIAL-opengapps-20230201 on a Dell optiplex 7050 micro with 16gb RAM and a Dell 2418HT touch screen monitor.
Video in apps is corrupted with green and black bars. The video plays smoothly but the entire screen is covered with thin alternating green/black bars.
I can play video fine with firefox/via etc.
I have tried many kernel parameters, such as
video=1920x1080, other valid resolutions
video=HDMI-1:d video=1920x1080, other valid resolutions
video=vga
vga=hex codes/decimal
vga=ask
nomodeset
xforcevesa
nomodeset xforcevesa
uc_mode=vesa (i believe that was it)
i've tried using the vga output instead of hdmi, with all the same parameters
If I choose a valid resolution below 1920x1080, the console seems to change resolution while booting but Bliss never changes, it's always 1920x1080.
The issue seems to persist in Bliss 15.8.4, and across gapps and foss versions. (edited: had Bliss 16 instead of 15)
Here is a screenshot that was taken in an app called Devinfo. Thank you to anyone who can help.
switch gralloc to something else like
Code:
GRALLOC=minigbm HWC=drm_minigbm
on kernel parameter.
HMTheBoy154 said:
switch gralloc to something else...
Click to expand...
Click to collapse
Thank you very much. Everything is working great now.
When I tried both parameters the green and black bars would blink.
When I tried just GRALLOC=minigbm by itself the green/black bars disappeared and everything is fine.
twolittlepennies said:
When I tried both parameters the green and black bars would blink.
Click to expand...
Click to collapse
I don't understand, can you explain ?
HMTheBoy154 said:
I don't understand, can you explain ?
Click to expand...
Click to collapse
I'm unable to replicate what happened. The green and black bars were no longer static but now flashed on and off like on a switch, which is the first and only time it ever happened.
I'm sure I did something wrong.
Everything works great, and I'm (now) using both of the parameters you provided. Thanks again.
And thanks to everyone who worked so hard to bring Android to PC.
twolittlepennies said:
I'm unable to replicate what happened. The green and black bars were no longer static but now flashed on and off like on a switch, which is the first and only time it ever happened.
I'm sure I did something wrong.
Everything works great, and I'm (now) using both of the parameters you provided. Thanks again.
And thanks to everyone who worked so hard to bring Android to PC.
Click to expand...
Click to collapse
Hi, please can You write out the steps, on how to fix that issue. Where do I input aforementioned commands and so on.
Please, for the love of god, someone guide me this ****fest. I NEED to fix the exact same issue. Ive been siting here for hours and hours trying to find out how the F* can I modify the system property You guys are talking about. My brain is melting.
Boot the device, when you see the boot selection screen hit 'e' to edit the boot parameters.
on the second line after 'quiet' put the following
'GRALLOC=minigbm' 'HWC=drm_minigbm'
then hit f10 to boot and see if it fixed it.
if it did, you can make it permanent by (in my case) doing the following
boot back to the boot selection screen and pick debug to boot
after it boots, type
mkdir /mnt/hd
mount /dev/sda1 /mnt/hd
vi /mnt/hd/EFI/Android/android.cfg
hit 'i' to be able to make changes
go to almost the bottom and look for "Create Main Menu"
on the first entry, after quiet, enter GRALLOC=minigbm HWC=drm_minigbm
hit escape
hold shift and type :
then type wq and hit enter
vi should save and quit
type
umount /dev/sda1
then reboot
this is what I did in my case, there is probably a better way. I'm using Bliss 15.8.4 on bare metal.