Database Develop

[Android] Shidell's Android 2.1 Eclair Port for the Vogue

Shidell's Android 2.1 Eclair Port for the Vogue​
After spending nearly every free hour of the last three weeks (and since 10:00 AM Saturday, it's now 5:40 AM Sunday.. so nearly the last 18 hours straight?) I've finally learned enough about linux and Android to present what I consider an excellent Eclair 2.1 port for the Vogue.
This port is based off of Manup456's work, and includes API level 7 support natively. I hope to be developing with Eclipse shortly, as I have other aspirations on an API-level for Android. (...I'm starting to think I have too many aspirations. )
But, before anything else...
Thanks to:
Plemen. Inspired me with his AOSP builds, and helped me in the very beginning with a few small questions.. just enough to get my feet wet.​
Zenulator. Provided literature in the form of guides not only on Android, but on ADB, internals, theming, and more--as well as answered questions. I'd still be researching what a binary file is in linux without Zen, let alone able to present this build now.​
Jamezelle. How many questions have you helped me with? lol. ​
dumbestcrayon. Showed me a fixed GenieWidget.apk from Nexus One, which I've incorporated into v1.1. Do something thoughtful, take a moment right now and send him a message on behalf of the MSM7k users, and thank him.​
tatnai. Thanks much for taking the time to assist people with this build, including ext2-related questions, and packaging it/making it available. ​
Also, thanks to all of you who have encouraged me both publically and privately to continue expanding. It is appreciated.​
Displaying the "Starfield" Live Wallpaper downloaded from the Market.
{
"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"
}
Features:
Android 2.1 Eclair (API: 7)
Android 2.1 sliding unlock screen
Voice/3G connectivity immediately upon first boot (give it a minute or so)--no reboot required
Nexus One boot animation
Updated wallpapers (including "Live Wallpapers"--Not yet functional, but incorporated)
Nexus One ringtones, notifications & alarms
Includes the latest GPS library improvement from Dzo (in testing, but appears to lock fast and be accurate as of 1-19-2010)
Extra software: Gmail & Mail clients, Market, Music, Corporate Calendar, GenieWidget (Nexus One Weather/Sports app. & widget), Gallery, YouTube (Nexus One) & Spare Parts
Limitations:
Bluetooth non-functional
Tethering (wired & wireless) unsupported by current kernel
Camera does not work
Voice Search/Dial isn't working (need an updated audio library for Eclair, but apps are included so once available, you can replace your .so library files and use them.)
Power collapse isn't completely working--this is an existing issue with Eclair builds and the current audio libraries
Notes:
Be sure to use the latest base files before attempting this build. GPS may not work unless using the 1-19-2010 NAND/zImage from Dzo's site. Dzo has made improvements to the kernel to help get more accurate results via GPS
LCD Density = 110 (for now, we're testing.) HaRET users be sure to set this manually; for NAND users, it's automatically incorporated.
I haven't tested this via HaRET, only via NAND--thus, I can't provide much support for ext2/HaRET users. if you do use HaRET, please report back on how this works for you, and try to assist others
This build basically fills the capacity of NAND's limits (about 88 mb. of data)--be patient when it's starting with the boot animation
This build contains both the standard English and Chinese input keyboards--long press on an input box (I.E. Text Message) and select "Android Keyboard" to set it to English
Please be sure to leave comments in the thread if you try this build. Thanks!
Download -- v1.0, 1-17-2010 (.ext2 and .sqsh links fixed):
System.ext2.zip
System.sqsh.zip​
Download -- v1.1, 1-19-2010 (.ext2 and .sqsh links fixed):
Removed: Voice Search, Voice Dial (without audio library support, they're just taking up precious space), Maps (easily available from the market, this chews up almost 5 mb. and I only have 88 to work with, so please download it post-setup), "Cube" Live Wallpaper (OK tech demo, but not very flashy. Pulled to save space.)
Added: Corporate Calendar )), Gallery3D instead of the original Gallery (a bit slower, please comment on your thoughts/preferences), GenieWidget App/Widget for weather/news from Nexus One, and YouTube from Nexus One. Additionally, I've packaged all of the Live Wallpapers from Nexus One. They aren't working yet, but once we've got the hold up cleared, I'll enable them.
Live Wallpaper: This is working, other than the Nexus One wallpapers. Search for "Live Wallpaper" on the Market, there's a few to pick from. I personally enjoy "Starfield".
GPS: The current GPS library incorporated with this build has debugging enabled, so it will write data to a file on your SD card. This shouldn't take up much space. You can remove this at will. This is simply a disclaimer and a notification of what to expect.
System_v1.1_1-19-2010.ext2.zip
System_v1.1_1-19-2010.sqsh.zip​
Download -- v1.2, 1-24-2010:
Removed: Gallery3D (Slow, doesn't run correctly)
Added: Original (2D) Gallery
GPS: Updated to use v1.5 of the GPS library, which is another monumental step forward. jnadke is making great strides in improving our GPS library, and Google Navigation should work nicely in this build.
System: Modified lcd density from 120 to 110; this allows for the Dialer and the Music application to fit the screen correctly, as well as provides for a bit more room in certain apps (like Messaging) which were previously crowded. This does cause some other apps to display things a bit awkwardly, such as Menus, which can cut off a bit of top text.
Give it a shot, and post your opinions. Thanks to tatnai for the recommendation.
system_v1.2_1-24-2010.ext2.zip
system_v1.2_1-24-2010.sqsh.zip​

Thanks for your hard work man.
Lookin forward to run this build.

Looking forward to using it. The download links look to point to the same file. Is this right? I'm looking for the SQSH.

going to give this a go with haret and post back, downloading now. will system.ext work with haret without ext2 partitions - i know, it's embarrassing, I have yet to partition my sd card; maybe I should do that today lol? also, is libgps.so actually included in the system file - I assume I have to load it in the rootfs using adb or terminal, right?
yeah, I think you were a bit tired, shidell, looks like your two links point to the same file, lol. strong work, thanks shidell, look forward to testing!
oh one last thing - tethering should work using PDAnet, I think it uses adb to do it, so as long as adb works it should.
EDIT: system.ext2 works fine with haret without partitions . . . that nexus boot animation sure is cool

Awesome work Shidell
Can you fix the dowload link for the sqsh file. It points to the ext2.
Thank you

I'd like to ask if the camera is working or not on this build.

Maybe someone can refresh my memory - is using the EXT file different from using the SQSH? Or can I just swap one of the other?

Are you saying that tethering via tetherbot doesn't work in this build?

Note from Tatnai
tatnai said:
sshark said:
Hey Tatnai, for Shidell's 2.1 port, what rootfs/initrd/zImage did you use?
I have NAND running on one phone so don't want to disturb that set up but as I am trying this using Haret for wife's phone, I need to know that...
Thanks,
sshark
Click to expand...
Click to collapse
using the 1/6/10a rootfs, using the 1/14/10 zimage, and the initrd.gz and haret from the latest basefiles 11/16/09 (first link).
ext2 extension is fine for use with haret and no partitions.
Click to expand...
Click to collapse

Any special conf needed?
And just use a standard vogue default text, set at what resolution? Thanks for any help.

Great work! It's so good to see someone else packing up systems for the community!
Contact me any time if I can help you with anything

a couple apps courtesy of zenulator, can't recall the link to his google code page, but included are calibration app, development app (use both to calibrate the screen), and modem app.

Shidell,
Two words.
Freakin awesome.

krwilson said:
Any special conf needed?
And just use a standard vogue default text, set at what resolution? Thanks for any help.
Click to expand...
Click to collapse
I keep getting cannot read default text from Haret??? Probably something stupid on my part. I have an Eclair build running so I do understand some of this. But if one of you great members could share what files you are using it would be most appreciated. Thanks.
Do you need rename the system.ext2 extension?
I am using the following:
rootfs-2010-01-06a
system.ext2
zImage-14-01-10
initrd.gz 16-11-09

Last message I see is "failed to allocate the storage". What am I doing wrong?
I run Eclair 2.01 now via Haret. I downloaded the latest linked zImage and rootfs.img. I have system.ext2 - previously I have always used SQSH.
Thoughts?

szman22 said:
Last message I see is "failed to allocate the storage". What am I doing wrong?
I run Eclair 2.01 now via Haret. I downloaded the latest linked zImage and rootfs.img. I have system.ext2 - previously I have always used SQSH.
Thoughts?
Click to expand...
Click to collapse
you are using rootfs from 1/7/10. this version does not seem to work with haret. use 1/6/10a.

Excellent work.
Can you please fix the link to the sqsh file in the first post?
It appears both go to the ext2 link.
Thanks

I have a running package of Shidell's eclair, if someone wants it, I can upload whole deal (zImage, default.txt, rootfs...etc.) somewhere. I don't have any filesharing account.

quick notes, running from sd card without partitions:
1. audio: was hopeful, but looks like we have to wait on lib.audio changes for voice search/dialer and speakerphone. question for those using sd card with partitions or nand and rootfs 1/7/10 - does speakerphone, voice dialer/search work for you? (and does rootfs 1/7/10 work for sd card w/ partitions?). may have to flash to nand if rootfs 1/7/10 fixes the lib.audio for eclair . . .
2. love the lock screen!
3. Market: just like donut, must first boot 320x480 to see all free apps in market. can then switch to 240x320. ideal lcd.density appears to be 110 at 240x320, this allows you to see what you are typing in Messaging, and allows the notification bar not to be screwed up (120 is fine for the notification bar, but you can't see anything you are typing in Messaging).
4. other: small enhancements here and there with 2.1 (dialer, contacts, haptic feedback, messaging, etc). i see accuracy noted now in maps without doing anything special, seems like the 1.3 libgps.so is in the system? haven't tried driving with it.
5. my orange sleep LED is not blinking. i don't think my phone is sleeping... I think this is why we don't have the wake-up problem (multiple presses to wake the phone up). have not tried the hacked zimage.
Great work Shidell! Love this build.

sshark said:
I have a running package of Shidell's eclair, if someone wants it, I can upload whole deal (zImage, default.txt, rootfs...etc.) somewhere. I don't have any filesharing account.
Click to expand...
Click to collapse
Please do upload if it's not too much trouble..........http://www.mediafire.com/ possible?
I have got this running finally! BUT, I have the keyboard with English letters but the text in the keyboard such as DONE or NEXT is coming up in some Asian language??? Just me, or anyone else find this?
So, if yours works correctly then please upload, thanks.
Great work Shidell, excellent. The only downside for me is no tethering, tried with PdaNet just to see, but fails.

[APP][4.0+][ROOT] BBQScreen

{
"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) =)

How do we fix the stuttering? Concerning the ~58.6hz refresh rate

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.

[APP][5.0+][Alpha] AA Passenger - Stream audio, control nav, show pics

AA Passenger
https://github.com/martoreto/aapassenger
What's this
With this app you can have two phones: one is the driver's phone, running Android Auto as usual.
Then you can have another one, e.g. handled by passenger. Passenger can then do 3 things:
play any music via car speakers (for now this requires root on passenger's device)
find some destination in Google Maps or another maps app and send it to Android Auto to navigate there
display pictures on the Android Auto screen (e.g. display how the hotel you're driving to looks like)
What's new
1.9-alpha9
AA Passenger: fixed Oreo crash
AA Passenger: fixed casting volume
1.9-alpha8
audio streaming, without root! (experimental)
audio streaming, without passenger app! (experimental)
works also with Hotspot active on the driver's device
AA Passenger now also available from Play Store
driver's app renamed to AA 2nd Seat
now compatible with Android 5.0 Lollipop
many bugs squashed
support for an NFC tag which launches or installs AA Passenger app
note that both driver's and passenger's apps must be updated to work together
Installation
https://github.com/martoreto/aapassenger/blob/master/README.md#installation
Screenshots
{
"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"
}

Can you describe some more what exactly you can do with this and how?
Can we install this android auto sdk somehow and use this?
Is it possible to have android navigation eg navigon running to a smartphone to display in android auto screen?
Thanks,
Sent from my SM-T700 using XDA-Developers Legacy app

Thanks for bringing additional functionality to AA!
I hope your SDK will bring more devs support for AA apps

sosimple said:
Can you describe some more what exactly you can do with this and how?
Click to expand...
Click to collapse
You mean this app or SDK? I assume app.
With this app you can have two phones: one is the driver's phone, running Android Auto as usual.
Then you can have another one, e.g. handled by passenger. Passenger can then do 3 things:
find some destination in Google Maps or another maps app and send it to Android Auto to navigate there
display pictures on the Android Auto screen (e.g. display how the hotel they're driving to looks like so the driver would easily find it)
play any music via car speakers (for now this requires root on passenger's device)
sosimple said:
Can we install this android auto sdk somehow and use this?
Click to expand...
Click to collapse
The SDK itself is for developers. It allows writing new Android Auto apps.
It rather won't help much in modifying existing apps to run on AA, as the logic behind AA apps is quite different than for normal apps.
The SDK is used like any other Android library.
I published an example demo project (linked in README) which shows how.
sosimple said:
Is it possible to have android navigation eg navigon running to a smartphone to display in android auto screen?
Click to expand...
Click to collapse
It is somewhat possible, for example by creating a new Andoid Auto app which mirrors the screen of the phone on the car screen and then somehow circumvents the fact that Android Auto displays its own graphics on the phone screen.
It's also possible to modify an open-source navigation app (I'm experimenting with OsmAnd recently) and implement the Android Auto functionality.

Many thanks for description. Very good. I would pay for an app mirroring passenger screen to android auto screen.. (showing anything passengers screen shows, video, navigation, etc).
I think many others would like this, if anyone could implement it..
Sent from my SM-T700 using XDA-Developers Legacy app

Any ideas for what other things than navigation, watching videos while stopped and dangerously distracting the driver while driving would this be useful?

Hi Martoreto
Thank you for your work and for the SDK. I tried to you your passenger app now. But I have to say I failed. I don't have rooted my phones yet, but you wrote to send (push) pictures should be possible right? Currently for me it is just possible to send a point in maps. Other than that if I try to send a picture with printscreen it shows "sent to Android Auto" but in Android Auto happens nothing than 1 second of black mirror. I think to push pictures no root is needed right?
Thanks for replay

Sissi1991 said:
Hi Martoreto
Thank you for your work and for the SDK. I tried to you your passenger app now. But I have to say I failed. I don't have rooted my phones yet, but you wrote to send (push) pictures should be possible right? Currently for me it is just possible to send a point in maps. Other than that if I try to send a picture with printscreen it shows "sent to Android Auto" but in Android Auto happens nothing than 1 second of black mirror. I think to push pictures no root is needed right?
Thanks for replay
Click to expand...
Click to collapse
Hi @Sissi1991, thanks for trying the app.
I see good news that you established the wireless connection successfully, which was one of the major concerns I had with the app.
You're right, sending photos should work without root. I saw another report in the SDK thread, when the example app could behave similarly.
Just to make sure it's the same: when you take the screenshot, the screen on Android Auto becomes black for about a second, and then appears the AA home sceen?
Also, does the same happen when trying to send some other picture than a screenshot (like Gallery -> <some photo> -> Share -> Send to Android Auto)?
A note about rooting: it's required only on passenger's device (to make audio work).

@Sissi1991, feel free to try the new release:
https://github.com/martoreto/aapassenger/releases/tag/0.9-alpha2

Couldnt make it work also, same problem as Sissi (tested the previous 0.9 alpha 1 version only)
If sending a picture from gallery, it gives an error 'error resizing image'

Kill Me said:
Couldnt make it work also, same problem as Sissi (tested the previous 0.9 alpha 1 version only)
If sending a picture from gallery, it gives an error 'error resizing image'
Click to expand...
Click to collapse
Ok, this looks like another issue and alpha 2 rather won't make any difference here.
This error shows on the passenger's device, right?
If possible, please PM me links to:
- Android bugreport captured after this error (Settings -> Developer options -> Take bug report)
- The picture which failed to send
Thanks for trying this out.

Thanks for developing such a great idea
Don't know what I am missing, I can't pair my two phones, even though they are connected through wifi direct, the app apparently can't see this connection :s
Enviado de meu Nexus 6P usando Tapatalk

@Sissi1991, @Kill Me, here's 0.9-alpha3 with "error resizing image" fixed. Give it a try!
https://github.com/martoreto/aapassenger/releases

bladerj said:
Don't know what I am missing, I can't pair my two phones, even though they are connected through wifi direct, the app apparently can't see this connection :s
Click to expand...
Click to collapse
Yeah, I expected that Wifi Direct may have some connection issues. Nevertheless, please do this:
On driver's device open "AA Remote Settings" -> "Enable discovery".
On passenger's device open "AA Passenger"; if the setup wizard shows up, go to the "Pairing" page.
Wait 5 minutes.
On both devices, capture Android bug reports, upload them somewhere and PM me the links.

Thank you, ill give it a try.
Pairing through Wifi direct isnt indeed ideal and it takes a while to get connected, i get why using 'passenger' smartphone, but as the driver is driving the passenger could use the connected AA phone i think

@martoreto installed and tested new version! Works perfect. Keep on your good work!

Kill Me said:
but as the driver is driving the passenger could use the connected AA phone i think
Click to expand...
Click to collapse
Just my 3 cents on this idea: some things can be done with this AA-connected phone, and this doesn't need any special app mostly.
I don't know how it is on other phones, but on my HTC One M8 I can open any app even when AA is connected using tricks like opening notifications drawer, going to Settings, Apps etc.
But even then Maps can't be open on both AA and the screen. It can't render at the same time to 2 destinations.
Then, fiddling with the cable can easily disconnect the nav.
That's why I go with the idea of using the passenger's phone, with his/her music library, maps favourites, bookmarks, whatever context etc., to make car travel a more "together" experience.

Let me announce a new major release: 1.9-alpha8
It has two new main features, namely:
Audio streaming without root, as rooting was rather a major blocker for
this feature to be useful.
Hotspot mode. Now the apps don't rely on Wi-fi Direct only (but it's still supported).
They will work also if the passenger's device is connected to the hotspot started
on the driver's device.
Full release notes:
audio streaming, without root! (experimental)
audio streaming, without passenger app! (experimental)
works also with Hotspot active on the driver's device
AA Passenger now also available from Play Store
driver's app renamed to AA 2nd Seat
now compatible with Android 5.0 Lollipop
many bugs squashed
support for an NFC tag which launches or installs AA Passenger app
Note that both driver's and passenger's apps must be updated to work together.
Enjoy!

1.9-alpha9
AA Passenger: fixed Oreo crash
AA Passenger: fixed casting volume

Deleted

[Win/Mac/Linux] One-Click Custom Rom installer

Hey guys, I'm looking for some testers for my Free-Droid application. It is available for Windows, Mac and Linux and is perfectly compatible with the Galaxy S5.
This software should be most useful to people new to custom rom installation. It takes from you the hassle of looking for TWRP and a Rom, it downloads everything for you (including magisk, microG and F-Droid) and does all the flashing on autopilot. For those users starting from scratch, it also helps setting up the drivers on windows machines.
{
"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"
}
You can download the application from the original/general thread here.
Feel free to leave some feedback or suggestions for improvement.

@imska have already posted on your main thread. .....
As far as the "Odin" look. Well, Odin, is much easier to read. Seems that some things, are Under others. As if the display is 1 size, with more info to actually have space for. (e.g. In Expert- towards the bottom , " -install google sync" is actually, Under the words "Only change these setting if you really know what you are doing" ! So yes, need to clean up this Free-Droid a bit.
What is confusing a bit, is where to work and where to look. Terminal has all the major things running like Passwords, IS the phone connected, etc.
one more Issue... Info- Sprint Galaxy S5 (SM-G900P Sprint KTLEDV ); Currently, Running LineageOS 16.0 (build date 22Jul19) w/Magsik!
Terminal says I am running a custom Rom. The Free-Droid Windows says that it does not know how to deal with my phone....
So Do I take that it only works with "Stock" images?
Oh, On Github, I did not see the galaxy S5 code name KTLEDV in your approved list??? could that be the issue here? Just not added into the system?
Hopefully you can get this cleaned up. Willing to try test it out again.
Just give me a shout, when you have a newer build out....
Tanx

Thanks for testing!
It does not need a new build to fix device detection... I did not know of a SM-G900P variant of the S5, but I just added it to the codename lookup table. Now it should recognize your device as the kltedv and know how to deal with it. The tool finds LineageOS, RR and AEX for the kltedv
Unfortunately, there is no official release of TWRP for kltedv and therefore Free-Droid will not be able to install stuff if a user is still running stock rom. Which TWRP do you use and where can I find it?
About the terminal output:
The stuff that gets printed there is just logging. You can just ignore it. A terminal window does not even open on windows or mac. Entering sudo password in terminal is only relevant for linux users and could only be avoided by setting up udev rules...
The "running custom rom" detection is there for the tool to decide whether to look for a TWRP image or not. So in your case, the tool should work now. For other kltedv users running stock, I will need to add a TWRP image to my archive.
Window layout / text positioning:
I have no idea why things do not display like in my screenshots... Can I send you a .jar to test if the layout is better?

imska said:
Thanks for testing!
Window layout / text positioning:
I have no idea why things do not display like in my screenshots... Can I send you a .jar to test if the layout is better?
Click to expand...
Click to collapse
Hey there! Please, was not "*****ing nor Complaining" about your app. Had read this thread, and the Link to another. Only had 1 person say it worked. I am always on the lookout for just about anything, that makes me life a bit easier!
Was on me laptop, Toshiba P55 (15" 1080 screen, no touch, 4th gen i5, 16GB Ram, and 1TB SSD running upto date Ubuntu 18.04.02) and was not running any other programs ( I had seen that I would have to use Terminal for password. That's OK with me, like a bit of control. Had some error there, popped up twice, both times trying to run it. Before asking about password. Everything seemed OK from there.
But the layout was not as Pictured in Pic 3, in the OP.
Oh, me phone. Actually I am on Virgin Mobile, which is that same the Galaxy S5 from Sprint on same network. TRWP, currently on build 3.2.2, there is a newer build out, but this still works well, believe it came out back March or April of this year.
I just thought, that it needed a bit better layout, so others, do really get into a mess by missing a line or 2. That would stink!
IF you would like me to test something, I am "OK" with that. Just send through PM message.
I can see, how this really can be nice, am not sure where it looks for ROMs and such.

godofsalt said:
Hey there! Please, was not "*****ing nor Complaining" about your app. Had read this thread, and the Link to another. Only had 1 person say it worked. I am always on the lookout for just about anything, that makes me life a bit easier!
Was on me laptop, Toshiba P55 (15" 1080 screen, no touch, 4th gen i5, 16GB Ram, and 1TB SSD running upto date Ubuntu 18.04.02) and was not running any other programs ( I had seen that I would have to use Terminal for password. That's OK with me, like a bit of control. Had some error there, popped up twice, both times trying to run it. Before asking about password. Everything seemed OK from there.
But the layout was not as Pictured in Pic 3, in the OP.
Oh, me phone. Actually I am on Virgin Mobile, which is that same the Galaxy S5 from Sprint on same network. TRWP, currently on build 3.2.2, there is a newer build out, but this still works well, believe it came out back March or April of this year.
I just thought, that it needed a bit better layout, so others, do really get into a mess by missing a line or 2. That would stink!
IF you would like me to test something, I am "OK" with that. Just send through PM message.
I can see, how this really can be nice, am not sure where it looks for ROMs and such.
Click to expand...
Click to collapse
No hurt feelings. Can you please replace the Free-Droid.jar file in the "bin" folder of the application with this one and report back if the layout in the expert pane is still messy? And you could help me investigate the issues on startup if you click "Report bug" in the help pane of the application and send me the created zip with the log files.
Thanks

@imska
You asked about an email. Did you want that sent through the link on your other thread (something like bug at Free-Droid) Or a PM here through XDA?
Asking, ahead of time, have yet tested. Will be very soon, but, because I am not sure where to send you an email.
Tanx
Edit- Forgot to throw Git-Lab into the mix, as places to report any sort of Bug. (yep, I always try and look up what ever Srcipt, On Github, Git-Lab, and/or LineageOS Gerrit!)
Tanx Again.

godofsalt said:
@imska
You asked about an email. Did you want that sent through the link on your other thread (something like bug at Free-Droid) Or a PM here through XDA?
Asking, ahead of time, have yet tested. Will be very soon, but, because I am not sure where to send you an email.
Tanx
Edit- Forgot to throw Git-Lab into the mix, as places to report any sort of Bug. (yep, I always try and look up what ever Srcipt, On Github, Git-Lab, and/or LineageOS Gerrit!)
Tanx Again.
Click to expand...
Click to collapse
Send it however you prefer. Thank you.

Version 0.7.0 released
stability improvements
fixed a few bugs
added button to rescan for roms
added driver installation help button
preparing ability to choose MoKee and /e/ rom
support for oneplus devices
Happy flashing!

OH man.....
Seems rather S L O W... on the download. 2 days trying to get their Latest Free-Droid......and counting!!!
Always get "Timed out" by there Sever, just trying to get the darn thing!
Still working on it! let ya all know when and if it goes....or comes

I'm sorry but after a short power shortage in the building, the server is not reachable. Since I will not get back home before the weekend, there is nothing I can do for now. I am pretty sure to have that solved on Saturday though, so patience please.

Problem fixed, sorry for the downtime...

Hi,
I'm looking to install the kitkat 4.4 os onto my samsung galaxy s5 and was very excited to see your new app written for people like me with not much experience in doing this sort of thing.
I thought it would be a good idea as there is a lot of apps on my phone that i don't use and I can't uninstall them and I'm running out of room.
Unfortunately this program couldn't detect my phone after plugging it in to my computer via usb and following the instructions to turn on debugging via usb.
Here are my phone and machine specs:
samsung galaxy s5
SM-G900I
Android Version 6.0.1
Baseband version G900IDVU1CQD1
I'm using windows 7 to install
Any help would be appreciated.
Cheers.

Alright. I am a noob that has been reading the forums for a long minute. I have no idea what I am doing as far as flashing, rooting and customization goes... and I need to learn. So instead of using my S8+ I have decided to use my old beloved S5 as my test subject to try and understand what is what ect, ect, ect.
Is this a good place to start? I have a MacBook Pro I can use and/or a Lenovo with Windows 10 that I can use as well. I guess I am hoping that maybe I can get a Thumbs up from someone that this may be a good place to start.
I can do my best to report any thing back if it might help...
Thanks.
Sent from my Samsung Galaxy S8+ using XDA Labs

Fellofftheporch said:
Alright. I am a noob that has been reading the forums for a long minute. I have no idea what I am doing as far as flashing, rooting and customization goes... and I need to learn. So instead of using my S8+ I have decided to use my old beloved S5 as my test subject to try and understand what is what ect, ect, ect.
Is this a good place to start? I have a MacBook Pro I can use and/or a Lenovo with Windows 10 that I can use as well. I guess I am hoping that maybe I can get a Thumbs up from someone that this may be a good place to start.
I can do my best to report any thing back if it might help...
Thanks.
Click to expand...
Click to collapse
It depends on what you aim for... If you just would like to install lineageos on your S5 then you're welcome to use free-droid for that. If you would like to really understand what everything means and how things work, I think free-droid might not be the right starting point, because it is meant to hide all the (more or less) complicated stuff from the user and make the installation as easy and convenient as possible.
If you choose to use it and something does not work as expected, you're welcome to report back here.

3DRea said:
Hi,
I'm looking to install the kitkat 4.4 os onto my samsung galaxy s5 and was very excited to see your new app written for people like me with not much experience in doing this sort of thing.
I thought it would be a good idea as there is a lot of apps on my phone that i don't use and I can't uninstall them and I'm running out of room.
Unfortunately this program couldn't detect my phone after plugging it in to my computer via usb and following the instructions to turn on debugging via usb.
Here are my phone and machine specs:
samsung galaxy s5
SM-G900I
Android Version 6.0.1
Baseband version G900IDVU1CQD1
I'm using windows 7 to install
Any help would be appreciated.
Cheers.
Click to expand...
Click to collapse
If you are on windows then this is very likely a problem with drivers. Have you tried the "still not detecting" link below the instructions?

For those of you who also own a Sony device: Free-Droid is now compatible with Sony devices!
0.7.5 update should also fix an issue for some variants of the Galaxy S5 like the kltedv (SM-G900P)