Portrait mode

liatoss

Dear Developers,

Actually today (25.05.2015), does the Firefly RK3288 supports the portrait mode in Android or in Lubuntu? Any third party distros which support the Portrait mode?

Thank you in advance, Vlad.

madman

Hello,  
Revert "Android->frameworks:Forced rotation to horizontal screen if insert hdmi"
   
    This reverts commit 137bead4fffd7f212ee144456420933d54fbd0ef.

diff --git a/frameworks/base/policy/src/com/android/internal/policy/impl/PhoneWindowManager.java b/frameworks/base/policy/src/com/android/intern
index 53e7068..fc80328 100755
--- a/frameworks/base/policy/src/com/android/internal/policy/impl/PhoneWindowManager.java
+++ b/frameworks/base/policy/src/com/android/internal/policy/impl/PhoneWindowManager.java
@@ -1112,7 +1112,7 @@ public class PhoneWindowManager implements WindowManagerPolicy {
         } else {
             mDemoHdmiRotation = mLandscapeRotation;
         }
-        mDemoHdmiRotationLock = SystemProperties.getBoolean("persist.demo.hdmirotationlock", true);
+        mDemoHdmiRotationLock = SystemProperties.getBoolean("persist.demo.hdmirotationlock", false);

you can chance the “true” to “false” or git revert it

liatoss

Hello Madman, thank you very much for quick reply...

It takes time for me but I have compiled a system image, a kernel image etc.... I've got all required images and furthermore I've built a new complete image.

However, despite all my efforts, I've got the same error message as those from this discussion: http://bbs.t-firefly.com/forum.php?mod=viewthread&tid=306.

All my similar attempts to fix the issue give me nothing. The board is still in the loop. My attempt to write FirFly original images for the latest Android image as well as for the Dual boot image gives my the same loop.

To clarify, I write parameters file by using the Android Tool release 2.33. It doesn;t work - the same loop. After that, I have made a full image by unpacking the latest Android image I have downloaded from your website and packed it back with my boot.img, kernel.img, misc.img. recovery.img, resource.img, system.img in Ubunut 14.10. In this time RKBatchTool v.1.7 wrote the image but I still got the loop.

Hereby is the text of the loop, which ends by a string "OUT" and after that it repeats the same again and again:
**************** Start of the boot listing *****************************
U-Boot 2014.10-RK3288-02 (Jan 21 2015 - 17:07:53)

CPU: rk3288
CPU's clock information:
    arm pll = 600000000HZ
    periph pll = 300000000HZ
    ddr pll = 200000000HZ
    codec pll = 594000000HZ
Board:  Rockchip platform Board
DRAM:  Found dram banks:1
Adding bank:0000000000000000(0000000080000000)
128 MiB
storage init OK!
Using default environment

GetParam
check parameter success
Unknow param: MACHINE_MODEL:rk30sdk!
Unknow param: MACHINE_ID:007!
Unknow param: MANUFACTURER:RK30SDK!
Unknow param: PWR_HLD: 0,0,A,0,1!
failed to prepare fdt from boot!
power key: bank-0 pin-5
light power led: bank-8 pin-1
pmic:act8846
SecureBootEn = 0, SecureBootLock = 0

#Boot ver: 2015-01-21#2.17
empty serial no.
checkKey
vbus = 1
no fuel gauge found
no fuel gauge found
read logo_on switch from dts [0]
no fuel gauge found
got recovery cmd from misc.
failed to load fdt from recovery!
kernel   @ 0x02000000 (0x00653540)
ramdisk  @ 0x04bf0000 (0x003dc705)
Secure Boot state: 0
bootrk: do_bootm_linux...
   Loading Device Tree to 04808000, end 04826935 ... OK
Add bank:0000000000000000, 0000000080000000

Starting kernel ...

DDR Version 1.00 20141007
In
Channel a: DDR3 200MHz
Bus Width=32 Col=10 Bank=8 Row=15 CS=1 Die Bus-Width=16 Size=1024MB
Channel b: DDR3 200MHz
Bus Width=32 Col=10 Bank=8 Row=15 CS=1 Die Bus-Width=16 Size=1024MB
Memory OK
Memory OK
OUT
******************** End of the boot listing *********************

By now the card is dead as I cannot use it. Please give me any idea how I can fix it?

I used Windows and Linux tools - the same result. It looks like the card doesn't allow to write parameters file and thus it cycled in the boot sequence.

Thank you for any help,
Vlad.

liatoss

I opened a new topic as follows: http://bbs.t-firefly.com/forum.php?mod=viewthread&tid=559

liatoss

Well, In my case, the reason of the kernel loop was the power cable. I took a USB cable from Cubieboard and it power up the board just to flash. However, as soon as the board starts, the board doesn't have enough power and the board reboots.

All of a sudden, I realized, I have another USB cable, the original one. As soon as I replaced the power cable, the board starts working and the boot continues...

By now, I can confirm the board can work in "Portrait mode" as flashing the new compiled image brought me the board in the Portrait mode even at the boot...

Thank you for your guidance,
Vlad.

liatoss

It looks like the code change doesn't work in not pad versin of the firmware. Can you clarify what shell I change in non pad version of the firmware?

Thank you, Vlad.