Which tool do I need to use to flash the single huge stock recovery img: ST10216-2A_V05.img - 495 021 284 bytes This must not be done with RKAndroidTool, right!? I don't even know how to do this with my stock recovery partition, as it seems to expect the img file to reside in the external SD, but have a specific name in order to find it.!? Sorry for my newbie questions. Will also provide dmesg and logcat output for the Bluetooth chip once I have restored the correct (non-standard) MTD layout and reinstalled CM 10.1. Alla barra sono saldate 2 staffe reggi-cristallo. Di diametro 60 per base. Futurelife mailing list to receive updates on new. ![]() Thanks again, awl. Thanks a million for your kind help! OK, I noticed that the new 'model fix' patch now additionally includes a Bluetooth kernel module! In the meantime, I have successfully recovered my old proper MTD partition setup by flashing the stock img (ST10216-2A_V05.img, see above) using RKBatchTool 1.8. So I will now (maybe tomorrow, as it's getting close to midnight.) try to install CM 10.1 again from step 1, but keeping the stock recovery img. Hopefully this will keep the Ventos MTD layout - otherwise now I at least know how to restore it. Thanks again & have a good night! Hello Oma, bad news: With the updated model fix from post 15, things are even worse: Neither WLAN nor Bluetooth now works, and we have a lot of error messages about OutOfMemory and OpenGL renderer in the catlog. For WLAN, the issue seems to be: 02-13 19:14:28.740 E/wpa_supplicant(1815): wlan0: Unsupported driver 'wext' for Bluetooth, Idn't even find any error messages, but it's simply not working. Please find both catlog and dmesg output with this setup attached. As I will only have time to look into this again after the weekend, please take your time - no need to hurry. And in case it looks like there is no easy remedy, I think we'll simply stay with the stock 4.1.1 ROM for this device. Thanks again & best regards, awl. Hello again, final update from me before the weekend. I have finally managed to create dmesg and catlog output after trying to activate Bluetooth: see attachments. This has been quite difficult, as typically, just a few seconds after trying to unsuccessfully activate Bluetooth for the first time, the kernel crashes: The tablet becomes hung/unresponsive, and I get kicked out of 'adb shell' with this message: error: protocol fault (no status) Also, I noticed that with the original stock Android 4.1.1, the WLAN driver (compiled statically into the kernel) states in dmesg log: MT5931 SDIO WiFi driver (Powered by Rockchip,Ver 2.07) init. ![]() While with your CM 10.1 (but the exact same 3.0.8+ kernel), the WLAN driver states on init (from mt5931.ko): MT5931 SDIO WiFi driver (Powered by Rockchip,Ver 1.08) init. Many thanks again in advance & have a nice weekend, awl. License key for matlab 2013 b license file crack matlab. Bad news: There are even two issues that need to be resolved with the most recent model fix from post #22: (1) Even though the MT5931 driver must be included statically in the kernel: CONFIG_MT5931=y in the kernel config, and I do not have any mt5931.ko on Trekstor's Android 4.1.1 stock ROM, with the most recent model fix on CM10.1, I still cannot activate WLAN either. (2) Also, Bluetooth still cannot be activated. I think that the model fix still contains a wrong Bluetooth driver. While you seem to have included Bluetooth drivers for MT6622 (system etc firmware MTK_MT6622_E2_Patch.nb0 and libbluetooth_mtk.so), the Ventos tablet has BCM4329 as its Bluetooth chip: CONFIG_BT_HCIBCM4325=y in the kernel config file and the dmesg file for the Trekstor 4.1.1 stock ROM says: [BT_RFKILL]: bcm4329 module has been initialized,rc=0x0 This also means that the stock kernel should already include the Bluetooth driver (as well as the WLAN driver). Still, CM10.1 does not seem to detect both drivers.!? Do you have any idea why neither WLAN nor Bluetooth do work with the CM10.1 ROM even though the kernel should include the drivers? In the meantime, I try to set up a 3.0.8 kernel compile environment for the source provided by Trekstor and will try to compile both WLAN and Bluetooth as kernel modules. Amazon s3 apis.
0 Комментарии
Оставить ответ. |
АвторНапишите что-нибудь о себе. Не надо ничего особенного, просто общие данные. Архивы
Март 2019
Категории |