Announcement

Collapse
No announcement yet.

Announcement

Collapse
No announcement yet.

OLD - UG802 2dark4u/Finless custom ROM version 1.7

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    ..

    Comment


      Originally posted by rfwagner View Post
      Another question, is about a good PSU.
      Anyone have bought a really 2A or more in the internet, that ships worldwide?

      I found some in **** and Aliexpress, but i'm a little septic, like what i see in the Feedback area of Aliexpress, some 2A PSU that were identified by buyers as fake 2A, so i'm waiting to see a really good option.

      Thanks again
      I use this product "EM1126" with my ug802
      It works great! !
      I power the ug802 from the charge port "2A" and hookup al my devices to the other ports of the hub like HDD, Ethernet adapter, etc etc...
      One more thing, you also got a on/off switch with this setup !!

      Last edited by gds; 13 December 2012, 12:01.

      Comment


        Originally posted by rfwagner View Post
        Another question, is about a good PSU.

        Anyone have bought a really 2A or more in the internet, that ships worldwide?
        I'm using one Arctic Cooling charger (http://www.arctic.ac/en/p/power/char...0/.html?c=2224). I think it is available globally.

        Comment


          HELP!!!

          I made a serious mistake, I installed Chainfire and now UG802 not booting! :-( Does anyone know how to solve?

          I using 2dark4u/Finless 1.7 with default options!

          Comment


            Originally posted by Anunakin View Post
            I made a serious mistake, I installed Chainfire and now UG802 not booting! :-( Does anyone know how to solve?

            I using 2dark4u/Finless 1.7 with default options!
            Reflash the rom and no, there is no other way. You'll probably have to open it up to press the reset button.

            Comment


              bootloop

              Originally posted by Anunakin View Post
              I made a serious mistake, I installed Chainfire and now UG802 not booting! :-( Does anyone know how to solve?

              I using 2dark4u/Finless 1.7 with default options!

              Comment


                Thanks!

                Originally posted by lambstone View Post
                Reflash the rom and no, there is no other way. You'll probably have to open it up to press the reset button.
                Thanks! I got my UG802 back!

                But we need a .img, I used one JB for MK808, and after it, reinstaller 2dark4u/Finless ROM 1.7 ....

                Thanks!

                Another question, any way to have "Natural Scrolling" under Android?
                Last edited by Anunakin; 14 December 2012, 13:06. Reason: more text

                Comment


                  Hi Bob

                  Hi Bob,

                  Any comment ?


                  Originally posted by compy View Post
                  Hi fin,

                  Thanks for your work.

                  Can we load this image on Neo-G4, as it uses almost same hardware as UG802.

                  I have attached dmesg from my device.

                  Thanks

                  Comment


                    Hey Bob,

                    thanks again for Image and Support.

                    But i have (for me) an important question. Is it possible to build MCS7830 Chipset driver in that great image?
                    Because of USB-RJ45 adapter. I have two of them here and it would be very good to use it instead of buying a new one.
                    I need it because my WLan router is far away from office where i play with my "toys".

                    Datasheet says working since Linux Kernel 2.6, so it should be possible to build the mcs7830.ko. Am i right?

                    HERE i found a link, but linux / andoird kernel is only up to 3 and not Android 4.

                    Could you maybe help?

                    Thanks & BR
                    Hans

                    Edit: Attached the linux driver source but i´m not sure if you can build with that
                    Attached Files
                    Last edited by Hans0815; 14 December 2012, 21:56. Reason: Added driver sources

                    Comment


                      Has anyone tried plugging in a USB Bluetooth dongle to see if we can get Bluetooth to work on the UG802? And which Bluetooth did you use?

                      Comment


                        Originally posted by jchau View Post
                        Has anyone tried plugging in a USB Bluetooth dongle to see if we can get Bluetooth to work on the UG802? And which Bluetooth did you use?
                        There is a Hardware thread with working hardware and i think i have seen a Bluetooth device there.
                        Have a look at that thread i think you will find what you need.

                        Comment


                          Originally posted by mrmrmrmr View Post
                          Hi,

                          I have tried this ROM on my new MK802 III. It works fine.
                          But it doesn't work with my USB hub.
                          In fact, the official firmware as well doesn't work with my USB hub. But the hub works fine with old original MK802.
                          So what's the problem with MK802 III ? is it hardware or software ?


                          thx.
                          please, I need help.
                          please share your ideas. I'd like to see if it will work before I go and buy another hub.

                          Comment


                            Originally posted by Finless View Post
                            I am going to close this BS prodding by ether0 with the following



                            As I stated above. NOT all parts of Android are GPL. In fact many are Apache and in fact as I stated, drivers etc MAY NOT BE GPL or open source!!!

                            From the link above:

                            "Important firmware or drivers are generally proprietary also. These handle the phone network radio, WiFi, bluetooth, GPS, 3D graphics, the camera, the speaker, and in some cases the microphone too."

                            So as stated. If Alex got hired to make drivers for a company THEY CAN BE PROPRIETARY!
                            All he is required to do is release the GPL parts of his kernel. Ether0 does not understand GPL and his arguement with Alex about making money making drivers and that HE MUST release the code, is total BS.

                            Now I quote GPL:
                            "Thus, it is not the intent of this section to claim rights or contest
                            your rights to work written entirely by you;
                            rather, the intent is to
                            exercise the right to control the distribution of derivative or
                            collective works based on the Program.

                            In addition, mere aggregation of another work not based on the Program
                            with the Program (or with a work based on the Program) on a volume of
                            a storage or distribution medium does not bring the other work under
                            the scope of this License.
                            "

                            So all Alex has to release is the mods he made the to kernel (derivative or collective work). He does not have to release his OWN code that he has added to the kernel. So you know his GPU driver is his own code!
                            The linux kernel is not Apache. It is GPLv2. I asked for sources in compliance with the GPL. Anorther straw man argument from you Bob. Let's stick to the issues.

                            Your quote from the document is deviously omitting an important piece of context, namely "But there are other problems", from whence the document expounds on the problems, one of the problems being that the drivers are being kept proprietary. The document certainly does not say that this acceptable, as you have implied. The point the document makes is quite contrary to this view.

                            Derivative work is clearly defined in the copyright laws: a "'derivative work' is a work based upon one or more preexisting works, such as a translation, musical arrangement, dramatization, fictionalization, motion picture version, sound recording, art reproduction, abridgment, condensation, or any other form in which a work may be recast, transformed, or adapted. A work consisting of editorial revisions, annotations, elaborations, or other modifications which, as a whole, represent an original work of authorship, is a 'derivative work.'"

                            Since 2dark4u transformed, adapted, or otherwise modified the kernel, it should be clear that the whole of the modified kernel including 2dark4u's modifications and drivers make up the total of the code that falls under the GPL and to which according to the terms of the GPL the complete corresponding source code must be provided.

                            Mere aggregation does not apply here. It is not like you're distributing a copy of Windows, i.e. the other work, bundled with your ROM. Without more, that would be aggregation and you would not be required by the GPL to disclose the source for Windows. Don't be silly Bob, another straw man? Really?

                            Ultimately, the question to you is when will we see the full corresponding (including the drivers) source to the kernel you are distributing, Bob?

                            Comment


                              Originally posted by ether0 View Post
                              ...........
                              Go out from here. We dont need you.
                              Please dont feed this troll.

                              Comment


                                Originally posted by 2dark4u View Post
                                On boot kernel allocates memory for GPU and VPU and after boot impossible to make them bigger/smaller, so I need to choose all settings to get 720P or 1080P before I'll compile the kernel.
                                To make possible switching to native resolution's without reflashing proper kernel, I need to add possibility to read settings from file system instead of properties inside kernel
                                Just overallocate for 1080p and then waste the extra memory in the 720p mode.

                                How do the stock versions communicate res changes to the kernel? boot flags? userland process using a proc write? ioctls? It's already being done, you just need to tap into this plumbing.

                                Comment

                                Working...
                                X