Forum switched to read-only as of 2020/06/01


Latest product reviews
ARCHOS 50 Diamond
ARCHOS GamePad2
ARCHOS
Smartphones
ARCHOS
TV Connect
ARCHOS 101 XS

A A A
Avatar

Please consider registering
Guest

Search

— Forum Scope —






— Match —





— Forum Options —





Minimum search word length is 3 characters - maximum search word length is 84 characters

Register Lost password?

ClockworkMod (CWM) Recovery easy install for RK3066 and RK3188 -- TWRP/CWM Flash-Tool and root for RK3288

 Please donate to support OMA and CrewRKTablets firmware work, thank you !

sp_Feed sp_TopicIcon
KitKat has landed on rk30board ;-)
Avatar
santhoshkarthik123
New Member
Forum Posts: 7
Member Since:
2013/12/09
sp_UserOfflineSmall Offline
16
2013/12/14 - 18:51
sp_Permalink sp_Print

Oma7144 said
Attached the kernel.img. Replace in the download pack.

Do not flash the loader from the download pack!

 

- Oma -

 

 

Hi oma.. i just flashed your rom with loader unticked and the kernel.img you gave.. the system boots into recovery even if reboot to system is given.. how to solve this??

 

Avatar
santhoshkarthik123
New Member
Forum Posts: 7
Member Since:
2013/12/09
sp_UserOfflineSmall Offline
17
2013/12/14 - 19:07
sp_Permalink sp_Print

Oma7144 said
Attached the kernel.img. Replace in the download pack.

Do not flash the loader from the download pack!

 

- Oma -

 

 

i just now flashed your rom ..but it boots only into recovery .. shows the following error in recovery ..

 

E: Can't mount /cache/recovery/last_log

E: Can't open /cache/recovery/last_log

E: Failed To mount /cache (No such file or directory)

E: Can't mount /cache/recovery/last_install

E: Can't open /cache/recovery/last_install

E: Can't mount /cache/recovery/last_log

E: Can't find misc

E: Failed To mount /cache (No such file or directory)

Avatar
daniel000
New Member
Forum Posts: 9
Member Since:
2013/11/30
sp_UserOfflineSmall Offline
18
2013/12/15 - 23:10
sp_Permalink sp_Print

cappybob said
@ Daniel

  Howdy again.

  Tried the 4.4 with the cube kernel since it was a Homebrew which looks as though it was backported from and with the 3.0.36.  Hybred 3.0.66, also with different recoveries,  the 3.0.8 looked to be debugable, but resolution problems.  So as of right now there is hope, but not working, and I do not have the knowledge to proceed with resolution and kernel.  Netlars and Oma will have us cooking fairly fast, but really hate to give up on 4.2.2 for it is really a sweet OS, KitKat will have to be really awesome for me to step up.

 

Latter

 

 

Thanks cappy. I really like 4.2.2 as well and dont think I will try KitKat for sometime! Thanks for the information!

Avatar
watdub
Dublin, Ireland
New Member
Forum Posts: 2
Member Since:
2013/10/07
sp_UserOfflineSmall Offline
19
2013/12/24 - 22:09
sp_Permalink sp_Print

Oma7144 said
Build will only run on a 3.0.36+ kernel. So for the moment no backport to a 3.0.8+ kernel. But hey, we are right at the beginning ....

 

- Oma -

Sorry, I'm (very) new to this but 3.0.36+ is earlier than 3.0.8+?  So something that works on 3.0.36 should work on a later 3.0.8 kernel?  Or am I missing something really obvious?

 

I'm on a Cube U30GT-H and would love to see kitkat on it...  Just installed my first custom ROM so really taking baby steps at this stage, lol.

 


Avatar
JochenKauz

Moderator

Firmware Guru
Forum Posts: 450
Member Since:
2012/11/19
sp_UserOfflineSmall Offline

Thanks Received: 76
20
2013/12/25 - 19:53
sp_Permalink sp_Print

3.0.36+ is a younger kernel release than 3.0.8+ and you can normally not mix modules between kernel releases.

Unfortunately even young tablets have "old" kernel.

But to be more precise, all Android Tablets have very old kernel (3.0.xx), mainline kernel for Linux are 3.12.xx and 3.13.xx is in test-phase.

The following users say thank you to JochenKauz for this useful post:

watdub
Avatar
GaBOr
New Member
Forum Posts: 3
Member Since:
2013/12/27
sp_UserOfflineSmall Offline
21
2013/12/27 - 19:03
sp_Permalink sp_Print sp_EditHistory

Hello, everyone,

First of all, thank you very much for your work. You all do a lot more for these devices than RockChip itself...

I have a BQ Maxwell 2 Lite, a rk3066-based tablet with 3.0.8+ kernel. So far, I've succesfully modified this kernel to run the version CWM that comes with CM11 just by building the SELinux modules (and the required options of the EXT filesystems). Nevertheless, I'm unable to make CM11 boot in the device. Actually, I cannot even debug it, since ADB cannot connect to it. I have to say I haven't tried to run a simpler init.rc, though, for debugging purposes.

I also have what is supposed to be the RK4.2.2-SDK, but I don't find anything that would be worth saying. It just includes the code for the sensors, lights, power libraries... (maybe some more I forget right now).

I've also tried to run your cROM by changing the kernel modules with the ones for this kernel, but I had no success. However, I was able to debug this time, and it was possible to see that surfaceflinger was not able to start:

D/libEGL  (  658): loaded /system/lib/egl/libEGL_mali.so
D/libEGL  (  658): loaded /system/lib/egl/libGLESv1_CM_mali.so
D/libEGL  (  658): loaded /system/lib/egl/libGLESv2_mali.so
W/libEGL  (  658): eglInitialize(0x1) failed (EGL_BAD_ALLOC)
E/[Gralloc-ERROR](  658): int alloc_device_open(const hw_module_t*, const char*, hw_device_t**):614 UMP open failed with 1

[...]

I/SurfaceFlinger(  658): Using composer version 1.3
D/hwcomposer(  658): hwc_getDisplayAttributes disp = 0, width = 1024
D/hwcomposer(  658): hwc_getDisplayAttributes disp = 0, height = 600
W/SurfaceFlinger(  658): no suitable EGLConfig found, trying a simpler query
F/SurfaceFlinger(  658): no suitable EGLConfig found, giving up
F/libc    (  658): Fatal signal 6 (SIGABRT) at 0x00000292 (code=-6), thread 658 (surfaceflinger)

Nevertheless, I read in a previous reply that it is also necessary to replace some libraries.

So, I would like to ask you whether you are going to update your Github repository with the latest changes for this version of Android. Else or aditionally, could you give me some suggestions of what I'm doing wrong? Are the *.rk30board.so libraries or any other dependent on something (like the Android version)? What did you need to modify in the sources to make it run?

 

Looking forward to hearing from you,

Gabriel.

Avatar
GaBOr
New Member
Forum Posts: 3
Member Since:
2013/12/27
sp_UserOfflineSmall Offline
22
2013/12/31 - 18:02
sp_Permalink sp_Print

Well, I guess nobody knows what happens here.

Recently, I've been able to rebuild the mali.ko and ump.ko kernel modules, and the result with CM11 is more or less the same as the one I stated in the previous post. This leads me to think that it might be caused by something I'm missing in the kernel.

I've also seen that in your repository "rk3x_kernel_3.0.36", you had to modify some files related to the framebuffer in order to make it compatible with KitKat, but it seems that you made a huge commit with other unrelated changes, so it is hard to see anything as clear as it should be.

Any hint, @JochenKauz?

Thanks in advance.

Avatar
JochenKauz

Moderator

Firmware Guru
Forum Posts: 450
Member Since:
2012/11/19
sp_UserOfflineSmall Offline

Thanks Received: 76
23
2014/01/01 - 14:54
sp_Permalink sp_Print

Hi,

Happy new year first....

 

You're right, in the framebuffer commit are some changes not directly related to the framebuffer itself.

Unfortunately the changes for the adc_battery were committed too.

But to see it clearer, you only have to ignore anything related to adc_battery.

The huge commit was the result of a completely change of drivers/video/rockchip to another version. This change was needed, because old driver was not correct for tablets. The base of the 3.0.36 kernel is a BQ Curie which was delivered very early 2013, but it was not correct for framebuffer handling as tablets needs it. I think that the base release of the kernel source was a mix of tablet and TV-Stick source. Something we often see if a kernel source is released.

A few things you can check..

What toolchain did you use for building the kernel/kernel modules? Only toolchain that work for me is a gcc gnueabi 4.4.3. Everything above this, results in not booting or early dying Android.

What display is used in the Maxwell 2? Same as in Odys Genio?

Our custom rom needs a 3.0.36er kernel, it will not run with 3.0.8. Did you use an own kernel build for your tries?

 

 

The following users say thank you to JochenKauz for this useful post:

GaBOr
Avatar
GaBOr
New Member
Forum Posts: 3
Member Since:
2013/12/27
sp_UserOfflineSmall Offline
24
2014/01/04 - 16:27
sp_Permalink sp_Print

JochenKauz said
Hi,

Happy new year first....

 

You're right, in the framebuffer commit are some changes not directly related to the framebuffer itself.

Unfortunately the changes for the adc_battery were committed too.

But to see it clearer, you only have to ignore anything related to adc_battery.

The huge commit was the result of a completely change of drivers/video/rockchip to another version. This change was needed, because old driver was not correct for tablets. The base of the 3.0.36 kernel is a BQ Curie which was delivered very early 2013, but it was not correct for framebuffer handling as tablets needs it. I think that the base release of the kernel source was a mix of tablet and TV-Stick source. Something we often see if a kernel source is released.

A few things you can check..

What toolchain did you use for building the kernel/kernel modules? Only toolchain that work for me is a gcc gnueabi 4.4.3. Everything above this, results in not booting or early dying Android.

What display is used in the Maxwell 2? Same as in Odys Genio?

Our custom rom needs a 3.0.36er kernel, it will not run with 3.0.8. Did you use an own kernel build for your tries?

 

 

Hi again,

First of all, I apologize for the delay. I'm quite busy and, unfortunately, I can't work in this as often as I would like...

Yes, as I suppose you already know, there are lots of TV-Sticks based on RK3066. That might be the reason why the kernel seems oriented to that kind of devices. Anyway, if I'm not wrong, I think that BQ released another version of the 3.0.36+ kernel for their Quad-Core tablets, but I don't know if the source code has been improved or not.

And as far as your hints are concerned,

  • Yes, I've been using that toolchain for building the kernel.
  • I supposed these devices used the same display, but now that you say so, I'm not that sure. Both have a Mali400 GPU, but different LCD. Another problem might be the Mali drivers, as my device has r3p2rel0, and I think you updated Odys Genio to r4p0.
  • Yes, I used my own kernel (3.0.8+) and changed the kernel modules of the ROM without success. As a result, I had the log I posted in #21. I suppose that's not enough at all, as there are many other shared libraries and dependencies, but it was a first approach.

Anyway, don't worry too much about it. I'll try some things to see if I can fix it.

If I get something new, I'll tell you.

Thanks again!

Avatar
g440i
Member
Forum Posts: 12
Member Since:
2013/12/22
sp_UserOfflineSmall Offline
25
2014/01/12 - 15:47
sp_Permalink sp_Print

Hi everyone,

 

So, can I use this to my Pipo M3 wifi, which has 1280x800 resolution?  How to flash it?  I have just installed CWM.

 

Also, if Kitkat is not ready yet, is there any 4.3 ROM that can use on Pipo M3?  I'd like to get the TRIM function.

 

Thanks!

Avatar
Oma7144

Moderator

Firmware Guru
Forum Posts: 6315
Member Since:
2012/10/06
sp_UserOfflineSmall Offline

Thanks Received: 1386
26
2014/01/12 - 16:00
sp_Permalink sp_Print

Due to lack of adequate kernel (3.0.36+ or higher) and mali driver there will be very limited benefit from Android 4.3 or 4.4.

Latest kernel for Pipo M3 is a 3.0.8+ kernel. I'd recommend our CM10.1 build.

 

Latest kernel for Pipo M3:

- old PCB http://crewrktablets.arctablet.com/?wpfb_dl=848

- new PCB http://crewrktablets.arctablet.com/?wpfb_dl=842

 

Latest CM10.1 build is here: http://crewrktablets.arctablet.com/?p=1913

 

- Oma -

 

 

 

 

 

Avatar
g440i
Member
Forum Posts: 12
Member Since:
2013/12/22
sp_UserOfflineSmall Offline
27
2014/01/13 - 03:04
sp_Permalink sp_Print

Oma7144 said
Due to lack of adequate kernel (3.0.36+ or higher) and mali driver there will be very limited benefit from Android 4.3 or 4.4.

Latest kernel for Pipo M3 is a 3.0.8+ kernel. I'd recommend our CM10.1 build.

 

Latest kernel for Pipo M3:

- old PCB http://crewrktablets.arctablet.com/?wpfb_dl=848

- new PCB http://crewrktablets.arctablet.com/?wpfb_dl=842

 

Latest CM10.1 build is here: http://crewrktablets.arctablet.com/?p=1913

 

- Oma -

 

 

 

 

 

so, no chance for enabling TRIM anymore? because my pipo m3 running slow when i installed more apps (actually not very much, just around 70 apps).

 

BTW, I guess as there is kitkat for S1, so the kernel for RK3066 should be ready.  Correct me if I'm wrong.

Avatar
JochenKauz

Moderator

Firmware Guru
Forum Posts: 450
Member Since:
2012/11/19
sp_UserOfflineSmall Offline

Thanks Received: 76
28
2014/01/13 - 10:05
sp_Permalink sp_Print

g440i said

BTW, I guess as there is kitkat for S1, so the kernel for RK3066 should be ready.  Correct me if I'm wrong.

Old rule, every tablet has it's own kernel (except it is a clone from another).

If there is no 3.0.36 kernel for a tablet, it can not be used for Kitkat, which needs it at this time.

Avatar
g440i
Member
Forum Posts: 12
Member Since:
2013/12/22
sp_UserOfflineSmall Offline
29
2014/01/14 - 09:36
sp_Permalink sp_Print

g440i said

BTW, I guess as there is kitkat for S1, so the kernel for RK3066 should be ready.  Correct me if I'm wrong.

Old rule, every tablet has it's own kernel (except it is a clone from another). If there is no 3.0.36 kernel for a tablet, it can not be used for Kitkat, which needs it at this time.

 

how about the source code here for the kernel?

 

https://github.com/omegamoon

Avatar
JochenKauz

Moderator

Firmware Guru
Forum Posts: 450
Member Since:
2012/11/19
sp_UserOfflineSmall Offline

Thanks Received: 76
30
2014/01/14 - 14:20
sp_Permalink sp_Print

g440i said

how about the source code here for the kernel?

I think you misunderstood something about the kernel sources.

You can look at our repo too, and you will find RK3066 sources there.

But that's not the point. This kernel sources work for specific RK3066 devices, but not for all RK3066 devices.

Cause Rockchip builds RK3066 devices for different distributors, they all have different components build in, different Touchscreens, different LCD, different rotation sensors, different batteries, and so on.

As an example, Omegamoon builds TV-Sticks, the have no LCD, no battery, no rotation sensors.

The released kernel sources of Rockchip are mostly incomplete in this parts and without the correct parameters for the components and correct drivers, you are not able to get the devices running.

 

Forum Timezone: Europe/Paris

Most Users Ever Online: 803

Currently Online:
206 Guest(s)

Currently Browsing this Page:
1 Guest(s)


Devices in use: Desktop (192), Phone (14)

Top Posters:

finless: 604

DarthJabba: 551

maikal: 394

mussonero1: 350

alex: 252

damo: 243

DanielVd: 237

Mark06: 222

Newest Members:

ppaofe

kabelodinternetu

waterwall

sufak79

ntukinal

Miguelcnc

Forum Stats:

Groups: 10

Forums: 185

Topics: 6037

Posts: 60500

 

Member Stats:

Guest Posters: 43

Members: 262194

Moderators: 5

Admins: 1

Administrators: admin

Moderators: globula_neagra, exelletor, JochenKauz, Oma7144, cracktech


CrewRKTablets moderators: JochenKauz and Astralix