I'm in the middle of porting CWM 6.0.0.x to dell devices, and I've gotten all but one.
Background:
CWM 6.0 prefers displays of type:
24/32bpp color Edit: after fiddling around with it, this isnt actually true.
Right side up
Double buffered(?)
My last device I'm having trouble with (Dell Streak 5):
16bpp
Upside down
Single buffered(?)
I've re-added screen flipping (for point 2) and fixed the pixels for point 1, but I have no idea how to fix point 3.
My exact issue: I can get CWM 6.0 to boot with correct colors on my S5, but every other buffer(?) is blank.
So blank -> correct screen -> blank -> correct screen -> etc.
It's just a graphics issue as it still works fine while black.
CWM 5.5 preferred single buffers but had board config switches to enable RGBX_8888 and double buffering.
But the move to 6.0 broke RGB_565 and single buffering.
I have no idea where in the code to force it to single buffer, I've already fiddled around in <CWM>\minui\graphics.c and besides the color-space changes, there's nothing changed regarding single/double buffering in it.
Here's my device tree if it helps:
DellInc._Streak_120718.rar
Related
The new FPse update is not as smooth a prcoess to update as usual, since you have to either disable your previous settings or clear data out to get the virtual controls to show up.
Another issue is the scaling options are gone, so I can not figure out how to adjust the display. It supposed to be able to be adjusted, but I have yet to figure it out. Everything is distorted full screen now on my Droid 3, Flyer and Thrive. I try to adjust it, but now controls show up. Tried pinch and zooom, in case that was it. Since not working on three devices, seems it is the app rather than the user..... Ok, it could be the user, but no luck on three devices.
Anybody figure it out? Scaled display is better, since no distortion and less pixels for the emulator to draw to (it is faster when scaled).
Hi folks,
I jumped on the 8.1 bandwagon and for most things are good. I do get constant hanging of my Bluetooth and Wifi, sometimes even a crash. But all in all, its okay and manageable.
I have another question about the display. When you click, Change PC Settings-> PC and Devices -> Display -> More options and choose Smaller, the screen becomes a thing of beauty. Its the only feature still keeping me.
BUT....the darn thing never remembers it. I constantly (out of nowhere) find myself in the Normal option. Its really annoying. Has anyone seen this bug or can help?
Uh... the DPI settings ("Display- > More options -> Smaller" that you mention) have been present in Windows for years. It's not even new to Win8, much less to 8.1. Surface Pro is unusual among Windows systems in that it intentionally ships with a lowered DPI in order to make the screen readable to people with bad eyesight, but if you set it to "smaller" (100%), then you get the full 1920x1080 logical pixels. By the way, the easiest way to find it is just open Start and type "dpi" (although on Win8 you'll have to look under Settings in search results). Navigating menus and such sucks. Learn the Start search; you'll save a lot of time.
As for the unexpected reverting, that's just a bug. Congrats, you're running pre-release software! Have you reported it to MS yet (or hit +1 for the existing bug report, if there is one)?
I think what he's referring to is how many Metro boxes can be fit on the screen at one time.
In Window 8, on the Surface Pro, the option was hidden because of the size of the screen. (The option was there on my desktop machine connected to a 24" monitor).
That said, I have the exact same problem as the original poster, actually it seems that if I do a reboot, the setting will stick, but as soon as I wake from sleep, it goes back to the default DPI. Hoping this get fixed in the final software (or that they don't remove the option!)
JUST AN INFORMATION if u ppl are building CM 10.1 kernel and facing same issue >
adfad666 (RD) said -
I have been modifying the Sony kernel sources, and porting our 4.1 kernel to a 4.2 CAF branch to be used with CyanogenMod 10.1 and above. We will eventually receive Android 4.3 direct from Sony, and therefore suitable kernel sources, but if we can beat them to it, why not?
However our Xperia SP has a very temperamental screen, it really needs a perfect frame buffer or it will crap out on you with no apparent way back.
If you flash a kernel with a broken frame buffer (a kernel that does not send the correct signals to the display), you will see nothing on the screen, sometimes random vertical lines, then your device will get into a low level bootloop, (ADB will not be available) and even if you flash a working kernel from a factory image this will not recover the device. Basically, the screen gets stuck in a non-functional state, the device is able to detect this and immediately hard resets, so your device seems hard bricked.
Well... almost.
Fortunately, Sony build into their factory images a special lock that, on first boot, nothing can cause the device to shut down or reboot. Therefore to break this hard brick, you need to do a full wipe with flashtool.
On reboot the screen will still be broken, but it will do a full boot (you will eventually hear touch sounds when pressing the screen). You can now hit the power button to switch off the display, hit it again and your screen should, finally, come back to life.
* * * * * * * * * *
Why does this happen? My guess is that a specific set of commands must be used to control the display. Any deviation from that set and the screen gets stuck in a non-functional state, and the only way to recover is to eventually send the correct off/on sequence to it.
However this can only happen from a working rom, but due to the auto detect of the broken screen and hard reset (forcing the hardware to switch off without sending an off command to the screen), this can only happen after a full wipe to recreate the first boot sequence.
Therefore if you are experimenting with the kernel you need to be aware of this... 'feature' and that luckily there is a way to recover from it.
I have needed to recover my device three times now with this method and I haven't even owned it for a week yet. I have never seen such behaviour on any of the other devices I have worked on, so this is going to make kernel porting a tricky and tedious affair. The fact that the screen 'remembers' your bad kernel even after you flash a good one is pretty disturbing. (I even left my Xperia SP powered off for over an hour to see if the lack of power would reset the screen, but no change)
official thread > http://forum.xda-developers.com/showthread.php?t=2457353
is this happen to our mobile also ? because both mobile are released at same period
Thanks
the are relased in simillar time,but both have different screens,sp have hd and we have FWVGA screen,we have also different lcd density,so i think this will be only on sp not on L.
Well, we've booted cm10.1 to homescreen. I had already adjusted frame buffer ( same as we do in recovery ) and it works fine.
A quick comparison between msm_fb.c ( video driver) in our stock kernel sources and MSM8930 CAF sources will tell you that sony team uses special CCI drivers to control the LCD... For eg brightness etc.
Without them, I doubt screen will work functionally.
Thankfully, the stock kernel booted cm10.1 without any major changes ( except frame buffers fix ) .
Hi everyone ! I'm posting this here as well as in the SP forum because I think this kind of problem isn't limited to one model or brand.
Story:
I recently got my Xperia SP's digitizer changed (apparently most phones don't like faceplants ) and when i got it back I noticed a "slight" change.
Symptom :
When I touch the screen and slide my finger there's a little lag before the move is recorded by the phone, like, I have to move my finger more than 1/2 inch away from the starting point or it consider my finger didn't move from it. (thus resulting in little jumps when sliding through menus or if you wanna draw a circle it start by drawing a straight line ) After the phone catches up however (so, as long as I keep my finger on it) it follow up well just like it has to. It's not related to the latency of the screen (as I said, after the first move and for as long as I keep my finger on the screen there's no problem) so even if it's after a hardware modification I believe it's a software related problem.
Resolution tested :
Through research I think my problem could come from a change between the dpi of the stock digitizer and the one I got in replacement, so the stock touch_slop value isn't adapted anymore. I tried to change it in my build.prop, but it mades no difference and the problem is still here. Although it doesn't mean the problem doesn't come from that (The way Android handles touch_slop has changed in the latest versions) I don't know how to fix it and I need advices. Has someone already encountered that problem ? How can I fix it ?
So, long story short : I need a way to tweak the dpi value of the digitizer that's stored somewhere on the phone.
How to change Nvidia Shield Tablet K1 Resolution from 1920x1200 to 1920x1080?
Basically they have this feature built in if you connect the HDMI cable to the tablet... then the tablet reboot in 1920x1080 and displays only on the HDMI screen (the tablet screen is off)
When you disconnect the HDMI cable it drops a notification every 1-2 minutes do you want to reboot back to normal 1920x1200 resolution and it keep asking till you agree and reboot.
My question is how i can turn it to 1920x1080 or just how to disable the notification that pop up over the screen?
I prefer not to root the device if its possible.
Nvidia Shield Tablet K1 working on Android 6
Thanks.
Hi, came across your question wile looking for a solution as well. I do have a work around for the constant ask for revert from console mode. But not sure if it works on Android 6. I'm on 5.1 still. Hate 6. I do the Console mode remove HDMI thing. Then I go on a rampage force stoping EVERYTHING I find running. I go to Settings/App/Running and force stop everything. Then the Show cached processes, also stop everything. (and I mean Everything I see, including all those google thing I dont need running at the time, tho most will turn themselves on again) Then to the 'All' apps tab and look for everything Nvidia/Shield related and force stop it. And it works. The nagging stop. I haven't figured out what is it that stop the message as I did this once on a rage for that stupid message and since it worked I do it like that every time. And I've play for well over 2+ hours without the message popping up
Oh, also, I don't have a controller but I have All-In-One Toolbox, that I also run to close everything after all the force stops. Just in case. Well with that app you can have a toolbar on the notification and add a 'Recent app' there. Which you can not only use to switch but if you tap it and then tap somewhere NOT on other apps you get send to Home screen. (Wish the add Home/Back as well)
I know it seems like a hassle. I only do this when I want to record something on Ultra and get 1920x1080 instead of that horrid 1728x1080.
OH! And the touch accuracy gets worst the closer you get to the upper/lower borders (on landscape) due to touch screen reading the 1200 pixels on a 1080 shrunk image. Takes some getting used too, but worthy to capture on an OCD friendly video resolution.
I'm on Stock 5.1.1, not root.
Gonna look for a ROM that can do 1080p and also keep the Navbar. And maybe even add 1 tap Screenshot/record shortcuts for the navbar. Old cheap tablet used to have that screenshot button on the nav bar. Which was awesome for quick snap at those special gaming moments.
Anyways, since you have 6, try going Settings/Apps/All and force stop everything Nvidia/Shield related. And let me know how it works. Running apps 5.1.1 management is one of the things that keep me on in. And how micro SD works.
Hope it helps.
@FreelancerGamer
Resoluition:
Root, terminal emulator, commands(enter):
su
wm - displays options
wm size - displays current res.
wm size 1080x1920 - it will change yours res. Restart.
All this things you can do with adb, without root.
Notifications&popup - go to - settings - sound & notify - applications - disable what you want.
Omizuke said:
Hi, came across your question wile looking for a solution as well. I do have a work around for the constant ask for revert from console mode. But not sure if it works on Android 6. I'm on 5.1 still. Hate 6. I do the Console mode remove HDMI thing. Then I go on a rampage force stoping EVERYTHING I find running. I go to Settings/App/Running and force stop everything. Then the Show cached processes, also stop everything. (and I mean Everything I see, including all those google thing I dont need running at the time, tho most will turn themselves on again) Then to the 'All' apps tab and look for everything Nvidia/Shield related and force stop it. And it works. The nagging stop. I haven't figured out what is it that stop the message as I did this once on a rage for that stupid message and since it worked I do it like that every time. And I've play for well over 2+ hours without the message popping up
Oh, also, I don't have a controller but I have All-In-One Toolbox, that I also run to close everything after all the force stops. Just in case. Well with that app you can have a toolbar on the notification and add a 'Recent app' there. Which you can not only use to switch but if you tap it and then tap somewhere NOT on other apps you get send to Home screen. (Wish the add Home/Back as well)
I know it seems like a hassle. I only do this when I want to record something on Ultra and get 1920x1080 instead of that horrid 1728x1080.
OH! And the touch accuracy gets worst the closer you get to the upper/lower borders (on landscape) due to touch screen reading the 1200 pixels on a 1080 shrunk image. Takes some getting used too, but worthy to capture on an OCD friendly video resolution.
I'm on Stock 5.1.1, not root.
Gonna look for a ROM that can do 1080p and also keep the Navbar. And maybe even add 1 tap Screenshot/record shortcuts for the navbar. Old cheap tablet used to have that screenshot button on the nav bar. Which was awesome for quick snap at those special gaming moments.
Anyways, since you have 6, try going Settings/Apps/All and force stop everything Nvidia/Shield related. And let me know how it works. Running apps 5.1.1 management is one of the things that keep me on in. And how micro SD works.
Hope it helps.
Click to expand...
Click to collapse
Hi,
Thank you for your reply.
I tried to force stop but it still pop up the notification to restore to 1920x1200.
About the Android 6, I love it Because of the SD format that turns your SD to be a part of your device storage.
I have a controller so i can navigate even without the nav bars
If i will find something i will update here.
dzidexx said:
@FreelancerGamer
Resoluition:
Root, terminal emulator, commands(enter):
su
wm - displays options
wm size - displays current res.
wm size 1080x1920 - it will change yours res. Restart.
All this things you can do with adb, without root.
Notifications&popup - go to - settings - sound & notify - applications - disable what you want.
Click to expand...
Click to collapse
Sorry for my noob question but can you please explain in more details how i can do this?
More? It's joke? There is no details.
https://youtu.be/84srsYuvKUo
dzidexx said:
@FreelancerGamer
Resoluition:
Root, terminal emulator, commands(enter):
su
wm - displays options
wm size - displays current res.
wm size 1080x1920 - it will change yours res. Restart.
All this things you can do with adb, without root.
Notifications&popup - go to - settings - sound & notify - applications - disable what you want.
Click to expand...
Click to collapse
Thanks for this post, it was answer to what I wanted to do with my tablet - getting full screen for HDMI output without console mode, which frankly would be actually worse even if it did't puck up with my Dualshock 3 (console mode for some reason closes/disables the DualShock 3 connection with the sixaxis app from Play Store) - when using Mirror mode I can use my Dualshock 3 fine and using terminal before starting to play makes the screen look glorious, especially with games like sonic 2 android or Final Fantasy IX android.