Recently I opened an AOSP bug: https://code.google.com/p/android/issues/detail?id=82922
This concerns the nexus 5's panel not reaching a full 60hz, or even within the range of error of CVT timings typically used in displays. Vsync timestamps are in the range of 58.6hz to 58.8hz, and the result is disastrous: stuttering. The problem is that timing loops assume the display is pretty close to 60hz, and try to synchronize to an even division of that. But waiting for vsync takes too long, and these programs skip frames--about 1 frame every 2/3 second --to keep up.
As a result, games aren't smooth at all. They hiccup regularly when smooth motion is attempted. Note that this isn't universally apparent; programs without an internal timer like the browser, launcher, or even some games, might just refresh whenever the vsync is ready, which is presumably how this was missed by the devs at LG/Google. 2D games suffer the worst.
I've tried to fix this. My initial suspicions lied with the initialization code and timings in the panel device file in the kernel, but I can't seem to make a difference with any changes to it.
So, I'd appreciate any help I can get with this. If anyone experienced in this area of kernel development has any suspicions about this, post them.
I'd also like some other people to test this if they can. I actually measured the timestamps from /sys/devices/virtual/graphics/fb0/vsync_event to confirm this is on the kernel level, but an easier way is to download the RetroArch app from the play store and use the calibrate refresh feature in the settings. I'm particularly looking for results from Cyanogen kernels, as those modify the msm dsi framework.
It'd also help to star the bug and try to get the Google devs' attention on this.
Thanks
tried turning off v-sync? it may be preventing you from reaching full 60hz, if you could give measurement of the said log file, for 60hz you should be getting something around, 5/3 sec? try playing back videos of various fps starting from 60-200
gamer.11 said:
tried turning off v-sync? it may be preventing you from reaching full 60hz, if you could give measurement of the said log file, for 60hz you should be getting something around, 5/3 sec? try playing back videos of various fps starting from 60-200
Click to expand...
Click to collapse
Vsync is the only method by which we can measure the actual refresh rate of the panel. There's no other way. That's not a log file, either, it's the sysfs interface by which the userspace layer polls the vblank interval start.
The panel is generating vblank interrupts at slightly over 17ms intervals. That equates with < 58.8hz.
Yes, 60fps videos suffer, too. There's no way to fit 60 unique frames into a display that can only show 58.6 or so of them every second without omitting one every ~2/3 second. 30fps videos either take twice as long to accumulate enough error, and stutter forward 34ms every 4/3 seconds, or still poll at 60hz and display one frame for 1 panel refresh every 2/3 seconds. It depends how the application was written.
Normal NTSC timing would be at minimum around 59.94hz--that's an acceptable level of error for a display, and would theoretically generate a stutter only every 17 seconds, but the leeway on the timing means it generally won't.
A discrepancy of 1.4hz (2.3%) is quite ridiculous for precision hardware like this. This bug heavily affects user perception, even if they don't know what's causing it. ("Android apps aren't as smooth as IOS", etc.)
MaulingDeOso said:
display one frame for 3 panel refreshes
Click to expand...
Click to collapse
Sorry, that's backwards, it should be 1 panel refresh. So the frame cadence ends up as 2, 2, 2, 2, 1, 2, 2, 2...
Edited.
you put the bug as small priority, put it with a higher value, because if you dont, i bet google will not look into
opssemnik said:
you put the bug as small priority, put it with a higher value, because if you dont, i bet google will not look into
Click to expand...
Click to collapse
They all start at low priority. Unfortunately, only Google devs can elevate it. With the amount of spam the bug tracker gets, it's obvious why.
MaulingDeOso said:
They all start at low priority. Unfortunately, only Google devs can elevate it. With the amount of spam the bug tracker gets, it's obvious why.
Click to expand...
Click to collapse
RetroArch
tried cm12 just to give feedback for you
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
opssemnik said:
RetroArch
tried cm12 just to give feedback for you
Click to expand...
Click to collapse
Thanks a lot. It looks like the updated kernel driver stack does makes some difference. This makes me confident that it isn't a limitation in the display controller and can indeed be fixed.
MaulingDeOso said:
Thanks a lot. It looks like the updated kernel driver stack does makes some difference. This makes me confident that it isn't a limitation in the display controller and can indeed be fixed.
Click to expand...
Click to collapse
im not a kernel developer but,
the file you said on the bug tracker page is exactly the same between cm12 and google sources (got from msm-hammerhead-3.4-l-release)
but i noticed there are some specific files for specific nexus 5 revisions, including a lcd driver. for instance, mine is rev 11 E (my first was rev 11 H), on these 2,i can´t run any rom older than release KRT16S (not even KRT16M)or else i get a yellow line at the center of my screen, so it could be that the problem is a hw problem for specific revs? or just a driver problem but again, for specific revs?
opssemnik said:
im not a kernel developer but,
the file you said on the bug tracker page is exactly the same between cm12 and google sources (got from msm-hammerhead-3.4-l-release)
but i noticed there are some specific files for specific nexus 5 revisions, including a lcd driver. for instance, mine is rev 11 E (my first was rev 11 H), on these 2,i can´t run any rom older than release KRT16S (not even KRT16M)or else i get a yellow line at the center of my screen, so it could be that the problem is a hw problem for specific revs? or just a driver problem but again, for specific revs?
Click to expand...
Click to collapse
As far as I know, there's two retail screens the Nexus 5 uses, both JDI/Orise combos, so I don't think there's much difference.
Most of the settings in that file I've found to be snake oil--they're overridden by the driver. I was referring to that. It's located in drivers/video/mdm/mdss.
MaulingDeOso said:
As far as I know, there's two retail screens the Nexus 5 uses, both JDI/Orise combos, so I don't think there's much difference.
Most of the settings in that file I've found to be snake oil--they're overridden by the driver. I was referring to that. It's located in drivers/video/mdm/mdss.
Click to expand...
Click to collapse
ahh ok, i just thoguht of that, because as i said i can´t run any kernel or bootloader older than release KRT16S.(big yellow line at the center of my screen)
i will look into the commit history of cm´s hh kernel, see if i find something, altought most come from qcom there shall be something in there
opssemnik said:
mine is rev 11 E (my first was rev 11 H), on these 2,i can´t run any rom older than release KRT16S (not even KRT16M)or else i get a yellow line at the center of my screen, so it could be that the problem is a hw problem for specific revs? or just a driver problem but again, for specific revs?
Click to expand...
Click to collapse
E and H are Elpida and Hynix, it's just the brand of the memory used in your device. One other person (ONLY one) has also reported a "HJ" brand memory but I have no idea what that would be.
But nothing to do with the screen.
opssemnik said:
RetroArch
tried cm12 just to give feedback for you
Click to expand...
Click to collapse
which cm12 build did you test? I have tried the latest 18 nightly and can only get 58.6hz...
xillius200 said:
which cm12 build did you test? I have tried the latest 18 nightly and can only get 58.6hz...
Click to expand...
Click to collapse
i tried on 15 nightly, altought i tried just now on the 19 nightly and same results, with the exception of the first that i got 48hz(but probably because i reiceived 3 notifications during the test)
opssemnik said:
i tried on 15 nightly, altought i tried just now on the 19 nightly and same results, with the exception of the first that i got 48hz(but probably because i reiceived 3 notifications during the test)
Click to expand...
Click to collapse
well I don't know what the difference between your phone and mine is exactly, however I have tried the 21 nightly also and cannot get anywhere above 58hz on stock kernel as well or any other kernel.
D821 - Black - CM12 5.0.2 - 16gb
Edit: Mine is also a Rev_11E
xillius200 said:
well I don't know what the difference between your phone and mine is exactly, however I have tried the 21 nightly also and cannot get anywhere above 58hz on stock kernel as well or any other kernel.
D821 - Black - CM12 5.0.2 - 16gb
Click to expand...
Click to collapse
well, either im doing something wrong, or idk. i recorded the test yesterday with my friends phone, i will ask him to upload it or give to me, so you guys see how i do the tests, because i got same results on stock 4.4.4
PS: D821 white, bought in brazil, rev11 E, came with stock 4.4.2 KOT49H
EDIT:
Edit 2:
video -> http://youtu.be/MSJkOENfsuQ
I got 59.07 , 59.02
I'm getting 60.0794Hz. Is this what we want?
rev_11
humzaahmed155 said:
I'm getting 60.0794Hz. Is this what we want?
rev_11
Click to expand...
Click to collapse
I have rev_11 too. Still,only 59.07 ..you
You people do realize rev_11 is the ONLY revision, and the letter is just the memory brand? Nothing to do with the screen.
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
BBQScreen lets you see your Android device's screen on your computer at fullspeed.
Unlike many Phone-to-PC screen sharing app, BBQScreen lets you see your device's screen in realtime and at a high framerate. It's super easy to setup, and can work through Wi-Fi, USB Tethering, or even Bluetooth tethering (best experienced with Wi-Fi or USB Tethering).
Get and install this app on your Android device, and get the latest client app on your computer at http://screen.bbqdroid.org. You just have to enter your device's IP address, and it's working immediately.
See it on the Play Store
It's not working, I think I need to forward the port. What port is this running on?
Always Stuck! No frames Received...
Lenovo s560. USB/Wifi Thetering not working
The program crashes on landscape (tested on HTC one X + Note II)
http://pastebin.com/2uk879kM
Nalty said:
It's not working, I think I need to forward the port. What port is this running on?
Click to expand...
Click to collapse
9876 UDP, but you should be on the same Wi-Fi network as your device (or use USB tethering).
okitsaws said:
Always Stuck! No frames Received...
Lenovo s560. USB/Wifi Thetering not working
Click to expand...
Click to collapse
Can you try lowering screen scale?
Could you provide a list of system requirements and/or supported platforms/devices?
Eg. What devices did you test the app successfully on (besides the Nexus 4)?
What OS versions (+SP or any additional components) did you test the clients with?
So I guess a list of verified configurations (vs. failed configurations) would be nice so people won't force something that is never going to work (with the current version).
bit2 said:
Could you provide a list of system requirements and/or supported platforms/devices?
Eg. What devices did you test the app successfully on (besides the Nexus 4)?
What OS versions (+SP or any additional components) did you test the clients with?
So I guess a list of verified configurations (vs. failed configurations) would be nice so people won't force something that is never going to work (with the current version).
Click to expand...
Click to collapse
In theory all devices should work, the app relies on the system's capability to do screenshots basically. We tested it on Nexus 4, S3, Note II and TF700T without any problem. We will investigate more however to check why it doesn't work for some people (where the same Android device works for others). The fact that we use UDP is giving lost frames, thus we'll invite users to reduce scale for more stability.
Maybe you need a free test app so people can ensure it works with their devices first :good:
I can't get this working on my laptop, I always get "no frame received, are you sure of your android device address?" I've restarted everything, and the address is typed in properly. This is with 3 different android devices.
airmaxx23 said:
I can't get this working on my laptop, I always get "no frame received, are you sure of your android device address?" I've restarted everything, and the address is typed in properly. This is with 3 different android devices.
Click to expand...
Click to collapse
Try lowering screen scale.
XpLoDWilD said:
Try lowering screen scale.
Click to expand...
Click to collapse
Thanks, but that didn't work, I went all the way down to 25%. I also tried lowering the quality.
It works here on an SGS2 but not on a GNexus.
PC: Win8 x64 (updated redistributable as instructed)
Connection method: WiFi router or USB tethering
Galaxy S2: JellyBam v5.1.0 stable (4.2.1 - 01.28.2013).
- Testing with the "Nexus" live wallpaper, I got an average framerate of 9 when using scale 80% (quality 50%) but it went up to 25 when reducing the scale to 50% (same quality). The image quality is not something to write home about but at least it's working.
Galaxy Nexus: ParanoidAndroid v3.15 (4.2.2 - 03.28.2013) no DPI tweaks applied, everything was set to default
- could not connect to the server regardless of the scale (went as low as 25%).
[edit] Results are the same when connecting through USB tethering. But the FPS is a little better on the SGS2. The image still gets corrupted even at scale 50 but only when increasing the Quality above 95%
Bug: the windows client always reconnects to the previous server, provided that's still running (in my case the SGS2) regardless of the IP typed in the connection dialogue.
o/
Doesn't work on Nexus 7 with Paranoid Android 3.10 - scale 25%, quality 5%
Works on my Nexus S (CM 10.1) on the same network and PC. I have about 6 FPS with default settings (scale 100%, quality 60%).
PC: Windows 8 Pro x64
The Linux client is compiled for 64 bit. Can you please provide an executable in 32 bit?
Code:
$ file BBQScreenClient
BBQScreenClient: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.18, BuildID[sha1]=01bf24149cc004e7eef5d9dd547e252219a3ada4, not stripped
An unrelated question: Is it possible to stream a video with this app?
Simply , AWESOME !
but a little problem
http://i.imgur.com/IQNbrBJ.png
too big ?
XpLoDWilD said:
9876 UDP, but you should be on the same Wi-Fi network as your device (or use USB tethering).
Can you try lowering screen scale?
Click to expand...
Click to collapse
Setting scale to minimum : 25%.
and quality to 5% still Not working.
I really want this app work for my phone Badly.
Sorry for bad English.
alkasser011 said:
Simply , AWESOME !
but a little problem
http://i.imgur.com/IQNbrBJ.png
too big ?
Click to expand...
Click to collapse
You can reduce Scale in app settings.
We are working on fixing the last issues. Hang tight.
opa0opa said:
It works here on an SGS2 but not on a GNexus.
(...)
Galaxy Nexus: ParanoidAndroid v3.15 (4.2.2 - 03.28.2013) no DPI tweaks applied, everything was set to default
- could not connect to the server regardless of the scale (went as low as 25%).
Click to expand...
Click to collapse
It doesn't work for me either (on a Galaxy Nexus). I tried both the Mac and the Windows client, but neither could connect.
Both reported the same: "No frame received, are you sure of your Android device address?"
Yes, I'm sure.
Watching the traffic between the computer and Android (via Wireshark) I see that UDP packets go out from the computer (source port 9876) to the Gnex (dest port 9876) and the Gnex sends back ICMP Destination Unreachable (i.e. Type=3) replies with Code=3 (Port Unreachable). And yes, I'm sure that the ICMP replies come from the Gnex, the source MAC address of the ICMP replies matches with my Gnex's WiFi MAC address.
Meanwhile on the Gnex I monitor traffic with Network Log. It doesn't show any (traffic) for BBQScreen.
It's as if BBQScreen fails to listen for incoming UDP packets.
Tried to lower the scale to 25% (the minimum), but it didn't help (I didn't expect it to either).
My Gnex has the official 4.2.2 build. There're no firewall (iptables) rules in place (apart from what Android itself uses for data usage logging).
What's next to debug?
Hi!
I just bought BBQScreen but it doesnt work on my Galaxy Tab 10.1 with Cm10.1! The windows client just says no frame received although the ip is right (and the devices are of course in the same wifi network)! What can I do to help you fix this problem with your app?
JanusDC said:
The Linux client is compiled for 64 bit. Can you please provide an executable in 32 bit?
Code:
$ file BBQScreenClient
BBQScreenClient: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.18, BuildID[sha1]=01bf24149cc004e7eef5d9dd547e252219a3ada4, not stripped
Click to expand...
Click to collapse
What this guy said and a readme with dependables (if necessary would be great) =)
On July 11, Google rolled out a new version of Google Maps for Android (V 7.0.1) for Android versions 4.0.3 and greater (less than 4.0.3 get a different update, I think.). I have used Maps and Navigation extensively for a long time. I also have used Waze. The new version of Google Maps will reroute you if traffic builds up on your route (just like Waze). I was looking forward to that feature.
I am currently running CM10 and the new Maps doesn't work well. The graphics are jumpy and stitchy (?). When I hit the options button during Navigation it brings up the menu, but then shortly thereafter that menu is covered up by the previous graphic and I can't see what I am supposed to select.
I don't know if it is a limitation of my phone, my ROM, or if Maps is buggy. On my previous phone, at one point I had to stop updating Maps because my phone wasn't powerful enough. I hope that isn't the case for the Exhibit and maps now.
I would like to hear from others, both good and bad, about their experience with the new maps.
Thanks.
wrusry said:
On July 11, Google rolled out a new version of Google Maps for Android (V 7.0.1) for Android versions 4.0.3 and greater (less than 4.0.3 get a different update, I think.). I have used Maps and Navigation extensively for a long time. I also have used Waze. The new version of Google Maps will reroute you if traffic builds up on your route (just like Waze). I was looking forward to that feature.
I am currently running CM10 and the new Maps doesn't work well. The graphics are jumpy and stitchy (?). When I hit the options button during Navigation it brings up the menu, but then shortly thereafter that menu is covered up by the previous graphic and I can't see what I am supposed to select.
I don't know if it is a limitation of my phone, my ROM, or if Maps is buggy. On my previous phone, at one point I had to stop updating Maps because my phone wasn't powerful enough. I hope that isn't the case for the Exhibit and maps now.
I would like to hear from others, both good and bad, about their experience with the new maps.
Thanks.
Click to expand...
Click to collapse
The lag and stickyness is due to phone's ram. its optimized for phone with ics or jb out of box, which have sufficient ram. I was surprised to see it actually run on our phone
ReckYoChips said:
The lag and stickyness is due to phone's ram. its optimized for phone with ics or jb out of box, which have sufficient ram. I was surprised to see it actually run on our phone
Click to expand...
Click to collapse
Thanks for the response. Sorry I am a bit slow. Can you clarify? Did you load it and also experience poor performance or are you just giving your reasoning (which I agree with) for my poor experience?
Also, which ROM did you use it with?
Thanks.
I tried it out on mine, saw the same issues you are seeing. Running the last available build of RootBox 4.1.2.
I restored the backup of the previous version I had made with Titanium Backup.
I see there might be a new AOIP 4.2 build soon, which will include overclocking options. I plan to try it on that one when it comes out.
Sent from my SGH-T679 using xda app-developers app
I am using it on AOIP I don't have any lag, GPS lock is good, only issue on aoip is that the notification bar flickers sometime and that causes the map to go out of whack, (1out of 10 times) so its manageable
Sent from my SGH-T679 using xda app-developers app
Tweaks
I experimented with different settings to see if I can make Maps work better.
CPU speed doesn't matter - CM10 is overclocked and I experimented with it
16 bit transparency option - doesn't help
Memory management, zRam - this *does* seem to help. It reduces the incidence of flickering. I tried 18% (default) and 26%. 26% seemed to help more.
Clearing up memory - This seemed to help the most. To clear up memory, I did it by menu - manage apps - running.
I will stop messing with it and just try it to see if I like it enough to live with the drawbacks. Perhaps AOIP will help. I'm waiting on the next version. I expect it won't. There is always a small chance that google will make it less memory dependent. Doubtful, though.
We have been very fortunate that we have good 4.1 and 4.1 ROMs for this device. Eventually we knew that our device just wouldn't cut it for some things. Maps may be the first/most prominent.
Thanks for the inputs/feedback. If you have more insights, I'd love to hear them.
Google Maps 7.0.1
I'm having the same problems here. I'm running AOIP 1.0 with the included kernel. I'm getting flickering and corruption. Also, the map display hangs and stops updating my current location after a few minutes, but the voice guidance is still correct. I can swipe the map and then click resume and it goes to the correct location. It doesn't seem like a problem with insufficient RAM to me because I can play music in the background and it works fine. It seems more like an issue with the graphics driver.
I wonder if Google is trying to make use of the fast cpu to gpu copy feature that most newer devices support? I think our current drivers from Qualcomm have a problem with this feature because I've seen similar corruption then using Robert Broglia's emulators that use this feature. Maybe the drivers report that the feature is present, but it is not correctly implemented? Does anybody know if there were ever any Snapdragon/Adreno 205 devices with an official ICS or JB ROM out there that we could borrow their drivers from, or does anybody know if the Snapdragon even supports this feature in hardware?
Here is my ROM and OpenGL info:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
spiked_mistborn said:
I'm having the same problems here. I'm running AOIP 1.0 with the included kernel. I'm getting flickering and corruption. Also, the map display hangs and stops updating my current location after a few minutes, but the voice guidance is still correct. I can swipe the map and then click resume and it goes to the correct location. It doesn't seem like a problem with insufficient RAM to me because I can play music in the background and it works fine. It seems more like an issue with the graphics driver.
I wonder if Google is trying to make use of the fast cpu to gpu copy feature that most newer devices support? I think our current drivers from Qualcomm have a problem with this feature because I've seen similar corruption then using Robert Broglia's emulators that use this feature. Maybe the drivers report that the feature is present, but it is not correctly implemented? Does anybody know if there were ever any Snapdragon/Adreno 205 devices with an official ICS or JB ROM out there that we could borrow their drivers from, or does anybody know if the Snapdragon even supports this feature in hardware?
Here is my ROM and OpenGL info:
Click to expand...
Click to collapse
Thanks for your thoughts and inputs. Unfortunately, I'm not smart enough to comment on whether the cpu to gpu feature is supported or not. Maybe someone else can comment. The drivers seem to be available here, though:
https://developer.qualcomm.com/mobi...phics-optimization-adreno/tools-and-resources
Ok, I think this problem is definitely related to the graphics drivers and not the amount of RAM. I installed the new Google Maps on an HTC Inspire 4G that I have and it's having the same problem. The Inspire 4G uses the same snapdragon/Adreno 205 SOC as the Exhibit 4G. I'm running a flavor of JB 4.2.2, and the ROM uses the same version graphics drivers. The main difference between the two is that the Inspire 4G has 768MiB of RAM instead of 512MiB.
I'm going to try creating a Qualcomm login to see if I can download the newer drivers. It looks like the JB.04.01.01.00.036 drivers are dated Aug 2012. The most recent ones are JB_VANILLA.04.02.02.060.053 from April 2013. If the new ones are available as binaries maybe the files can be swapped in the ROM zip file and re-flashed. If it's source only I don't have a build environment setup, nor the time to learn how to do it.
spiked_mistborn said:
Ok, I think this problem is definitely related to the graphics drivers and not the amount of RAM. I installed the new Google Maps on an HTC Inspire 4G that I have and it's having the same problem. The Inspire 4G uses the same snapdragon/Adreno 205 SOC as the Exhibit 4G. I'm running a flavor of JB 4.2.2, and the ROM uses the same version graphics drivers. The main difference between the two is that the Inspire 4G has 768MiB of RAM instead of 512MiB.
I'm going to try creating a Qualcomm login to see if I can download the newer drivers. It looks like the JB.04.01.01.00.036 drivers are dated Aug 2012. The most recent ones are JB_VANILLA.04.02.02.060.053 from April 2013. If the new ones are available as binaries maybe the files can be swapped in the ROM zip file and re-flashed. If it's source only I don't have a build environment setup, nor the time to learn how to do it.
Click to expand...
Click to collapse
Good luck. I appreciate your efforts.
I tried this http://forum.xda-developers.com/showthread.php?t=2306286 to update the drivers to JB_VANILLA.04.02.02.060.053 and the phone boots, but the display is blank. I'm running a 3.4 based kernel, but I'm not sure if it meets this requirement
Needs a 3.4 caf kernel on the jb2 branch. Or at least the drivers from it
Click to expand...
Click to collapse
.
Team Insomnia had AOIP 1.5 up on their site, but I didn't try it because I don't like changing ROMs alot, and I want to make sure everything works before I flash. So keep an eye out for that. Maybe there will be some kernel updates, and then I'll try this again. Or maybe Google will update Maps.
spiked_mistborn said:
I tried this http://forum.xda-developers.com/showthread.php?t=2306286 to update the drivers to JB_VANILLA.04.02.02.060.053 and the phone boots, but the display is blank. I'm running a 3.4 based kernel, but I'm not sure if it meets this requirement .
Team Insomnia had AOIP 1.5 up on their site, but I didn't try it because I don't like changing ROMs alot, and I want to make sure everything works before I flash. So keep an eye out for that. Maybe there will be some kernel updates, and then I'll try this again. Or maybe Google will update Maps.
Click to expand...
Click to collapse
Where did you see the "Needs a 3.4 caf kernel" info?
BTW, I PM'd one of the developers and he said "We cant use the new qualcom drivers because our kernel doesnt support ion."
I'm not sure what ion is.
[edit]
I found that: ION is a generalized memory manager that Google introduced in the Android 4.0 ICS (Ice Cream Sandwich) release to address the issue of fragmented memory management interfaces across different Android devices.
http://lwn.net/Articles/480055/
result?
wrusry said:
Where did you see the "Needs a 3.4 caf kernel" info?
BTW, I PM'd one of the developers and he said "We cant use the new qualcom drivers because our kernel doesnt support ion."
I'm not sure what ion is.
[edit]
I found that: ION is a generalized memory manager that Google introduced in the Android 4.0 ICS (Ice Cream Sandwich) release to address the issue of fragmented memory management interfaces across different Android devices.
http://lwn.net/Articles/480055/
Click to expand...
Click to collapse
Does the end result of all of this mean we can't run Google Maps on our phones, as the chip just isn't powerful enough? Can we downgrade to an older Maps? I really liked this functionality of my old GB phone and would hate to lose it. Thanks.
Proud2banoob said:
Does the end result of all of this mean we can't run Google Maps on our phones, as the chip just isn't powerful enough? Can we downgrade to an older Maps? I really liked this functionality of my old GB phone and would hate to lose it. Thanks.
Click to expand...
Click to collapse
I don't know the reason why the new Google Maps doesn't run well on the Exhibit. As has been suggested before, it may be a driver/kernel issue. I think the hardware is probably sufficient. It may not be, though.
In any case, you can still run Google Maps 6.14.4. You can find it here: http://www.apk4.net/applications/travel-local/google-maps-6-14-4-apk/
If you want nice traffic rerouting (new feature of Google Maps 7.0x) you can use Waze instead.
installing
wrusry said:
I don't know the reason why the new Google Maps doesn't run well on the Exhibit. As has been suggested before, it may be a driver/kernel issue. I think the hardware is probably sufficient. It may not be, though.
In any case, you can still run Google Maps 6.14.4. You can find it here: http://www.apk4.net/applications/travel-local/google-maps-6-14-4-apk/
If you want nice traffic rerouting (new feature of Google Maps 7.0x) you can use Waze instead.
Click to expand...
Click to collapse
thanks for the link. do i need to download it to a computer first? What is the protocol for putting this app on my phone? I have never installed any other way than from the Google Play market. Thanks. I will also try Waze.
Proud2banoob said:
thanks for the link. do i need to download it to a computer first? What is the protocol for putting this app on my phone? I have never installed any other way than from the Google Play market. Thanks. I will also try Waze.
Click to expand...
Click to collapse
You can download it directly to your phone. Then you locate it (in file manager under downloads directory most likely) and click on it and it will ask you if you want to install it. It is pretty simple.
perfect
wrusry said:
You can download it directly to your phone. Then you locate it (in file manager under downloads directory most likely) and click on it and it will ask you if you want to install it. It is pretty simple.
Click to expand...
Click to collapse
Awesome. Thank you. Waze is ok, except they linked to my FB. I am already running Tinfoil for FB, so they can't track me. This is Waze is counter-productive for that.
Unfortunately, I am having another problem. Maps keeps updating itself to the latest version, which doesn't work. There is no option to disable automatic updates, so how do I make it stop? Thanks.
Sent from my SGH-T679 using xda app-developers app
Proud2banoob said:
Unfortunately, I am having another problem. Maps keeps updating itself to the latest version, which doesn't work. There is no option to disable automatic updates, so how do I make it stop? Thanks.
Sent from my SGH-T679 using xda app-developers app
Click to expand...
Click to collapse
Open play store then -> settings -> disable auto-update apps
The Google Maps 7.0.2 update from 7/17/13 seems to be working fine now. I tried it yesterday and it was very responsive, and no display corruption.
Is there any ROM that works with Android Auto for the smartphone samsung galaxy slll (i9300)?
AN17 said:
Is there any ROM that works with Android Auto for the smartphone samsung galaxy slll (i9300)?
Click to expand...
Click to collapse
Last I checked a few months ago no, at least among popular Android 5.1 ROMs, which I think are mostly derived from CM.
I've never checked some Ancient 5.0 ROMs though, and 5.0 is the minimum for AA.
Basically, the H.264 video encoder does not work, and the CM dev did not expect that to ever be fixed or even fixable.
Same for GT-N7100, GS2/Note1 and even GT-I9000.
Android Auto working on i9300 custom ROM
Hi all, well this is my first post on XDA but not my first visit, I hope you find it helpfull... (and sorry for the long post)
I recently fond myself unable to use the Android Auto car projection on my i9300, I did a little googling and came across this post, but the answer of mikereidis did not convince me, since I found in my logcat the following line:
FFmpegExtractor: suppoted codec(h264) by official Stagefright
Click to expand...
Click to collapse
I don't know if that means that the encoder is working but I found no errors or warnings pointing to h.264 (again, I did not check it thoughtfully). What I did found, when I started the AA app, was the following:
01-16 13:38:10.575 15461 15461 I FsmController: fireEvent(EVENT_VANAGON_MODE_STARTED)
01-16 13:38:10.595 15461 15461 D FsmController: State stack (size=1)
01-16 13:38:10.595 15461 15461 D FsmController: 0: com.google.android.projection.gearhead.frx.SetupFsm$VanagonCapabilityCheckState
01-16 13:38:10.625 15461 15496 W CAR.SERVICE: Not supported: total mem 867790848 is lower than minimum 891289600
01-16 13:38:10.625 15461 15496 I CAR.SERVICE: check device capability result false iframe interval -
Click to expand...
Click to collapse
Even if there where a codec problem, the first problem was RAM... But wait, i9300 has 1GB RAM of which only 827 MB are aviable to user, we where only 23552 KB away.
Where is my precious RAM going? The answer to that question came with the help of [1]. Sadly there is no app or customizable kernel that supports editing the reserved device memory, so I had to recompile the whole kernel (First time doing that too =D ).
After a few days, I downloaded the LineageOS 14.1 code and came across its configuration parameters, which are the following:
#
# Reserved memory configurations
#
CONFIG_VIDEO_SAMSUNG_MEMSIZE_FIMC0=62464
CONFIG_VIDEO_SAMSUNG_MEMSIZE_FIMC1=15360
CONFIG_VIDEO_SAMSUNG_MEMSIZE_FIMC2=0
CONFIG_VIDEO_SAMSUNG_MEMSIZE_FIMC3=0
CONFIG_VIDEO_SAMSUNG_MEMSIZE_MFC_SECURE=50176
CONFIG_VIDEO_SAMSUNG_MEMSIZE_MFC_NORMAL=4096
CONFIG_VIDEO_SAMSUNG_MEMSIZE_JPEG=0
CONFIG_VIDEO_SAMSUNG_MEMSIZE_TVOUT=0
CONFIG_VIDEO_EXYNOS=y
CONFIG_VIDEO_EXYNOS_MEMSIZE_FIMC_IS=12080
#
# Reserved memory configurations
#
CONFIG_VIDEO_SAMSUNG_MEMSIZE_FLITE0=10240
CONFIG_VIDEO_SAMSUNG_MEMSIZE_FLITE1=10240
# CONFIG_VIDEO_EXYNOS_MIPI_CSIS is not set
# CONFIG_VIDEO_EXYNOS_TV is not set
# CONFIG_VIDEO_EXYNOS_ROTATOR is not set
CONFIG_VIDEO_EXYNOS_FIMC_IS=y
# CONFIG_VIDEO_EXYNOS_FIMC_IS_BAYER is not set
CONFIG_MEDIA_EXYNOS=y
CONFIG_V4L_MEM2MEM_DRIVERS=y
# CONFIG_VIDEO_MEM2MEM_TESTDEV is not set
#
# Graphics support
#
# CONFIG_DRM is not set
CONFIG_ION=y
CONFIG_ION_EXYNOS=y
CONFIG_ION_EXYNOS_CONTIGHEAP_SIZE=71680
# CONFIG_ION_EXYNOS_CONTIGHEAP_DEBUG is not set
# CONFIG_VGASTATE is not set
# CONFIG_VIDEO_OUTPUT_CONTROL is not set
CONFIG_FB=y
# CONFIG_FIRMWARE_EDID is not set
# CONFIG_FB_DDC is not set
# CONFIG_FB_BOOT_VESA_SUPPORT is not set
CONFIG_FB_CFB_FILLRECT=y
Click to expand...
Click to collapse
This are the things that take most of our RAM, but modifying them has its cost, lowering the FIMCx makes the camera crash, but lowering the "CONFIG_ION_EXYNOS_CONTIGHEAP_SIZE" has a more mild effect. I changed it from 71680 to 48128, and compiled. The result is the following:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(drive link if this method does not work: https://drive.google.com/file/d/0BzImZDCU_wKFRDRmcVc0VmpEZUE/view?usp=sharing)
It works! I have not tested the ROM a lot, but camera (photos and video) is working, video playback from youtube is also working. I do not play any 3D games on my phone, so I cannot tell if there is any horrible consequence there. The new ROM has 850 MB of RAM aviable to user and is AA fully compatible.
I hope you find it useful!
[1] -- https://forum.xda-developers.com/ga...t/discussion-kernel-space-dma-device-t1856133
RawthiL said:
Hi all, well this is my first post on XDA but not my first visit, I hope you find it helpfull... (and sorry for the long post)
I recently fond myself unable to use the Android Auto car projection on my i9300, I did a little googling and came across this post, but the answer of mikereidis did not convince me, since I found in my logcat the following line:
I don't know if that means that the encoder is working but I found no errors or warnings pointing to h.264 (again, I did not check it thoughtfully). What I did found, when I started the AA app, was the following:
Even if there where a codec problem, the first problem was RAM... But wait, i9300 has 1GB RAM of which only 827 MB are aviable to user, we where only 23552 KB away.
Where is my precious RAM going? The answer to that question came with the help of [1]. Sadly there is no app or customizable kernel that supports editing the reserved device memory, so I had to recompile the whole kernel (First time doing that too =D ).
After a few days, I downloaded the LineageOS 14.1 code and came across its configuration parameters, which are the following:
This are the things that take most of our RAM, but modifying them has its cost, lowering the FIMCx makes the camera crash, but lowering the "CONFIG_ION_EXYNOS_CONTIGHEAP_SIZE" has a more mild effect. I changed it from 71680 to 48128, and compiled. The result is the following:
(drive link if this method does not work: https://drive.google.com/file/d/0BzImZDCU_wKFRDRmcVc0VmpEZUE/view?usp=sharing)
It works! I have not tested the ROM a lot, but camera (photos and video) is working, video playback from youtube is also working. I do not play any 3D games on my phone, so I cannot tell if there is any horrible consequence there. The new ROM has 850 MB of RAM aviable to user and is AA fully compatible.
I hope you find it useful!
[1] -- https://forum.xda-developers.com/ga...t/discussion-kernel-space-dma-device-t1856133
Click to expand...
Click to collapse
Hey RawthiL,
I am sitting with the same problem on my Samsung S3 with Lineage OS 14.1 trying to run AA with my car display.
Do you have a compiled ROM with the changed settings that you can share. I am a layman at this and would appreciate the help.
Thanks.
RawthiL said:
Hi all, well this is my first post on XDA but not my first visit, I hope you find it helpfull... (and sorry for the long post)
I recently fond myself unable to use the Android Auto car projection on my i9300, I did a little googling and came across this post, but the answer of mikereidis did not convince me, since I found in my logcat the following line:
I don't know if that means that the encoder is working but I found no errors or warnings pointing to h.264 (again, I did not check it thoughtfully). What I did found, when I started the AA app, was the following:
Even if there where a codec problem, the first problem was RAM... But wait, i9300 has 1GB RAM of which only 827 MB are aviable to user, we where only 23552 KB away.
Where is my precious RAM going? The answer to that question came with the help of [1]. Sadly there is no app or customizable kernel that supports editing the reserved device memory, so I had to recompile the whole kernel (First time doing that too =D ).
After a few days, I downloaded the LineageOS 14.1 code and came across its configuration parameters, which are the following:
This are the things that take most of our RAM, but modifying them has its cost, lowering the FIMCx makes the camera crash, but lowering the "CONFIG_ION_EXYNOS_CONTIGHEAP_SIZE" has a more mild effect. I changed it from 71680 to 48128, and compiled. The result is the following:
(drive link if this method does not work: https://drive.google.com/file/d/0BzImZDCU_wKFRDRmcVc0VmpEZUE/view?usp=sharing)
It works! I have not tested the ROM a lot, but camera (photos and video) is working, video playback from youtube is also working. I do not play any 3D games on my phone, so I cannot tell if there is any horrible consequence there. The new ROM has 850 MB of RAM aviable to user and is AA fully compatible.
I hope you find it useful!
[1] -- https://forum.xda-developers.com/ga...t/discussion-kernel-space-dma-device-t1856133
Click to expand...
Click to collapse
Could you make this release available? Tks.
---------- Post added at 06:52 PM ---------- Previous post was at 06:47 PM ----------
avidsukhoi said:
Hey RawthiL,
I am sitting with the same problem on my Samsung S3 with Lineage OS 14.1 trying to run AA with my car display.
Do you have a compiled ROM with the changed settings that you can share. I am a layman at this and would appreciate the help.
Thanks.
Click to expand...
Click to collapse
Did you get any version that supports Android Auto for Galaxy S3?
AN17 said:
Is there any ROM that works with Android Auto for the smartphone samsung galaxy slll (i9300)?
Click to expand...
Click to collapse
I'm using one S3 as AAGateway Slave with android 5.0.1 so I think this version can run Android Auto.
JRFabbi said:
I'm using one S3 as AAGateway Slave with android 5.0.1 so I think this version can run Android Auto.
Click to expand...
Click to collapse
But, do you can connect, with this ROM, to your car multimedia? I'm asking this cause I have a ROM that supports Android Auto, but the car multimedia doesn't accept the connection.
Tks.
Sadly I do not use the i9300 anymore so I cannot tell you if it is working with the latest AA updates. I worked back then just beacuse I was able to squeeze a little more RAM into the user pool. If they raised the minimum RAM requirements of AA it wont work...
Nevertheless I will search for the ROM in my backups and try to upload it for you (give me a couple of days). If you want to build it yourself you will have to download the lineageOS code and edit the kernel config, using a text editor or the "make menuconfig" command (if I remember well). As I said in the post, you only have to reduce the video heap size which is under the option name "CONFIG_ION_EXYNOS_CONTIGHEAP_SIZE" .
RawthiL said:
Sadly I do not use the i9300 anymore so I cannot tell you if it is working with the latest AA updates. I worked back then just beacuse I was able to squeeze a little more RAM into the user pool. If they raised the minimum RAM requirements of AA it wont work...
Nevertheless I will search for the ROM in my backups and try to upload it for you (give me a couple of days). If you want to build it yourself you will have to download the lineageOS code and edit the kernel config, using a text editor or the "make menuconfig" command (if I remember well). As I said in the post, you only have to reduce the video heap size which is under the option name "CONFIG_ION_EXYNOS_CONTIGHEAP_SIZE" .
Click to expand...
Click to collapse
Thank you so much. If you find in your backup and upload I really appreciated. Tks.
Hi @RawthiL,
I'm also interested in making AA work on my S3, could you please explain how you managed to get the error log when launching the app ? I'd like to check if requirement changed in recent version. If not, I'll be interested in your custom ROM (if you still have it)
@RRvello if @RawthiL sent it to you privately, I'm interested in getting it too
Thanks Guys
I sent the ROM to @RRvello, but I don't know if it is working, maybe he can give us some feedback on that. I will send the link to you via PM @lenuisible2 so you can try it.
I think that I used the adb logcat command while launching the android auto app. have you checked that?
RawthiL said:
I sent the ROM to @RRvello, but I don't know if it is working, maybe he can give us some feedback on that. I will send the link to you via PM @lenuisible2 so you can try it.
I think that I used the adb logcat command while launching the android auto app. have you checked that?
Click to expand...
Click to collapse
Thanks @RawthiL for the file and the command, I'll try them and let you know !
really
very useful and helpful thread
thanks
It does work, Thanks @RawthiL !
I used to have "Your Device is not compatible ..." with all CM and Lineage version I tried, and now the connection to the car is established. Didn't make much tests, but it looks laggy, nothing surprising for a 7 years old device.
Next I will try the mirroring hack, not sure it will be usable because of the under powered phone, but I'll give it a try.
AA mirror works, without much lag !
I just followed the usual tutorial, no need to downgrade Google Play Services or anything else:
- root GS3
- install AA unlock/AA mirror
- launch unlock, grant root access, unlock, reboot
- launch AA mirror, configure settings you need
- connect phone to the car, go to speedo icon, choose AA mirror
Sound and video are working great, I don't have a touchscreen on my car (Audi A4 B9), so I have to navigate with the phone touchscreen (I enabled the Show Taps dev option to see where my finger is).
Of course it's not safe to play with phone / stare at screen while driving...
Thanks again to @RawthiL for making this test a success on my old unused GS3 !
Great to hear that!
Thanks for sharing how to enable the screen mirroring, I was not aware that you could do that. The lag issue is indeed annoying in AA...
lenuisible2 said:
AA mirror works, without much lag !
Click to expand...
Click to collapse
Hi,
Someone can confirm is still works?
I have an old S3, and want to give it a way to use it with my android car (soon to own that).
If so, what ROM, kernel, and root do you use?
Thank you
It's really annoying that there's these framedrops all over the software, and the phone never runs a 100 percent smooth because of it.
Snapchat and YouTube are the worst in my opinion. Ir's gibberish mix from 60 to 120 hz and it makes the phone feel incredibly slow and bugged.
I searched everywhere, tried every little thing to force 120 hz, like it was possible on OxygenOS 11 still.
No mod is working anymore. What a dealbreaker to be honest.
Do any of you think that there is hope? I saw in this AndroidPolice post at the end that arter97 ("AutoHz") might have found a fix for Android 12 and will update the app sooner or later. That was almost 5 months ago now though.
Any hope? I'd go that far to set up a bounty of 100$ for anyone who can provide a working fix.
memocatcher said:
It's really annoying that there's these framedrops all over the software, and the phone never runs a 100 percent smooth because of it.
Snapchat and YouTube are the worst in my opinion. Ir's gibberish mix from 60 to 120 hz and it makes the phone feel incredibly slow and bugged.
I searched everywhere, tried every little thing to force 120 hz, like it was possible on OxygenOS 11 still.
No mod is working anymore. What a dealbreaker to be honest.
Do any of you think that there is hope? I saw in this AndroidPolice post at the end that arter97 ("AutoHz") might have found a fix for Android 12 and will update the app sooner or later. That was almost 5 months ago now though.
Any hope? I'd go that far to set up a bounty of 100$ for anyone who can provide a working fix.
Click to expand...
Click to collapse
I know on precious devices you can on root. Is that not the case anymore?
You can already do this, there's a mod for it..have had it installed, just can't remember where it is.
I'll have a look for you.. keep that bounty on ice I'll be back now
Edit: there y go pal.
dladz said:
You can already do this, there's a mod for it..have had it installed, just can't remember where it is.
I'll have a look for you.. keep that bounty on ice I'll be back now
Edit: there y go pal.
Click to expand...
Click to collapse
No way?! Wow you're a life saver! No idea how I overlooked that lol. Does it have to be set up every reboot or not? And do you think it will have a huge negative impact in battery life?
Also dm me ur paypal I'll give you 10$ for the help
@dladz sry for pinging but you seem to know quiet some stuff abt the 10 pro. one other issue is really bugging me.
whenever I use an app like chrome, gmail etc... and leave the app with the "home button" (to keep it in ram), then revisit the app 10 seconds later, I will be greeted with the splash screen and the app acts like I just now opened it.
it won't stay open in the background it seems.
any help for that?
memocatcher said:
@dladz sry for pinging but you seem to know quiet some stuff abt the 10 pro. one other issue is really bugging me.
whenever I use an app like chrome, gmail etc... and leave the app with the "home button" (to keep it in ram), then revisit the app 10 seconds later, I will be greeted with the splash screen and the app acts like I just now opened it.
it won't stay open in the background it seems.
any help for that?
Click to expand...
Click to collapse
No worries man.
But yep I'm having the same issue buddy, seems like the close apps for saving battery is super aggressive, I have the same issue when I'm trying to copy days from one's app to another..
Really haven't found a fix as yet..13 is exactly the same.. It's absolutely pants mate.
Maybe a way to push the content to remain but I've just put up with it if I'm being honest.
Sorry man, defo annoying though.
memocatcher said:
No way?! Wow you're a life saver! No idea how I overlooked that lol. Does it have to be set up every reboot or not? And do you think it will have a huge negative impact in battery life?
Also dm me ur paypal I'll give you 10$ for the help
Click to expand...
Click to collapse
Hahaha don't be daft it's all good, hope it works for you, found it in the 10 pro TG channel, I can't post it's address here but you can find it if you search for it.
dladz said:
No worries man.
But yep I'm having the same issue buddy, seems like the close apps for saving battery is super aggressive, I have the same issue when I'm trying to copy days from one's app to another..
Really haven't found a fix as yet..13 is exactly the same.. It's absolutely pants mate.
Maybe a way to push the content to remain but I've just put up with it if I'm being honest.
Sorry man, defo annoying though.
Click to expand...
Click to collapse
Damn thats an insanely annoying issue, I now always have to make sure my data is saved within an app bc oneplus just decides to close it within seconds... Crazy. I already miss my 8 Pro and OOS 11 ;/
memocatcher said:
Damn thats an insanely annoying issue, I now always have to make sure my data is saved within an app bc oneplus just decides to close it within seconds... Crazy. I already miss my 8 Pro and OOS 11 ;/
Click to expand...
Click to collapse
I totally agree dude..I would gladly swap my 8 pro back for this, the photocrom lens, the ROMs, the performance, battery life. Even the XDA forums are laid out better.
Severe miscalculation
In other words, "Mistakes were made."
2 methods to Forcely Enable 120hz or any you wish..
1. Install Lsposed from Magisk
2. In LSposed Install "Lucky Tool" for Oneplus
3. Enable Scope for Recommend Apps and Reboot
4. Select You desired refresh rate at xx Resolution..
Spoiler: Image
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2nd Method is to flash Dpfs.zip In Magisk
its Easy to Manage from a Txt file
GuyInDogSuit said:
In other words, "Mistakes were made."
Click to expand...
Click to collapse
I get told that when I jump into an abyss on BO3
Using this app since long, works perfect. Select the 1st option, if 120 hz is not sticking just select the 2nd option and then select the 1st option back.
Another way : you just need to run a command with root previlege every reboot (which can be easily automated with magisk)
Code:
service call SurfaceFlinger 1035 i32 13
On my 8T, I use a magisk module to force 120Hz. But 10Pro have different display modes so this module itself won't work. You need to check display modes by running command
Code:
dumpsys SurfaceFlinger | grep hwcId
this is the output from 9Pro.
edit the service.sh inside the module to choose display mode id you like
Also, set persist.oplus.display.vrr=0 to reduce some frame drops (module also does that)
I think this method can be used on any android device if you can get root but haven't tested myself.
Xpid3r said:
2 methods to Forcely Enable 120hz or any you wish..
1. Install Lsposed from Magisk
2. In LSposed Install "Lucky Tool" for Oneplus
3. Enable Scope for Recommend Apps and Reboot
4. Select You desired refresh rate at xx Resolution..
Spoiler: Image
View attachment 5708831
2nd Method is to flash Dpfs.zip In Magisk
its Easy to Manage from a Txt file
Click to expand...
Click to collapse
Thank you but I find the option that dladz gave, a bit more convenient. Good to know though, that there's multiple options!
One thing, do you know any fix for the agressive background killing of apps? It bugs me so much that apps like chrome or gmail are closed withing literal seconds after I leave them.
I already tried disabling every possible optimisation but it didn't help.
6addri said:
Another way : you just need to run a command with root previlege every reboot (which can be easily automated with magisk)
Code:
service call SurfaceFlinger 1035 i32 13
On my 8T, I use a magisk module to force 120Hz. But 10Pro have different display modes so this module itself won't work. You need to check display modes by running command
Code:
dumpsys SurfaceFlinger | grep hwcId
this is the output from 9Pro.
View attachment 5708873
edit the service.sh inside the module to choose display mode id you like
Also, set persist.oplus.display.vrr=0 to reduce some frame drops (module also does that)
I think this method can be used on any android device if you can get root but haven't tested myself.
Click to expand...
Click to collapse
Thank you! I'll keep that in mind
memocatcher said:
Thank you but I find the option that dladz gave, a bit more convenient. Good to know though, that there's multiple options!
One thing, do you know any fix for the agressive background killing of apps? It bugs me so much that apps like chrome or gmail are closed withing literal seconds after I leave them.
I already tried disabling every possible optimisation but it didn't help.
Click to expand...
Click to collapse
In the Same App 'Lucky Tool' You can apps which van stand 'Not to be killed' Add apps in this and restart phone..
Spoiler: Image
6addri said:
Another way : you just need to run a command with root previlege every reboot (which can be easily automated with magisk)
Code:
service call SurfaceFlinger 1035 i32 13
On my 8T, I use a magisk module to force 120Hz. But 10Pro have different display modes so this module itself won't work. You need to check display modes by running command
Code:
dumpsys SurfaceFlinger | grep hwcId
this is the output from 9Pro.
View attachment 5708873
edit the service.sh inside the module to choose display mode id you like
Also, set persist.oplus.display.vrr=0 to reduce some frame drops (module also does that)
I think this method can be used on any android device if you can get root but haven't tested myself.
Click to expand...
Click to collapse
Is that number "13" display mode id i should change inside service.sh?
Xpid3r said:
In the Same App 'Lucky Tool' You can apps which van stand 'Not to be killed' Add apps in this and restart phone..
Spoiler: Image
View attachment 5709281
Click to expand...
Click to collapse
Just worried about my battery life that'll surely be negatively affected by these modules. But thank you I give it a try
Xpid3r said:
In the Same App 'Lucky Tool' You can apps which van stand 'Not to be killed' Add apps in this and restart phone..
Spoiler: Image
View attachment 5709281
Click to expand...
Click to collapse
It didn't help... Apps still automatically close within seconds after I leave them.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Moto Edge 20 Pro
Code:
- Your warranty is now void.
- You have been warned.
- Use at your own risk.
Introduction:
This is the Official Lineage OS 19.1 thread for the Moto Edge 20 Pro.
Downloads:
Please follow the install instructions in your device's Wiki page linked below exactly, and make sure your device's firmware matches the required firmware listed.
pstar - Official builds
If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.
Known Bugs:
None.
Find any? Report them according to this guide.
Notes:
The only supported GApps package at the moment is MindTheGapps, linked on our Wiki page about gapps.
Kernel Source: https://github.com/LineageOS/android_kernel_motorola_sm8250
Is there still a problem with the black screen of death?
wangyi666 said:
Is there still a problem with the black screen of death?
Click to expand...
Click to collapse
It shouldn't no
Will you add the fingerprint variations?
I can't use fingerprint to unlock my phone after install los, even no options in system settings. ls it normal situation?Did los doesn't support fingerprint?
x-new said:
I can't use fingerprint to unlock my phone after install los, even no options in system settings. ls it normal situation?Did los doesn't support fingerprint?
Click to expand...
Click to collapse
We are working on it, some devices use goodix fp, it is not supported right now
Thanks for this, this ROM fixes so many problems that the stock ROM from Motorola has. It's so nice now being able to call fine, use WiFI calling, being able to turn wifi on and off without it crashing and rebooting etc etc! All issues on the stock ROM for myself and others!
And it's amazing to have double tap to wake that works and a screen brightness that lowers like it should .
Only issues noticed are the fingerprint sensor issue as above, which I know you're looking into Elctimon (big thanks!) and one I seem to be getting with third party launchers sometimes which is when returning to the home screen and tapping an app icon, it interacts with the previous app instead. It's fine if you just wait longer...
I've logged a bug report for both following the instructions in the original post.
The only feature I miss from stock is the ability to set refresh rate for games to 120 or 140hz sometimes, otherwise I like my phone to be at 60hz for power savings. I turn off all animations anyway. The dynamic refresh rates sadly don't work below 70% brightness (same as stock ROM behaviour)
I tried to flash the Moto games apk which did this but unfortunately I get a missing library error : "Package com.motorola.gamemode requires unavailable shared library moto-core_services; failing!".
Perhaps a quick toggle setting could be added for refresh rates?
P.S Always on Google listening hotword detection doesn't work if you follow the instructions and install the mindthegapps package linked, it seems that it doesn't install enough packages. It needs the Google app to be installed before the OS first boots it seems? Make sure the gapps you are flashing includes Google app if you care about this.
is dc (anti flicker) works well？ i have flashed los a few month ago but the dc stoping working after lock screen
Thank you Electimon, the black screen issue has resolved for me with the latest releases.
Do you think that merging the Goodix (GF3626 fingerprint sensor) related files from the Berlin (edge 20) LineageOS build would resolve the Goodix fingerprint not working issue?
The files: https://github.com/LineageOS/android_device_motorola_berlin/search?q=goodix
I made a branch of it with the files copied over but I wasn't sure about these two files, if anyone could help me with getting these created for our device that'd be awesome!
android_device_motorola_berlin/rootdir/etc/init/hw/init.mmi.overlay.rc at 136fd799ec84e4d6ed008ab2641cac3e2d5aef3c · LineageOS/android_device_motorola_berlin
Contribute to LineageOS/android_device_motorola_berlin development by creating an account on GitHub.
github.com
android_device_motorola_berlin/modules.load at 71457c4f0467182bf7ae7834efe6dbeffa129cb7 · LineageOS/android_device_motorola_berlin
Contribute to LineageOS/android_device_motorola_berlin development by creating an account on GitHub.
github.com
https://github.com/LaurenceGough/android_device_motorola_pstar (if it helps at all) pull requests were not allowed
Thanks!
Hello Electimon. Thanks for the ROM, it's great to have something different for this underdeveloped device.
I came to Lineage to try to solve a problem with Bluetooth, but it didn't work. The problem remains exactly the same, Bluettoh only works from time to time, most of the time it doesn't even turn on. Still, I'm going to stay in this ROM, because I think it's better than the stock one.
If you have any suggestions of what I can do please enlighten me.
I don't understand how this can happen to some people and Motorola doesn't recognize it and make a fix available. I don't know what else to try, but my problem is the exact one demonstrated by this guy on Reddit:
https://www.reddit.com/r/motorola/comments/ym02hj
Hi guys,
What's up with the random reboots in this ROM? I used to have that problem on the previous Lineage as well as on the latest LMODroid build.
I need the original camera to take 108mb
thomashastings said:
Hi guys,
What's up with the random reboots in this ROM? I used to have that problem on the previous Lineage as well as on the latest LMODroid build.
Click to expand...
Click to collapse
I'm at 71 hrs uptime now, this was not achievable on any previous ROMs for this device. I'm truly thankful for this release, it's just excellent.
thomashastings said:
Hi guys,
What's up with the random reboots in this ROM? I used to have that problem on the previous Lineage as well as on the latest LMODroid build.
Click to expand...
Click to collapse
Ive never had a random reboot on this ROM, well apart for one time which I'm 99% sure was to do with an OTA update.
I've run this ROM for many weeks too.
The only downside is no fingerprint reader for my Edge 20 pro phone and that's it.
It fixes a load of issues with the stock motorola ROM!
rambo2405 said:
I need the original camera to take 108mb
Click to expand...
Click to collapse
It's just pixel binned anyway like all modern phones the 108mp is kinda a waste of time I feel. Look into gcam for our phone that's worth installing.
Well, since the last update (March 28), Bluetooth is working normally. It's still too early to know if it's fixed, but it hasn't worked this well for a while.
Bothrops said:
Well, since the last update (March 28), Bluetooth is working normally. It's still too early to know if it's fixed, but it hasn't worked this well for a while.
Click to expand...
Click to collapse
Is that with the stock ROM?
I wondered if Motorola have also fixed the outgoing call issues that all the edge 20 and 30 phones are getting? Where you cannot make a call unless you reboot or turn off WiFi, which usually causes a reboot.
And when you turn WiFi off and on it reboots the phone...
Factory resetting does not resolve the issue but installing LineageOS does fix the issue. Sadly banks require so many workarounds now to work, and my fingerprint sensor still doesn't work but I know one of the Devs are working on it.
Sadly call quality for me is really bad on this ROM, next to unusable for me. I think it needs some kind of voice technology that's on the stock ROM but is missing from this ROM. But it's better than no calls so I'm running it for now.
Also I'm noticing very high WiFi latency spikes and packet loss jssues that was also an issue on the stock ROM. It uses the same drivers as the stock ROM so I guess that's expected. All other non Motorola devices are fine.
I take back what I wrote. After a few days working normally, Bluetooth became unstable again. For me Lineage has the same problem as the stock ROM. In my case, Wifi works perfectly both on stock and Lineage. But Bluetooth doesn't work properly on either of the 2.
Motorola drivers may not work for all Wifi and Bluetooth modules, as there may be hardware differences between devices. Anyway, it's a serious failure, due to complaints on websites, youtube, Telegram groups, etc... and the worst thing is that I haven't seen the problem acknowledged anywhere.
I do not recommend LineageOS for this device, WiFi/Bluetooth didn't get fixed and are features that is not fully workable as in stock rom. Also, Motorola has rollout the Android 13 stock rom and if you remove some bloatwares, I fully recommend it.