Related
Hi, first post here & I did search for an answer first
I'm trying to add a menu to my app, in my onCreateOptionsMenu method I can use
menu.add(0, 1, 0, "Text1");
menu.add(0, 2, 0, "Text2");
etc
It works OK & when I press the menu key it pops up, the onOptionsItemSelected method correctly detects the item selected.
If I try to use the MenuInflater on an XML file, it does not work. When I press the MENU key, it pops up a menu with blank buttons - no text or icons & the number of buttons corresponds to the number of ITEM entries in my XML. The XML looks valid .
Any ideas where I'm going wrong. I would paste the code, but the forum says I cant until I've made more posts.
Thanks.
Still new to this myself, but in my recent menu tries, i had to put in a TextView into the xml to tell it what to say.
<TextView
android:text="@string/menu_button1" />
And define the name you want on that button under the strings file.
<String name="menu_button1">New Game</String>
I may be completly off so take what Im saying with a grain of salt lol
Hmmmm, tried that & it didnt work either. Thxs for the suggestion.
Not a problem the book i have at home had me do some menus, i could post the books complete code later maybe i missed something with what i told you. Its in pdf form so it wouldnt be a big deal. Ill be getting home in around 3 hours.
Maybe its a combination of button and textview together to actually make it work. It was pretty easy last time i did it so im sure its just a small detail being missed. I've slowly learned eclipse isnt able to catch every single error.
is your menu's xml file in the res/menu folder? if not it prob wont work
Yup res/menu
Here is the code for the menu from my book.
Code:
<?xml version="1.0" encoding="utf-8"?>
<LinearLayout
xmlns:android="http://schemas.android.com/apk/res/android"
android:background="@color/background"
android:layout_height="fill_parent"
android:layout_width="fill_parent"
android:padding="30dip"
android:orientation="horizontal" >
<LinearLayout
android:orientation="vertical"
android:layout_height="wrap_content"
android:layout_width="fill_parent"
android:layout_gravity="center" >
<TextView
android:text="@string/main_title"
android:layout_height="wrap_content"
android:layout_width="wrap_content"
android:layout_gravity="center"
android:layout_marginBottom="25dip"
android:textSize="24.5sp" />
<Button
android:id="@+id/continue_button"
android:layout_width="fill_parent"
android:layout_height="wrap_content"
android:text="@string/continue_label" />
<Button
android:id="@+id/new_button"
android:layout_width="fill_parent"
android:layout_height="wrap_content"
android:text="@string/new_game_label" />
<Button
android:id="@+id/about_button"
android:layout_width="fill_parent"
android:layout_height="wrap_content"
android:text="@string/about_label" />
<Button
android:id="@+id/exit_button"
android:layout_width="fill_parent"
android:layout_height="wrap_content"
android:text="@string/exit_label" />
</LinearLayout>
</LinearLayout>
And the strings file
Code:
<?xml version="1.0" encoding="utf-8"?>
<resources>
<string name="app_name">Sudoku</string>
<string name="main_title">Android Sudoku</string>
<string name="continue_label">Continue</string>
<string name="new_game_label">New Game</string>
<string name="about_label">About</string>
<string name="exit_label">Exit</string>
</resources>
Thats pretty close to what I'm doing, but not exactly. The main difference seems to be your using a LinearLayout & my code uses RelativeLayout. OK, I'll try your code EXACTLY when I get home later. Thanks.
When you say menu, you are referring to the options that pop up when you press the hardware menu button, right?
I ask because... what does that linearlayout code have to do with a menu?
Are you implementing this function?
onPrepareOptionsMenu(Menu menu) {
MenuItem option 1 = menu.findItem(R.id.opt1);
...
}
I thought the Layout may affect how the menu text & icons were displayed & was why I couldn't see them.
No I dont implement onPrepareOptionsMenu, only onCreateOptionsMenu and onOptionsItemSelected - I'd post my code but the forum wont let me yet
I'm following the example from Android Developers "Creating Menus" which only has those 2 methods detailed.
OK guys I've fixed it !!! You'll never guess what it was.......
.... OK, I'll tell you then
In my menu.xml, I had the menu namespace xmlns URI as https not http, I had copied & pasted this from another website. Changed it back & we are working again.
Thanks for the assist - Thanks have been awarded.
Oh man thats a killer...I've had that happen to me a couple of times already
Good example android.text instead of android:text...lol
Glad to here its working though,good luck with the rest of your app.
lol - I either need more or less caffeine - not sure which.
Thanks bud.
I am making a game that has a main.xml view (the default one that the game screen is made from. But I have a button for "help" that starts a new view which is just text explaining how to play the game. But I want to add a button to the help menu that will take the user back to the main game. Only problem is when I add a button to the xml file for it, it always crashes as soon as it is called. All the other buttons work fine in main.xml but I cant get the ones in the help.xml to work. Any suggestions?
The way that android's view hierarchy works is actually kind of complicated, and is one thing that I still at times struggle to grasp.
So when you press the help button, and help.xml is supposed to show up, it crashes?
yeah, heres my xml code:
<?xml version="1.0" encoding="utf-8"?>
<ScrollView
xmlns:android="http://schemas.android.com/apk/res/android"
android:layout_width="fill_parent"
android:layout_height="fill_parent"
androidadding="10dip" >
<TextView
android:id="@+id/about_content"
android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:text="Text goes here" />
</ScrollView>
But it crashes if theres a button inside of it
are you using the new layout in the same Activity or a new one? If the same, try out making a new Activity class (remember to add it to manifest!), it might be a lot easier to then determine your problem if it's separate.
We could do with a logcat output of the crash to help determine what's wrong
I just started to build my app's layout and I'm confused, so I could use a little help.
I want it to look like this:
- there's a bar with buttons which always stays on the bottom of the screen (like position:fixed in CSS)
- there are two (or more) lists with a dynamic number of records which will mos definitely overgrow the screen size, so I need a scrollbar on them. These will not push down the button bar.
This is easy as hell, I know, but I'm not sure how to do it properly so I won't need to change it later.
It's all about learning to love (and hate) RelativeLayout
http://blog.maxaller.name/2010/05/attaching-a-sticky-headerfooter-to-an-android-listview/
Yeah, should just be a ScrollView with a nested RelativeLayout putting your buttons on the bottom...not too painful
I have a problem with my ListView. I want it to be full size without a scrollbar (the parent of ListView is scrollable), but it shows up really short (only 1.5 rows fit in). Here's my code :
Code:
<ScrollView
xmlns:android="http://schemas.android.com/apk/res/android"
android:layout_width="fill_parent"
android:layout_height="fill_parent"
android:layout_below="@id/top_controlbar"
android:layout_above="@id/bottom_controlbar">
<LinearLayout
android:layout_width="fill_parent"
android:layout_height="fill_parent"
android:orientation="vertical">
<!-- GEOTASKS -->
<LinearLayout
android:id="@+id/geotasks_layout"
android:layout_width="fill_parent"
android:layout_height="wrap_content"
android:orientation="vertical"
android:layout_marginTop="10dp"
>
<TextView
android:layout_width="fill_parent"
android:layout_height="30dp"
android:text="@string/main_header_geotask"
android:textSize="18sp"
android:background="@color/header_bg"
android:textColor="@color/header_text"
android:gravity="center"
android:layout_marginBottom="5dp"
/>
<ListView
android:id="@+id/list_geotasks"
android:layout_width="fill_parent"
android:layout_height="fill_parent"
/>
<TextView
android:id="@+id/empty_geo"
android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:text="@string/main_empty_geo"
android:textSize="15sp"
android:paddingLeft="5sp"
/>
</LinearLayout>
etc, same for timed and simple tasks
I tried changing the height of the parent layout and the listLayout (all 4 combinations), but it didn't help.
Well **** my rusty sheriff's badge. I can't believe nobody knows the answer.
ScrollViews are weird. The way they stretch to fill content is not intuitive.
I can't remember the solution off the top of my head but do some googling for "ScrollView" and I think there are some answers on stackoverflow.
hth
My problem is not the scroll view, but ListView. Scrollview stretches without problems.
I want to achieve a simple thing - make the ListView display all of it's content without scrolling. How is that not possible ? OMG
At first I used LinearLayouts and added new views to the root layout. That was very ugly and I couldn't register those views for context menus. Then I found out about list views, and I couldn't be happier if I could just do this one thing.
Sorry I misunderstood what you were asking.
What's the point of having the parent of a ListView scrollable anyways? I think you're just thinking about things in a strange way and that what has got you stuck.
ListView has an addHeaderView() addFooterView() if you need static items at the top and bottom, and you know how to put bottom and top control bars using relative layout, why not eliminate the ScrollView?
I think you're making things difficult on yourself by putting something scrollable inside something scrollable.
Your other option is to use views like you were using them, they do support context menus: http://developer.android.com/reference/android/view/View.OnCreateContextMenuListener.html
Hope that helps.
Edit: btw, the reason I am recommending it this way is that even if you override ListView's onTouchEvent, I dont think it will expand to wrap all the content and be scrollable by the ScrollView. Instead it will just sit there as an unscrollable listview that leaves the user unable to reach the content beyond what they can see originally.
So im following this guys tutoirals:
http://www.youtube.com/watch?v=7OSfxz0iWkI&list=PL4695D1A275CDEE4A
(Watch 1.12 and 1.13)
I understand all of those concepts he used but Im still confused about the android:weight and android:weightSum functions (if that's what you call them). Could someone give a explanation on what they mean?
TwilightLoz said:
So im following this guys tutoirals:
http://www.youtube.com/watch?v=7OSfxz0iWkI&list=PL4695D1A275CDEE4A
(Watch 1.12 and 1.13)
I understand all of those concepts he used but Im still confused about the android:weight and android:weightSum functions (if that's what you call them). Could someone give a explanation on what they mean?
Click to expand...
Click to collapse
It defines how the space which is left after calculating all view sizes is used.
Code:
<Button ...
android:layout_weigth="1" />
<Button ...
android:layout_weight="1" />
The space left over is divided by two and every view will get the half of it.
Code:
<Button ...
android:layout_weigth="1" />
<Button ...
android:layout_weight="2" />
The second button will get twice as much space as the first one.
Weightsum is not necessary. It can define the sum of all weight attributes.
Notice that this just splits the space which is left over.
If you want one View to get a third of the total space and the other two thirds of the space, use this:
Code:
<Button ...
android:layout_weigth="1"
android:layout_width="0px" />
<Button ...
android:layout_weight="2"
android:layout_width="0px" />
Nikwen hit right on the money. As he said, weightsum isn't necessary but is used to define the accumulative weight of its child views. Then each child of said parent view,will have a weight defined to it, adding up to the parent's weightsum. Basically its saying, take up this percentage of parent view.
Sent from my SPH-D710 using Tapatalk 2
Last updated: 2023-05-11
DAB-Z v2.x thread is here
This thread is discussing the (now "legacy") DAB-Z v1.x versions...
Release notes of currently active release on Google Play 1.9.127
Release notes of currently active PUBLIC BETA on Google Play: 1.9.127
If you want to become beta user, subscribe in Google Play or open this link from the device : https://play.google.com/apps/testing/com.zoulou.dab
The app is available in Google Play named DAB-Z with package name "com.zoulou.dab".
It can be installed in parallel to any original preinstalled DAB+ Player.
Get DAB-Z on Google Play
Get previous versions on Apkpure
Compatible devices:all DAB USB dongles with VID/PID = 16C0/05DC (decimal 5824/1500) ("VOTI", "Van Ooijen Technische Informatica", "shared ID for use with libusb", "[email protected]")
Examples (for sure not complete!)
XTRONS USBDAB01
Joying DAB+
Pumpkin Y0251
Hotaudio Dasaita DAB+
(and dozends or hundreds more, they are all quite the same, if not equal.)
Use this link to find out more
NOT SUPPORTED:* Any SDR ("Software Defined Radio") devices (e.g. based on Realtek RTL2832U R820T)
* Fulljoin adapter
* Dension DAB+U
* Dasaita DAB box
Frequently asked questions FAQ:DAB-Z's expected behavior regarding Play/Pause, Mute/Unmute, Navi App announcements
Q: Does DAB-Z support fallback to FM Radio?
A: No and it is not planned due to technical reasons.
Q: Why do some stations appear several times in the list but have all the same content?
A: This is an annoying behavior of the broadcasting stations. DAB-Z does not lump them together to give the user the choice to pick one into the favorites list that has the best signal strength.
Q: Is it possible to add a sort of buffer to bridge short reception outages and therefore interruptions of audio, e.g. while driving through a tunnel?
A: No. DAB is a real-time, live (but digital) broadcast (same as old-style TV and FM radio), in contrast to streaming. The broadcasted data that is lost due to missing reception cannot be recovered or re-requested later. Also, DAB cannot be read-ahead in contrast to streaming. An app therefore cannot create a buffer of "future" data in order to have data locally, which can then be used to bridge the loss of reception.
For testers ...... that want to actively support me and help everyone to have a better DAB-Z app:
If you encounter an issue with DAB-Z, I will maybe ask you to provide a) logcat logs or b) raw recordings.
a) logcat logs are created by pressing the logcat button in DAB-Z Settings -> Info (at the very bottom)
A zip file is created and you will be able to choose what to do (send via Email, add to Google Drive, etc...). Get this zip file to me somehow.
If I additionally ask you to enable "OMRI verbose logging", then follow these steps before creating the logcat as above:
1. Enable Developer Menu: tap 7x on DAB-Z Settings->Info->Version , then go back, a new menu item appeared "Developer options" at the very bottom
2. Enable OMRI verbose logging
3. Close DAB-Z
4. Reopen DAB-Z
... reproduce the issue ...
5. Create the logcat DAB-Z Settings -> Info (at the very bottom)
b) raw recording are created by this procedure:
raw recordings are done using this procedure:
1. Enable Developer Menu: tap 7x on Settings->Info->Version , then go back, a new menu item appeared "Developer options" at the very bottom
2. Enable OMRI raw recording (you don't need to activate verbose logging)
3. Close DAB-Z (raw recording enable/disable requires a restart of DAB-Z)
4. Reopen DAB-Z
... reproduce the issue ...
6. Go to DAB-Z Settings and disable OMRI raw recording. Restart DAB-Z again.
Afterwards, files with ending .raw exist in:
<internal memory>/Documents/DAB/rec/
Download them all from the head unit, zip them and send to me.
YHX-DAB+V170425_zoulou-20170521
Updated version YHX-DAB+V170425_zoulou-20170521
Change log:
- Some icons by cruiser12 (china-rns.com)
- Avoid repeating USB permission request on Android 6
{
"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"
}
Been looking for an alternative dab+ app and you have created a great looking app. Just installed the new version looks so much better than the original, not keen on the green though if I'm being picky.
The problem I had with the original dab+ app was the signal would be full then completely drop out and I would have to close the app and then reopen to get the station to play. This could happen 4 or 5 times during my 20 minute journey to work, it was so annoying I've used FM radio for months.
I have had only one dropout so far with your updated app so far so good. Many thanks for all your hard work hope to see more improvements.
Sent from my HTC One M9 using Tapatalk
I really appreciate this effort! Obvious that whoever makes the original app doesn't know anything about how DAB works and what features users want. Will download your latest patched version and try using DAB again. I've relied on internet radio instead as the original app is close to useless with the horrible reception and crap interface.
Hey Zoulou many thanks for the great app.
Is it possible to get station logo to show in UK ?
Thanks
I am sorry that the slideshow feature (aka station logos) does not work in UK. However, I am unable to fix this, because decoding of the slideshow is done inside a libdab.so, which I am unable to change. I can only do changes in Java code and on the layout.
I assume that your original DAB+ App also does not show any station logo, right? I suggest then you contact your dealer and tell that the DAB App that comes with the device (or stick) does not show any station logo. The only chance to get this fixed is to report these bugs to the guys that develop this piece of crappy DAB App.
Great that you are trying to make this crappy app a bit better. In the past i made some modifications in the layout in this app for myself. I also found some icons or code which pointed in the direction of adding favorite radiostations. They never integrate it. Can you make this?
I also tried to integrale a lockscreen in this app, so Automate Will show the radiostation picture when playing. Unfortunatly i couldnt het It to work. Maybe you can look at it of you have the time.
Keep up to good work. Looking forward to your next release!
Hi thank you very much for your release!
With the version shipped by malaysk rom I had real problems. Every time the app was moved to background playback began to stutter...
This issue is now gone! Thanks!
One small request: Could you add a higher resolution app icon? The current one looks pretty crappy since the resolution is too low.
Thank you!
Can you show a screenshot of what you mean with the too low resolution icon?
The icon an text is very blurry. see the attachment
Another question, could it be that the app doesn't display images which a transmitted by the station?
freii said:
The icon an text is very blurry. see the attachment
Click to expand...
Click to collapse
You are right. I will change the icon in my next release. I don't have this icon in a higher resolution.
freii said:
Another question, could it be that the app doesn't display images which a transmitted by the station?
Click to expand...
Click to collapse
Some stations broadcast a complex slideshow (aka station logo), which this app cannot decode. Example: Bayern 3. Whereas Antenne Bayern is decoded fine. (I see you are from Bamberg )
Thank you.
The application works fine, but as with all the applications I have tried, I have no signal on my Erisin ES6046B.
realzoulou said:
Some stations broadcast a complex slideshow (aka station logo), which this app cannot decode. Example: Bayern 3. Whereas Antenne Bayern is decoded fine. (I see you are from Bamberg )
Click to expand...
Click to collapse
Ah okay I will check that out.
Just noticed because on my RK3188 device on "Radio Galaxy" the covers of the currently playing track was displayed.
Switched over to a PX5 device now and installed your mod right away because of the stuttering in the default app. So I don't really know if it would have worked with the default malaysk px5 app.
But this isn't that important to me, just noticed that it isn't working anymore.
---------- Post added at 14:18 ---------- Previous post was at 14:17 ----------
macandnews said:
Thank you.
The application works fine, but as with all the applications I have tried, I have no signal on my Erisin ES6046B.
Click to expand...
Click to collapse
Which usb dongle are you using and what kind of antenna?
freii said:
Which usb dongle are you using and what kind of antenna?
Click to expand...
Click to collapse
I have this tuner DAB + USB with the antenna delivered with that I put on the roof of my car to give a try.
http://www.ebay.fr/itm/162249572594?_trksid=p2057872.m2749.l2649&ssPageName=STRK%3AMEBIDX%3AIT
I have the same USB receiver.
But I replaced my antenna on the roof with this one: https://www.amazon.de/gp/product/B00IRWQ06G/ref=oh_aui_search_detailpage?ie=UTF8&psc=1
Because all the other antennas I tried didn't work. Now with this antenna I have full reception nearly all the time.
Chapeau!!!
Great work so far.
I just have the same issue with the original app, that the album pic is too small. This seems to be related to my screen size/DPI settings on my device.
I am using an Android TV box which is connected by HDMI to my Pioneer AppRadio SPH-DA110.
The pioneer has a 7" display and the DPI settings of my box is set to 480DPI.
My solution was to change some settings in the player.xml:
Code:
<?xml version="1.0" encoding="utf-8"?>
<LinearLayout android:orientation="horizontal" android:id="@id/relative_layout_main" android:background="@drawable/backgroud2" android:layout_width="fill_parent" android:layout_height="fill_parent" android:baselineAligned="false" android:weightSum="10.0"
xmlns:android="http://schemas.android.com/apk/res/android">
<LinearLayout android:orientation="vertical" android:id="@id/left_area" android:layout_width="fill_parent" android:layout_height="fill_parent" android:layout_marginLeft="10.0dip" android:layout_weight="4.0">
<LinearLayout android:orientation="horizontal" android:layout_width="fill_parent" android:layout_height="wrap_content" android:layout_marginLeft="10.0dip">
<LinearLayout android:gravity="center|left" android:layout_width="fill_parent" android:layout_height="fill_parent" android:layout_weight="9.0">
<ImageView android:layout_gravity="center|left" android:id="@id/signal_level" android:layout_width="wrap_content" android:layout_height="wrap_content" android:layout_marginTop="0.0dip" android:src="@drawable/signal_0" android:contentDescription="@null" />
<Button android:gravity="center_vertical" android:id="@id/bt_record" android:background="@drawable/record_start_selector" android:visibility="gone" android:layout_width="wrap_content" android:layout_height="wrap_content" />
</LinearLayout>
<LinearLayout android:gravity="center" android:layout_width="fill_parent" android:layout_height="fill_parent" android:layout_weight="1.0">
<TextView android:textSize="16.0sp" android:textColor="#ffffffff" android:id="@id/service_name" android:layout_width="wrap_content" android:layout_height="wrap_content" android:text="@string/service_name" />
</LinearLayout>
</LinearLayout>
<LinearLayout android:gravity="right" android:orientation="horizontal" android:visibility="visible" android:layout_width="fill_parent" android:layout_height="wrap_content">
<LinearLayout android:gravity="left" android:layout_width="0.0dip" android:layout_height="fill_parent" android:layout_weight="1.0">
<TextView android:textSize="10.0sp" android:textColor="#ff808080" android:layout_gravity="center" android:id="@id/service_freq" android:paddingLeft="30.0dip" android:visibility="visible" android:layout_width="wrap_content" android:layout_height="wrap_content" android:text="service freq" />
</LinearLayout>
<TextView android:textSize="10.0sp" android:textColor="#ffffffff" android:layout_gravity="center" android:id="@id/service_pty" android:visibility="gone" android:layout_width="wrap_content" android:layout_height="wrap_content" android:layout_marginRight="30.0dip" android:text="service pty" />
<Spinner android:textSize="10.0sp" android:textColor="#ffffffff" android:entries="@array/pty_array" android:layout_gravity="right" android:id="@id/pty_spinner" android:visibility="gone" android:layout_width="wrap_content" android:layout_height="wrap_content" android:layout_marginRight="10.0dip" android:spinnerMode="dropdown" style="@style/customSpinner" />
</LinearLayout>
<LinearLayout android:gravity="center" android:layout_gravity="center_horizontal" android:background="@drawable/backgroud_text_area" android:layout_width="400dip" android:layout_height="250dip" android:layout_marginTop="1.0dip" android:layout_weight="8.0">
<ImageView android:id="@id/mot" android:layout_width="380dip" android:layout_height="230dip" android:src="@drawable/radio" android:contentDescription="@null" />
</LinearLayout>
<LinearLayout android:layout_gravity="center_horizontal" android:orientation="horizontal" android:layout_width="wrap_content" android:layout_height="wrap_content" android:layout_marginTop="1.0dip" android:layout_weight="2.0">
<Button android:layout_gravity="center_vertical" android:id="@id/bt_prev" android:background="@drawable/previous_selector" android:layout_width="wrap_content" android:layout_height="wrap_content" />
<Button android:layout_gravity="center_vertical" android:id="@id/bt_scan" android:background="@drawable/scan_selector" android:layout_width="wrap_content" android:layout_height="wrap_content" />
<Button android:layout_gravity="center_vertical" android:id="@id/bt_next" android:background="@drawable/next_selector" android:layout_width="wrap_content" android:layout_height="wrap_content" />
<Button android:layout_gravity="center_vertical" android:id="@id/bt_pty" android:background="@drawable/pty_selector" android:layout_width="wrap_content" android:layout_height="wrap_content" />
</LinearLayout>
<LinearLayout android:gravity="center_horizontal" android:layout_width="wrap_content" android:layout_height="wrap_content" android:layout_marginLeft="10.0dip" android:layout_marginTop="1.0dip" android:layout_weight="1.0">
<com.ex.dabplayer.pad.activity.MarqueeText android:textSize="18.0sp" android:ellipsize="marquee" android:id="@id/dls2" android:scrollX="4.0sp" android:visibility="gone" android:layout_width="wrap_content" android:layout_height="wrap_content" android:text="" android:singleLine="true" android:marqueeRepeatLimit="marquee_forever" />"
<TextView android:textSize="18.0sp" android:ellipsize="end" android:id="@id/dls" android:visibility="gone" android:layout_width="wrap_content" android:layout_height="wrap_content" android:text="" android:singleLine="true" />
<TextView android:textSize="18.0sp" android:ellipsize="marquee" android:gravity="center_horizontal" android:id="@id/dls_scroll" android:focusable="true" android:focusableInTouchMode="true" android:layout_width="wrap_content" android:layout_height="wrap_content" android:text="this is dls" android:singleLine="true" android:marqueeRepeatLimit="marquee_forever" />
</LinearLayout>
</LinearLayout>
<LinearLayout android:orientation="horizontal" android:background="@drawable/backgroud_text_area" android:layout_width="fill_parent" android:layout_height="fill_parent" android:layout_marginTop="20.0dip" android:layout_marginRight="20.0dip" android:layout_marginBottom="20.0dip" android:layout_weight="6.0">
<ListView android:scrollbarAlwaysDrawVerticalTrack="true" android:id="@android:id/list" android:paddingTop="20.0dip" android:scrollbars="vertical" android:layout_width="fill_parent" android:layout_height="wrap_content" android:listSelector="@drawable/list_selector_background" android:stackFromBottom="false" android:transcriptMode="alwaysScroll" />
</LinearLayout>
</LinearLayout>
May be you have another idea to fill the picture background?
So the original and my modded app show a very small album picture (slide show in DAB terms), did I get this right? Maybe you could attach a screenshot?
realzoulou said:
So the original and my modded app show a very small album picture (slide show in DAB terms), did I get this right? Maybe you could attach a screenshot?
Click to expand...
Click to collapse
Yes, exactly... Will do a screenshot tomorrow on my commute.
Thanks again for the great mod
Can I suggest some small UI design changes? I modded the UI slightly myself a while back and thought the player looked much better without the "glow" frames around the slideshow and channel list. They don't need to be replaced at all, just removed. It would also look a lot better with some material design buttons instead of those 90's web design ones (previous, next, search etc).
Great mod, thank you very much
This version also shows Norwegian info text with correct font, something the original app did not.
I agree with nyogtha on the removal of the glow frame.
PTY is very useful, but favorites would be even better. Perhaps just an option to edit a file with the channel numbers to display and then add an extra PTY category named "My Favorites" or something like that to select the channels defined in the file?