Beelink R89/UBOX ROM/Tools release

[Elroy1]

Re: Beelink R89/UBOX ROM/Tools release

Not sure but I know lexar 64gb SDXC class 10 works.

Sandisk ultra class 10 64gb also working here

[ICU]

Not sure but I know lexar 64gb SDXC class 10 works.

Maybe because all sdcards are not supported?

[leolas]

Re: Beelink R89/UBOX ROM/Tools release

BTW I formated a 64gb micro SD card fat32 and the r89 sees it 59.6 GB available. Not sure why its advertised as only taking up to a 32gb micro sd.?

Maybe because all sdcards are not supported?

[ICU]

BTW I formated a 64gb micro SD card fat32 and the r89 sees it 59.6 GB available. Not sure why its advertised as only taking up to a 32gb micro sd.?

[ICU]

Well said bro. You saved me the trouble figuring stuff out once I start testing the dual boot and messing about.

Thanks, every time I mess up, I learn something new. But as my dear old departed mom used to say. Iffen you don't mess up, you ain't trying your best.

[clarkss12]

Phew! Glad to hear you got it going again. May have to save this post of yours.

Thanks, every time I mess up, I learn something new. But as my dear old departed mom used to say. Iffen you don't mess up, you ain't trying your best.

[4WheelSpyder]

Phew! Glad to hear you got it going again. May have to save this post of yours.

[clarkss12]

R89 broken again

Tried to install Firefly dual Android/Linux rom on my R89, it loaded but could only get to the Firefly screen. Tried just the Linux rom, but my R89 says "prepare IDB fail". Tried installing Finless rom, but same problem IDB fail. Not sure what to do next. I connect to my Windows 7 computer and it detects the device perfectly. Is this going to be a situation where I have to short two pins? I surely hope not, my vision is not very good.
Any help would be greatly appreciated.

Link to the rom I tried to install. I am not sure what caused the IDE to fail, I did do a lower format.

http://www.t-firefly.com/en/download/

thanks

Ok, back working again. From Oman's first post he shows those two teeny, tinny holes, I guess it is the same as shorting two pins on the ram chip. Anyway, when I shorted those two pins and then held in the reset button as I powered it on, it showed as "mask rom", and I had never seen that before. Since I had no idea what I was doing, I started clicking buttons on the advanced tab. "ReadIDB", "TestDevice", "ResetDevice", ect. Anyway, after I got done clicking buttons, I removed the jumper I had in those two tenny, tinny holes and pulled the power plug. When I again held the reset button, and plugged in the power, it worked. So, I am back to Finless 2 rom for my R89. I may try again tomorrow to install the dual boot linux.

[Finless]

Hi,Bob:

Some hints->
1.http://developer.android.com/google/play/filters.html

system\etc\permissions\

2.The advice I can give out is using your external keyboard/2.4G Airmouse by OTG port.

Ah yes.... I should have remembered that! the XML files in permissions

Totally forgot about that one.
Thanks for the reminder!

Bob

[oman]

OK this is odd, no matter how much I edit build.prop to spoof thinks as well as the fingerprint, etc. I cannot get APPs to allow install and they say not compatible!
Trust I have tried everything in build.prop I could think of.

Prime example the Crackle APP says not compatible.

Makes me wonder how Google Play is now determining that?


Also Oman, there is something really wrong with the keyboard input. It's laggy for soft keyboard and when you have a external keyboard (Logitech k400 is mine) it will start repeating characters really bad!
Funny as this was an early bug on 3188 devices

Bob

Hi,Bob:

Some hints->
1.http://developer.android.com/google/play/filters.html

system\etc\permissions\

2.The advice I can give out is using your external keyboard/2.4G Airmouse by OTG port.

[4WheelSpyder]

It's laggy for soft keyboard and when you have a external keyboard (Logitech k400 is mine) it will start repeating characters really bad!
Funny as this was an early bug on 3188 devices

Bob

I am seeing exactly that on an external keyboard (Microsoft). This is a new bug in the later SW releases since I used the keyboard before on the R89 without any problems.

[Finless]

Apps not compatible and Keyboard lag/bounce

OK this is odd, no matter how much I edit build.prop to spoof thinks as well as the fingerprint, etc. I cannot get APPs to allow install and they say not compatible!
Trust I have tried everything in build.prop I could think of.

Prime example the Crackle APP says not compatible.

Makes me wonder how Google Play is now determining that?


Also Oman, there is something really wrong with the keyboard input. It's laggy for soft keyboard and when you have a external keyboard (Logitech k400 is mine) it will start repeating characters really bad!
Funny as this was an early bug on 3188 devices

Bob

[4WheelSpyder]

Installed the 110k version using the new drivers with the previous tool. The new tool was just "sitting" there - no feedback on the progress.

In relation to clarkss12 micro USB connection problem. This time I grabbed the USB cable that came with my Nexus 7 and the connection was very "iffy".

[clarkss12]

Downloading now. I will post it to FT servers when done.

Bob

Thanks, Btw, I got my R89 to connect with my computer. I tried 3 different OTG adapters, and none worked. I purchased an Apple charge/data cable for $5 US at Big lots, and now I can connect to my PC.

[Finless]

Post 188, but I am having a tough time downloading it. It started to download then stopped, will not connect again.

http://www.freaktab.com/showthread.p...ht=#post237837

Downloading now. I will post it to FT servers when done.

Bob