Jump to content

µTorrent MiniUI


Ultima

Recommended Posts

  • 1 month later...
  • Replies 174
  • Created
  • Last Reply

Top Posters In This Topic

Hello,

I'm trying to make MiniUI work on my Sony-Ericsson W705, but it doesn't work ok.

WebUI and MiniUI works great, when separatly tested on any browser on my home or work PC (so: all is properly configured, port forward ok, etc...)

(and it works great - nice work !)

But... on my w705, it only displays an incomplete page with the top 4 tabs (torrents, details...) and a "Loading..." message (in the page, not the "loading" from the phone browser while loading the page)

Here is what I see :

1247939932_pb-tel.png

Left: what's in my pc browser.

Right: what I see on my phone.

(right image is a simulation based on my pc browser, but rather realistic)

Looks like a problem with the XMLHttpRequest call on the phone's browser...

Does anybody makes it work on a sony embedded browser ?

Link to comment
Share on other sites

If what I'm seeing on Google is accurate, then the W705 browser is based on NetFront (the same engine as the PSP's browser). NetFront's support for many web technologies seems to be lacking (at least with the versions licensed and included in the devices I've seen or read about). I don't know what to say, other than that if XHR isn't supported on the browser, then MiniUI won't work.

Finding an alternative way to communicate with the µTorrent backend has been on my todo list for a while now (specifically, for BlackBerry v4.5.0 and lower, and PSP/NetFront support), but it's low priority at the moment (on top of the already low priority all of my projects have at the moment, what with me being busy and all this summer).

Link to comment
Share on other sites

Chances are, you have non-ASCII characters in your torrent jobs list, which would mean you're running into an Opera Mini bug.

@michelp: Yeah, Opera Mini is officially supported by µTorrent MiniUI (see the first post). I'd forgotten it was available for just about any phone with Mobile Java support, though, so it slipped my mind to recommend it.

Link to comment
Share on other sites

  • 1 month later...

Auto-reloading (with configurable intervals) has actually been implemented in my local copy of MiniUI for a while now (among a bunch of other changes), but it hasn't been released because it's still not as polished as I'd like it to be, and I haven't had much time to work on MiniUI.

Link to comment
Share on other sites

Eh, I suppose since I won't be making much further progress for the time being, I'll just release it now. Did a bit of code cleanup and testing today.

Auto-refreshing could've been enabled in Mobile IE 5, but unfortunately, the browser likes to scroll back to the top of the page every time the page refreshes, which makes the whole thing pretty useless. As such, I had to implement it in a way that Mobile IE 5 couldn't understand (window.setInterval() rather than repeated calls to window.setTimeout()). Opera Mobile and Iris Browser (RIP) work correctly, so meh.

2009-09-04

+ Feature: Auto-refreshing

~ Change: Attempt to request a new token if previous request fails

~ Change: Implement proper guest account restrictions

~ Change: Use queue.slow_*_threshold to determine active/inactive torrents

* Fix: Torrent files don't load when torrent is clicked in some situations

* Fix: Torrent properties never get cached

Oh, and remember how I mentioned I'd try and implement support for other browsers (like NetFront, or BlackBerry Browser v4.5.0 and older)? Well I tried, and failed. There are just too many complexities and crazinesses involved with them that quite simply make it not worth the effort (and really, it doesn't look like it'll be possible anyway).

Link to comment
Share on other sites

  • 1 month later...

Hello,

I'm trying to make MiniUI work on my NOKIA E71, but it doesn't work ok.

WebUI and MiniUI works great, when separatly tested on any browser on my home or work PC (so: all is properly configured, port forward ok, etc...)

(and it works great - nice work !)

But... on my E71, it only displays a page with "torrent 0 speed 0" and can never display the actual information.

Here is what I see :

medium.jpgmedium.jpg

Top: what's in my pc browser.

Down: what I see on my mobile phone.

the versions:

uTorrent: 1.8.2

µTorrent MiniUI: 2009-09-04

opera mini: 4.2

mobile phone: NOKIA E71

Does anybody make it work on opera mini with NOKIA mobile?

Thanks.

Link to comment
Share on other sites

It's an Opera Mini server bug. If at all possible, you and other people running into the problem should help me complain on Opera's forums in this thread, because they don't seem like they prioritize a bug report when just one user reports it, no matter how important it is. This gaping bug in such an integral Javascript component has existed for way too long already, and yet, they still don't seem interested in even responding to queries on the bug's status, let alone fixing it. They fixed it in Opera 10 after I'd reported it -- how difficult is it for them to fix the exact same bug in Opera Mini? (Yes, I'm frustrated with Opera right now)

By the way, from your screenshot, it seems like there's another bug where it isn't displaying "µT" correctly in the titlebar -- probably related to the fact that you're using Chinese for the UI language.

@Cmalave: What URL are you accessing? How did you install MiniUI?

Link to comment
Share on other sites

This doesn't work for me. :-( I get either a blank page (FF3.5), a "page cannot be displayed" page (IE7), or an "invalid request" page (IE Mobile 6, Safari on iPod Touch). Just to confirm, I made a folder called mini inside %appdata%\uTorrent (webui works fine with webui.zip in %appdata%) and extracted the index.html and 8 .gz files there? (I also tried extracting the .jz and style.css files in case they were gzipped by mistake but that failed too).

And I was going to http://myurl:xx/gui/mini/index.html btw. I even tried it on the local machine running localhost:xx/gui/mini/index.html.

Link to comment
Share on other sites

@Ultima

I Jumped over to MiniUI since Java APP wasnt working for me... Well things are pretty smooth.. And i have been using it on my Opera Mini (4.3) for somedays now .. I just found 1 bug/problem today...

In the setting for : Bandwidth limiting, when i change the values (say i change teh download from 100 -> 200 ) the page automatically refreshes without saving the settings

:-S

So basically i cannot change the bandwidth setting due to this ...

Link to comment
Share on other sites

Hm, odd, I thought I specifically made it so that auto-refresh happens only when the user is viewing the torrent jobs list or a torrent job's basic details... I guess I'll need to fix it when I find a bit of time. Thanks for the report!

Edit: Heh, after a bit of testing, it looks more like I completely broke the "Refresh" button for anything but Torrents, Details > Basic, and Settings. Will definitely need fixing.

Edit: http://www.mediafire.com/download.php?1bmmtjyfjjy

Get here miniui.js.gz and replace the one you placed in webui.zip.

Link to comment
Share on other sites

Works :-D

I was really looking for this feature.

One more thing.. i got confused upon was the "RATIO". I am(i guess most of us) are used to looking at ratio has a figure(i mean in the form : 1.XX) and NOT as a percentage value(1XX%).

Neways its nothing BIG .. a simple edit does the thing.

Feature Request:

A option to set a default category. The first thing i like to see in my list the "ACTIVE" torrents list. If webUI/MiniUI could have an option to set a default category it would just make it a lil faster to use. Esp. if you have many torrents in the COMPLETED listed ..

Link to comment
Share on other sites

The ability to store the last used settings is on my todo list, but not at the top right now because the only real way I can store settings is in a certain WebUI settings key that would be shared between any project using the WebUI backend. Unfortunately, there does not exist any standardized way for projects to non-destructively share that key at the moment, so I'm holding off on it.

And yes, I've toyed with using different default categories, but I refrained from defaulting to Active because if the user doesn't currently have any active torrent jobs, he might be confused for a while about why his list is empty when he first loads MiniUI.

Link to comment
Share on other sites

  • 4 weeks later...

I upgraded my BlackBerry Bold to OS 5.0 and I can no longer add torrents using Browse for file. MiniUI just hangs. Adding a torrent by URL still works, but I use a few private trackers and I need to browse for the .torrent file for these to work. Everything worked fine in BlackBerry OS 4.6

The third party Bolt Browser doesn't seem to have any issues adding a torrent by file.

Link to comment
Share on other sites

I haven't tested BlackBerry OS 5.0 yet (didn't even know it was out), but speculatively, I'd say this is a BlackBerry issue. I don't do anything particularly special when sending the .torrent file -- it simply submits a form with the relevant file.

Question: When you click "Add File", do you see anything show up in the µTorrent Logger tab (make sure you're logging WebUI requests in the logger)?

Link to comment
Share on other sites

Thanks for the quick response. The following are the logs when adding the same .torrent file using two different browsers.

Here's the log using the BlackBerry browser:

[2009-11-04 20:09:40] HTTP: IP 206.53.153.88: GET /gui/mini/index.html

[2009-11-04 20:09:46] HTTP: IP 206.53.153.88: GET /gui/mini/style.css

[2009-11-04 20:09:52] HTTP: IP 206.53.153.88: GET /gui/mini/utility.js

[2009-11-04 20:10:00] HTTP: IP 206.53.153.88: GET /gui/mini/utorrent.js

[2009-11-04 20:10:06] HTTP: IP 206.53.153.88: GET /gui/mini/webui.js

[2009-11-04 20:10:12] HTTP: IP 206.53.153.88: GET /gui/mini/pane.js

[2009-11-04 20:10:18] HTTP: IP 206.53.153.88: GET /gui/mini/page.js

[2009-11-04 20:10:24] HTTP: IP 206.53.153.88: GET /gui/mini/html.js

[2009-11-04 20:10:30] HTTP: IP 206.53.153.88: GET /gui/mini/miniui.js

[2009-11-04 20:10:37] HTTP: IP 206.53.153.88: GET /gui/token.html

[2009-11-04 20:10:44] HTTP: IP 206.53.153.88: GET /gui/?token=u6X6PlQGt80F8RRagK_3jra0YTOAdZemRrmYs6PwcpBzmNhLYUNBZw0m8ko=&action=add-url&s=&t=1257383444473

[2009-11-04 20:10:51] HTTP: IP 206.53.153.88: GET /gui/?token=u6X6PlQGt80F8RRagK_3jra0YTOAdZemRrmYs6PwcpBzmNhLYUNBZw0m8ko=&action=getsettings&t=1257383451312

[2009-11-04 20:10:55] HTTP: IP 206.53.153.88: GET /gui/?token=u6X6PlQGt80F8RRagK_3jra0YTOAdZemRrmYs6PwcpBzmNhLYUNBZw0m8ko=&list=1&cid=&t=1257383459325

[2009-11-04 20:11:09] HTTP: IP 206.53.153.88: GET /gui/?token=u6X6PlQGt80F8RRagK_3jra0YTOAdZemRrmYs6PwcpBzmNhLYUNBZw0m8ko=&list=1&cid=1655032814&t=1257383469384

[2009-11-04 20:11:32] HTTP: IP 206.53.153.88: GET /gui/?token=u6X6PlQGt80F8RRagK_3jra0YTOAdZemRrmYs6PwcpBzmNhLYUNBZw0m8ko=&action=add-file

And here's the log when using the Bolt Browser that works:

[2009-11-04 20:18:02] HTTP: IP 174.132.56.156: GET /gui/mini/index.html

[2009-11-04 20:18:02] HTTP: IP 174.132.56.156: GET /gui/mini/style.css

[2009-11-04 20:18:02] HTTP: IP 174.132.56.156: GET /gui/mini/utility.js

[2009-11-04 20:18:02] HTTP: IP 174.132.56.156: GET /gui/mini/utorrent.js

[2009-11-04 20:18:03] HTTP: IP 174.132.56.156: GET /gui/mini/webui.js

[2009-11-04 20:18:03] HTTP: IP 174.132.56.156: GET /gui/mini/pane.js

[2009-11-04 20:18:04] HTTP: IP 174.132.56.156: GET /gui/mini/page.js

[2009-11-04 20:18:04] HTTP: IP 174.132.56.156: GET /gui/mini/html.js

[2009-11-04 20:18:05] HTTP: IP 174.132.56.156: GET /gui/mini/miniui.js

[2009-11-04 20:18:06] HTTP: IP 174.132.56.156: GET /gui/token.html

[2009-11-04 20:18:06] HTTP: IP 174.132.56.156: GET /gui/?token=LfpnMBybQatfIbfCwJifxw3L2BaL86lZXRUpyAt5iRRhU0RcBPucOc4n8ko=&action=add-url&s=&t=1257383893414

[2009-11-04 20:18:06] HTTP: IP 174.132.56.156: GET /gui/?token=LfpnMBybQatfIbfCwJifxw3L2BaL86lZXRUpyAt5iRRhU0RcBPucOc4n8ko=&action=getsettings&t=1257383893709

[2009-11-04 20:18:07] HTTP: IP 174.132.56.156: GET /gui/?token=LfpnMBybQatfIbfCwJifxw3L2BaL86lZXRUpyAt5iRRhU0RcBPucOc4n8ko=&list=1&cid=&t=1257383894082

[2009-11-04 20:18:23] HTTP: IP 174.132.56.156: GET /gui/?token=LfpnMBybQatfIbfCwJifxw3L2BaL86lZXRUpyAt5iRRhU0RcBPucOc4n8ko=&list=1&cid=2104417531&t=1257383910424

[2009-11-04 20:19:14] HTTP: IP 174.132.56.156: GET /gui/?action=add-file

Seems like the BlackBerry browser doesn't have a separate entry for the GET /gui/?action=add-file line, it just adds it to the end of the previous line. Hope this information can help you.

Link to comment
Share on other sites

[11/5/2009 9:42:48 PM:484]

POST /gui/?token=fkCxoJ1pdz7V1z21-An0yCgGNBb7Cq0hDvoAp4-RQWZqM-5MHqNk4xiN80o=&action=add-file HTTP/1.1

User-Agent: BlackBerry9530/4.7.0.75 Profile/MIDP-2.0 Configuration/CLDC-1.1 VendorID/-1

profile: http://www.blackberry.net/go/mobile/profiles/uaprof/9530_evdo/4.7.0.rdf

Accept: application/vnd.rim.html,text/html,application/xhtml+xml,application/vnd.wap.xhtml+xml,text/vnd.sun.j2me.app-descriptor,image/vnd.rim.png,image/jpeg,application/x-vnd.rim.pme.b,application/vnd.rim.ucs,image/gif;anim=1,application/vnd.rim.jscriptc;v=0-8-72,application/x-javascript,application/vnd.rim.css;v=1,text/css;media=screen,application/vnd.wap.wmlc;q=0.9,application/vnd.wap.wmlscriptc;q=0.7,text/vnd.wap.wml;q=0.7,*/*;q=0.5

Authorization: Basic [LOGIN]

Content-Length: 9201

Connection: close

Referer: http://[HOST]:[PORT]/gui/mini/index.html

Accept-Charset: UTF-8,ISO-8859-1,US-ASCII,UTF-16BE,windows-1252,UTF-16LE,ISO-2022-JP,Shift_JIS,Big5-HKSCS,Big5,GB2312,KSC5601,x-Johab,EUC-KR,windows-1250

Host: [HOST]:[PORT]

Accept-Language: en-GB,en;q=0.5

Content-Type: multipart/form-data; boundary=------------1257475368390

x-wap-profile: "http://www.blackberry.net/go/mobile/profiles/uaprof/9530_evdo/4.7.0.rdf"

Via: MDS_4.1.2.17

--------------1257475368390

Content-Disposition: form-data; name="torrent_file"; filename="test.torrent"

Content-Type: application/octet-stream

[TORRENT CONTENTS]

--------------1257475368390--

[11/5/2009 9:42:48 PM:562]

HTTP/1.1 200 OK

Connection: keep-alive

Content-Length: 16

Content-Type: text/plain

Cache-Control: no-cache

{"build":17127}

Result (BlackBerry OS v4.7): Torrent successfully added.

[11/5/2009 9:40:41 PM:453]

POST /gui/?token=Rt5wQaADK5pLOHyg7INDqVxejF9_2w2H0_l57RQigvDhr0oeb6LLmiuM80o=&action=add-file HTTP/1.1

User-Agent: BlackBerry9500/5.0.0.252 Profile/MIDP-2.1 Configuration/CLDC-1.1 VendorID/-1

profile: http://www.blackberry.net/go/mobile/profiles/uaprof/9500_umts/5.0.0.rdf

Accept: application/vnd.rim.html,text/html,application/xhtml+xml,application/vnd.wap.xhtml+xml,text/vnd.sun.j2me.app-descriptor,image/vnd.rim.png,image/jpeg,application/x-vnd.rim.pme.b,application/vnd.rim.ucs,image/gif;anim=1,application/vnd.rim.jscriptc;v=0-8-72,application/x-javascript,application/vnd.rim.css;v=2,text/css;media=screen,application/vnd.wap.wmlc;q=0.9,application/vnd.wap.wmlscriptc;q=0.7,text/vnd.wap.wml;q=0.7,*/*;q=0.5

Authorization: Basic [LOGIN]

Content-Length: 0

Connection: close

Referer: http://[HOST]:[PORT]/gui/mini/index.html

Accept-Charset: UTF-8,ISO-8859-1,US-ASCII,UTF-16LE,UTF-16BE,windows-1252

Host: [HOST]:[PORT]

Accept-Language: en-GB,en;q=0.5

Content-Type: multipart/form-data; boundary=------------1257475241328

x-wap-profile: "http://www.blackberry.net/go/mobile/profiles/uaprof/9500_umts/5.0.0.rdf"

Via: MDS_4.1.2.17

[11/5/2009 9:40:41 PM:453]

HTTP/1.1 200 OK

Connection: keep-alive

Content-Length: 33

Content-Type: text/plain

Cache-Control: no-cache

{"build":17127,"error": "Error"}

Result (BlackBerry OS v5.0): Torrent not added.

So yes, I can confirm that there is indeed a problem with BlackBerry OS v5.0. Looks to me like BlackBerry's servers are stripping out the .torrent file data before it gets sent to µTorrent for BlackBerry Browser v5.0, but not for BlackBerry Browser v4.7. Maybe it's a browser profile related issue (something controlled on BlackBerry's end; see those .rdf files mentioned in the packet sniffs)... I really don't know what else to say.

By the way, the requests as indicated in your log show that BlackBerry Browser is actually making the correct WebUI request -- BOLT browser is technically doing it wrong, and it will fail if webui.token_auth is enabled.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.


×
×
  • Create New...