Related
Hi,
I really need the cp210x.ko module, but I couldn't successfully build it properly for my Iconia A500 with 3.2.1 and 2.6.36.3+ kernel.. I get the following when I tried insmod my cp210x.ko build using ubuntu cross compiler approach:
cp210x: version magic '2.6.36.3+ preempt mod_unload ARMv5 ' should be '2.6.36.3+ SMP preempt mod_unload ARMv7 '
A little search showed that I need to build it in ARMv7, and need to set the kernel config to build SMP kernel. In this thread I saw a few modules offered but couldn't post reply as a new xda-developers user, so I post here. My A500 has already been rooted via the su (version 3) method posted few days ago.
Please help me build the cp201x.ko module - I am kinda stuck..
Bill
Bill,
Might I suggest you look at loading one of the many custom ROM's that will have what you want? If you are rooted, then install CWM (ACER Recovery from the marketplace) which should allow you to load custom ROM's. In order to load the cp201x.ko module you'd have to recompile the kernel and people doing this type of work normally are building custom ROM's.
Anyway, just my 2¢
Thanks for the advice. I am testing Thor ROM at the moment. Cool..
From what I can read and see within various ROMs /system/lib/modules, very few (out of total possible) kernel modules made it to these custom ROMs - mostly to get game controller to work, extra filesystems, or networking protocols. USB-to-serial modules are rare and certainly my search didn't turn up cp210x.
Cross-compiling the kernel source on Gentoo is mentioned to be better supported then ubuntu, due to its crossdev toolkit, as I'm trying to figure out how to specify target ARMv7 instead of ARMv5 I'm defaulting to when cross compiling from Ubuntu's arm-linux-gnueabi-*
I'm wondering if various nice ROM cooks have releases of their modified kernel source - or might be willing to help me build the just the cp210x as a .ko module, e.g. in the .config, "CONFIG_USB_SERIAL_CP210X=m" - I've found a post few months ago where a successful build and insertion of cp210x module was done but he had some problems when initiating communication on it - I fear the worst but hope for the best, and would like to try that myself as I've successfully talked to my device through the cp210x module on Linux.
Or, if any tips on how to build kernel (just the modules really) properly e.g. As Thor's ROM version number hints at need for some custom and virtualized build environment, I'm looking for the quick and dirty solution if cooking ROMs/kernel/ko's has steep learning curve..
Any help much appreciated!
Bill
It looks like I was speeding down the the wrong track last few days
Apparently the /proc/config.z copied off the a500 device was missing something - and how strange that is - so I had to enable SMP and choose Tegra 2 ARM processor using "make menuconfig" to get the vermagic on the build module (e.g. modinfo after successful make modules) to show ARMv7 and SMP, build from my Ubuntu cross-compiling setup. I haven't tested this new cp210x.ko on a500 yet (as it's currently running one of the customized ROMs that has different EXTRAVERSION/vermagic to the stock Acer kernel source version 2.6.36.3 that I'm based on.
I think it'd be really wonderful if various Android kernel and kernel module makers release their kernel config, sync'ed to each ROM or kernel release, so people like me may independently build special purpose kernel modules with more efficiency and accuracy (to target their customized kernel), and we can recontribute back to to a growing list of tested and working modules for corresponding devices.
Bill
Hmm... Silly. It looks like Thor's ROM already has cp210x build-in, not as a loadable module but compiled in. My device is reported to attach to ttyUSB0! How nice
Thanks!
Bill
For those who are interested, the cp210x.ko module build using latest mentioned approach, e.g. modified kernel config.z, generate module that appear to insert correctly into lightspeed and taboonay roms (neither has this USB-to-serial module) - with a little modification of the EXTRAVERSION variable in the Makefile.
Bill
CP210x and GT-P7500
Has anyone got CP210x module working with Samsung Tab GT-P7500? My problem is that the connected USB-device doesn't create node dev/ttyUSB*. I have spent lot of time trying to figure this one out.
I have tried 1) Manually compiling the linux kernel that has cp210x support as a module. After compiling the module I tried insmoding the cp210x.ko to a running kernel, but even though it seemed to load and unload all right, it did not give me the wanted results. It does not create device node /dev/ttyUSB*. I have also tried modifying ueventd.rc for adding this row, but I am guessing it is only relevant for permissions after the node is created.
Also 2) loading cyanogenmod 10 (which should have cp210x support) to tablet but it doesnot create the desired /dev/ttyUSB* node. I can see device file under dev/bus/usb/001/ but the node does not exist.
I am going to try making needed files for building custom kernel and inserting to tablet. However, I have 0 experience on this, I think it can be tough one.
Any help would be welcome, thanks.
Hi all!
I will try to get the Android Open Accessory (AOA) protocol into our defy/defy+.
Anybody else working on this topic?
Atm I just added the android.hardware.usb.accessory.xml file to /etc/permissions and the com.android.future.usb.accessory.jar to /system/framework (jar taken from the droid sdk API16, my fw is latest quarx CM10).
Right now I can install f.w. the ADK2012 app. So I may on the right way... but I guess that is not all the work... does anybody know if we need to add some kernel modules f.e.?
[Edit] btw... looks like we just need to add a new f_accessory.o to our usb gadget... f.e. see https://www.codeaurora.org/gitweb/q...in;h=5d9d8625e39f815673dedea353f39edccabb1fac
Best regards, Stephan
Like to know this to. If quarx managed to give us sub host, I might be able to use my duomilanove board...
Aren't there other projects for the ADK that doesn't use the protocols?
Please ask all questions in the Q&A section. Thread moved there.
Ok... I gave it a short try with the patch and quarx's linux-2.6.32 but it failed during the compiliation... but meanwhile I noticed that quarx is working on linux-3.0.8 (see its repo in github). There we have our accessory...
So I would say stay tuned for a while and let's if quarx may got this newer kernel working with our defy...
You can find all the steps needed to patch it here:
https://github.com/ezterry/manifest-gingerbread-DS/issues/32
They're saying everywere that you need 2.6.35+ kernel (don't know if it really is mandatory, kernel in the link is 2.6.34)
A kernel with the same chipset that has it enabled can be found here:
https://github.com/XDA-Bam/samsung_kernel_latona_GB
Apparently, you need to enable it in the kernel (config), add the libs to the kernel (driver/usb/f_accesory and include/linux/f_.accesory), add the lib in the framework (might be included from CM side already??), hope it will work (or debug why not).
---------- Post added at 01:21 AM ---------- Previous post was at 01:06 AM ----------
It seems that the files are indeed in the 3.0 kernel.
I already ordered a USB-host shield for my arduino a week ago, I'll try and compile a kernel with it ones it comes in the mail.
Edit:
Tried the changes I listed, will build it tomorrow (or so). Maybe then my shield might arrive to (hate waiting, stupid holidays.. )
Any place to upload it when it works?
Got something build, but it didn't include the /system/framework/com.android.future.usb.accessory.jar and got bootloop without (cause I added the /etc/permision/something_with_usb_accesory.something
Pushed the jar with adb from bootmenu (from another CM rom).
Don't have the usb_shield yet, so can't really test. Will try and install an usb_accessory app. Does someone want the build to try?
Ok, the app fails to launch.
Ok, my repo's:
Kernel: https://github.com/labsin/jordan-kernel/commits/2.6.32
Device: https://github.com/labsin/android_device_moto_jordan-common/commits/jb_2ndboot
But doesn't work. The library isn't build (in framework/base).
And it also doesn't build in the kernel... :/
Anyone??
Might it be possible to check the driver?
Edit: Found it.
It seems to many commits need to be merged in. Can't seem to find a kernel that's not based on the nexus line that has it.
If anyone is still interested in this, I managed to make an Arduino Mega ADK board with the DemoKit application work in accessory mode on my Defy
Quarx backported the USB gadget driver from 3.0.8 kernel into his 2.6.32 based kernel already a while ago. All that was still missing was the accessory configuration in init.usb.rc and the .jar and .xml files. Quarx has already merged my pull request, so in the next CM10.1 nightly with 2.6.32 kernel, USB accessory mode should work out of the box
Thnx. Already saw this actually
Hello everybody,
Before I jump into the compilation proces and uploading my build I want to ask everybody first if anybody is interested in a weekly build CM10.
I know that Ivendor is not changing his sources every week, but the base of CyanogenMod is under constant development, so changes in the CyanogenMod source will be up to date again.
Let me know if you're interested by replying to this thread.
Also if theres enough interest in a build with kernel 3.0 inside I'm also willing to upload this image as well.
Because already one person replied I'm willing to share my compiled image. After all it's already compiled.
This build is compiled against ivendors sources on his Github and the latest CyanogenMod sources which were available.
Of course this image is already tested on my phone and everything seems to work like it did on Ivendor's last build.
Because Ivendors sources haven't been changed, this build still has the same bugs as his build.
To be complete the following:
- Vsync doesn't work, because the current kernel doesn't support this yet.
- Panorama shots
- Also mobile internet has a little glitch, which only appears to happen if you have a Pin locked SIM.
Solutions to this are:
* Setting the phone into Airplane Mode and back to normal. This should load the needed module.
* A more clean solution is to use the patch provided at: d-h.st/BgH This patch can be applied through CWM.
- Also camera view is upside down, but this is not noticable in the final saved image. (Don't know if this is a new or already known bug I don't use camera that much).
You can download my build from: mediafire.com/?m765ok5mtly7l6h
You have to copy the links into you're adress bar, because I'm not yet allowed to post outside links.
If anyone has questions feel free to ask.
Greetings PsychoGame
a weekly build would be nice
i don´t use the 3.0 kernel because of the not working camera
i hope it changes soon
Hereby I updated my thread and put in the links to where you can download my build.
Greetings PsychoGame
PsychoGame said:
Hereby I updated my thread and put in the links to where you can download my build.
Greetings PsychoGame
Click to expand...
Click to collapse
Great idea. You can use 2 builds,one with 2.6 kernel, second with 3.x
it would be very great
Sent from my GT-I9001 using xda premium
Latest Thread update
This section is to alert returning readers to new sections or information as they are added. New readers, please start at "Introduction"
17th Jul 2013 - Added Googy-Max. I thought this thread was dead
21st Jun 2013 - Request: Please don't ask if x.x.x (new release) has SDS fix. See "***" at end of post 1.
19th Jun 2013 - Added Official CWM Link in safe recoveries (Please only use links provided)
18th May 2013 - Revised "Stock section" to be more succinct
13th May 2013 - Added Devil kernel to safe list
3rd May 2013 - Added more about SDS v half SDS in the "What do we think we know" section
12th Apr 2013 - tried to distinguish between Fix 1 and Fix 2
6th Mar 2013 - Added ICS boaotloader to "Other links"
25th Feb 2013 - Added "Other Links" section at end of post 1
26th Jan 2013 - Update on bootloader requirement, courtesy of AndreiLUX
Previous: Added Speedmod K2-5 Test 1 Kernel
Previous: Added quotes around the fixed items for visual prominence
Introduction
Hi All,
I am seeing a lot of Buzz about the Sudden Death issue and recent fixes identified by AndreiLux and implemented into his Kernel here:
http://forum.xda-developers.com/showthread.php?t=1691401 so please take a moment to thank him.
Unfortunately as there seems to be some uncertainty about what is or is not covered by the Fix, I have put this thread together to eliviate some of the many off topic questions posed by members in development threads, which is unfair on the developers.
So what do we think know?
Please be aware, this is not related to the Exynos Memory security issue.
The "Sudden Death" issue is caused by firmware on the (16 GB) VTU00M, revision 0xf1 eMMC (Embedded MultiMedia Card or internal memory if you like). Samsungs Kernel Source Code (Update 7) has been identified as the fix. There is still no evidence that the latest sboot bootloader addresses this issue.
Although we are still not quite 100% Certain this will prevent all S3's suffering the SDS (Predisposition to the fault etc), to the best of our knowledge it does. Even if it does not fully fix it, its closer to a fix and safer than older versions, so if its within your means to do so, an update would be advised. Please don't panic. If it's going to happen, it's going to happen and that's that. It will be repaired under warranty. I had to use a Bold 9000 for 7 days whilst mine was repaired
SDS seems to manifest in 2 distinct ways.
1) Complete eMMC failure. This usually happens over night whilst on charge* - The LED may be lit but the phone will not wake. Subsequent removal of the battery will turn off the LED. You will never get the LED back on. The phone will never turn on again. It needs to go to a service centre and have the motherboard replaced
* Being on Charge is NOT the cause. This is a writing to memory issue and it is more likely to happen when teh device is awake rather than in deep sleep. When the S3 is on charge, it holds a wake lock (so remains awake) throughout the entire charging period, meaning SDS is more likely to occur when on charge This does not mean you should avoid charging your phone. If it's going to happen, it's going to happen
2) Half SDS as it has not-so-affectionately become known. This tends to be more of a boot loop of the Samsung boot splash. the eMMC is partially wiped out. You cannot boot into android or recovery. It fails at the boot screen, but the screen does turn on none-the-less. The only; thing you can do is top boot into Download mode.
One problem Half SDS has is that the information download mode uses to show the status as "Official" appears to be wiped out by the bug, leaving your status as "Custom". This can leave you in a precarious position as this is what Samsung uses to establish warranty validity. You may also see your product field is blank.
Please help me maintain this list by identifying fixes as and when released, Please post the Link and Version number of anything with this fix implemented
How do I check my eMMC?
Using the EMMC check app from play, you can see if your eMMC is the VTU00M 0XF1 (affected chip).
Please note:
1) We only need this app to check the version.
2) Nothing you see in this app will change once you apply a fix. It simply gives you the version. If you expect 0xf1 to change to something else, you are mistaken. Only replacing the motherboard will do that.
What do I need to be "Safe"?
The "Fix" is actually a preventative measure. It cannot revive a "dead" device. It has to be applied before failure.
To be 100% safe, you need:
A bootloader with fixes**
[*]A Recovery with a fixed kernel
[*]A Fixed kernel to run Android
If you are a normal user only using official releases (no custom ROMs, Kernels or recoveries) then we treat you as "Stock" - read on.
Lets get to it... Where is it fixed?
Stock:
All 4.1.2 official releases (stock) include a Kernel, bootloader and recovery with the Update 7 "Fixes" (or newer) applied. If you have 4.1.2, officially consider yourself "Safe".***
Stock (but rooted):
If you rooted a 4.1.2 stock ROM, you will still be safe, however - if you changed to a custom kernel or recovery, you need to look at the below custom sections to ensure your kernel or recovery are listed as safe.
The below official kernels were tested, but we no longer need to test. All 4.1.2 (stock) kernels and newer have fixes.
XXELKC
XXELL1
XXELL4
XXELL5
XXELL6
XXELLA
XXELLB
XXELLC
Fix v1
Please note, you may experience freezes and /or reboots using a Fix v1 ROM (Well actually kernel that is included in this ROM). Essentially any Stock 4.1.2 ROM between:
LKC and MA2
Which means:
2012 November revision 12 and 2013 January Revision 2
...may experience freezes due to the way the fix works. This is annoying but better a freeze than a motherboard replacement.
Fix v2
From what appears to be Update 8 sources (MB1 onwards), the fix seems to be much better with far fewer freezes. I haven't included the MR* vodafone ROMS because who knows? They don't follow the standard naming convention. All I can say is MR2 came out when MBx was around (B = February) but is still only fix v1
People who have never rooted need not read any further. Essentially, if you have an official, never rooted 4.1.2 ROM, you're "safe"
Click to expand...
Click to collapse
-------------------------------------------------------------------
Custom ROMs which include a ROM specific and dedicated kernel (including fixes):
These are custom ROMs that have their own kernel that is not flashable separately. This means it is not packaged with a kernel from the "Custom Kernels" section. If you have the version specified or newer, you are "safe"
Any 4.1.2 (or newer) TouchWiz ROM with a repacked, stock kernel - no need to list them all.
HydRx-D v2.2.1r1 (TW)
CM 10.1 Nightly 20130109 (AOSP)
Tamasek's Unofficial CM10.1 v32 (AOSP)
ReVolt JB Nightly 20130111 (AOSP)
Click to expand...
Click to collapse
Custom Kernels:
These kernels include the update 7 fixes (or newer). If you are rooted with a custom Kernel that is older than (or doesn't match) the versions below, you are not considered "safe"
Perseus Alpha31+ (i9300 TW)
Boeffla 2.6 Alpha1 (i9300 TW
Speedmod K2-5 Test 1 )i9300 TW)
Yank555.lu 3.0a (i9300 TW)
Siyah 1.8.7 (i9300 TW & AOSP)
Devil ALL Versions (i9300 TW & AOSP)
Googy-Max ALL versions (i9300 TW & AOSP)
Yank555.lu 1.4 (i9300 AOSP)
Click to expand...
Click to collapse
Custom Recoveries:
Since the recovery uses a kernel too, to be "safe", the recovery's kernel must also be fixed.
PhilZ Touch 4.00-b04 (i9300)
Siyah 6.0.1.4 (Siyah Kernel users only)
TWRP 2.3.3.1
CWM.img from clockworkmod.com CWM.tar from mskip (6.0.3.2)
CF-auto-root (stock recovery supplied with this)
Click to expand...
Click to collapse
Please be weary of CWM. It can be compiled by anyone which means we cannot guarantee all versions have the latest fixes. Please only download from the links posted above
Obviously, rooted users are probably more familiar with what to do. I don't really want to recommend non-techy people flash official firmwares if they are not comfortable doing it. There will be a fix on its way to you all soon anyway, so the worst that will happen is you are affected and you have to get your phone repaired...
For those who are technical but would prefer to follow an Odin flash guide for official firmware, read the appropriate section here:
http://forum.xda-developers.com/showthread.php?t=1671969
Recap
So to recap, if you checked you have VTU00M 0xf1 with EMMC check , you need to ensure:
If unrooted (never rooted / modded), you are on one of the "Stock" ROMs listed above
If rooted, you have one of the "Custom Kernels" OR "Custom ROMs including kernel" OR rooted "stock" with original kernel AND one of the "Custom recoveries" from the lists below
**Bootloader note
Download mode uses a bootloader packaged micro-kernel
It will only affect those who use download mode. Personally I am rooted so I don't use it so i'll be sticking with one that doesn't mess with the flash counter, however anyone who does use download mode should consider updating. Those who care more about flash counters and will stay with older bootloaders should avoid flashing anything in download mode
*** Please do not ask if newer builds (either not mentioned here, or newer than 4.1.2) include the fixes.
Samsung have a single repository of kernel source code. They continue to develop this code. When they add a fix, it's there forever in every new kernel built after the fix is added. Every fix is in new kernels automatically. They do not have a list of fixes they must add every time.
The only way a new kernel does not contain a fix is if it is manually (and specifically) removed from the source code. Can you think of any logical reason why they would do that?!
Other Links
Ultimate Unusual Freezing thread (The fix causes Freezing, possible solutions)
Ultimate SDS thread (Further discussion of the SDS issue)
ICS Bootloader for those who want to keep custom counter at 1
In another thread a guy got a SDS after flashing ELLA via Odin, so that's weird at least
Yank's kernel has the fix too, I think.
Two questions:
1. When boot into Download Mode- is it safe?
2. Someone said about charging the phone when it is off and off the wallsocket. How about the fix/security then?
Glebun said:
In another thread a guy got a SDS after flashing ELLA via Odin, so that's weird at least
Click to expand...
Click to collapse
Could the failure process already have started? I'll put a caveat next to that....
rootSU said:
Could the failure process already have started? I'll put a caveat next to that....
Click to expand...
Click to collapse
As far as i know he had siyah kernel installed
BTW cm team add the patch too
http://review.cyanogenmod.org/#/c/29932/
yahyoh said:
BTW cm team add the patch too
http://review.cyanogenmod.org/#/c/29932/
Click to expand...
Click to collapse
Thanks. Signed off my Andrei today so I assume that appears in tonights nighty?
#
Sorry guys, ran out of thanks today
It appears the fix is in some older kernels too, but there has definitely been instances of SDS on those, so it's possible that the fix found in update 7 is not the whole story.
theslashy said:
As far as i know he had siyah kernel installed
Click to expand...
Click to collapse
That would make sense as its the kernel not the rom that has the fix. Has anyone got a link please?
mjb said:
It appears the fix is in some older kernels too, but there has definitely been instances of SDS on those, so it's possible that the fix found in update 7 is not the whole story.
Click to expand...
Click to collapse
Best we have right now is from Andrei stating it *looks* complete, but I agree we just cannot know everything for sure yet. I changed teh op to say "what do we think we know"
Great thread. Hope for news regarding the recovery.
Its allways a risk to flash via odin. Anything could of happened during the flash. Am I goin crazy or does everyone not know that all ready. We allways flash at our own risk! Need to keep this issue real. Some people think they have a tickin time bomb in there pocket. Boom!
Sent from my GT-I9300 using xda premium
PhilZ Touch 4.00-b04
Download:
- odin: http://www.mediafire.com/file/3g6ke58rsvs3j8y/philz_touch_4.00-b04-i9300.tar.md5
- cwm: http://www.mediafire.com/file/m6z7wwrd20pd9ln/philz_touch_4.00-b04-i9300.zip
This version wouldn't have been pushed as I did not plan any updates of the binary before 4.00 Final. But since we needed a repack with XXELLA kernel and the code was ready for these changes, I pushed it.
Changes:
- Repack with XXELLA kernel supposed to be SDS safe
- Fix romname added to nandroid backups: now build.prop will be parsed instead of reading system properties
- Custom rom.zip scripts completely revised to add a bit of process progress (beta and will be completely revised in Final build)
Click to expand...
Click to collapse
I do not feel like it is so much of a risk to flash via odin. Unless you are a noob. I am a noob but I usually read a lot before doing anything on my device.
montage mahal said:
Its allways a risk to flash via odin. Anything could of happened during the flash. Am I goin crazy or does everyone not know that all ready. We allways flash at our own risk! Need to keep this issue real. Some people think they have a tickin time bomb in there pocket. Boom!
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Yes indeed but ts a real issue even if you never flash anything.
rootSU said:
Best we have right now is from Andrei stating it *looks* complete, but I agree we just cannot know everything for sure yet. I changed teh op to say "what do we think we know"
Click to expand...
Click to collapse
Good.. I think the patch is complete too, but my concern is that we just don't know if this is addressing SDS, another fault, or just part of SDS and there is actually more to the problem than what this patch is "fixing".
I only say this due to finding the strings in the patch in older stock kernels, where people have experienced SDS.
mjb said:
Good.. I think the patch is complete too, but my concern is that we just don't know if this is addressing SDS, another fault, or just part of SDS and there is actually more to the problem than what this patch is "fixing".
I only say this due to finding the strings in the patch in older stock kernels, where people have experienced SDS.
Click to expand...
Click to collapse
Yep no worries. I have reworded the OP a little more to reflect. Please feel free to help me phrase it
I think that best solution is to flash PhilZ Touch 4.00-b04 as is based on XELLA (secure) and using XELLA reom with kernel or Perseus. PhilZ recovery works with exfat - Yank kernel not - so is for me useless
Great news! I hope with this recovery we can avoid SDS issues!.
Thanks for your help and effort
Thanks rootSU for all your support (sorry, out of my 8 thanks as always)
Just an edit to the op: stock recoveries: instead of none, maybe add XXELLA
Bye
I am trying to build a custom kernel for my redmi 2 running on Nexus Experience. I found there kernel source at their github page in nx_kernel_xiaomi_msm8916 . It's the only kernel referring to XIAOMI so I think it is the right one.
I am really new to kernel building. I read some tutorials on the web and tried building one for the stock miui rom but it didn't work out.
So before I start re-building the kernel for Nexus Experience I had some questions. I wanted to add the support for external wifi adapters based on RTL8188CUS. I found the option to enable it. My question is that , By just enabling that feature will my phone just start supporting the adapter out of the box or do I have to add some Modules to it.
And the last question, After I compile the kernel I get this zImage file. I put this file in the anyKernel.zip but I found that I also have to add the wlan.ko file and I couldn't find it....
I really need some help here.