Jump to content

ALL ABOUT KERNEL SOURCE,KERNEL PARTITION,STORAGE ETC(F1,A310,POLYMER)


Recommended Posts

Guest prshkr07
Posted

i guess it's not what u telling....if that thing is true then coolpad f1 kernel never boot on mmx devices

may be u r right but just because of a single improper sensor driver (espically like accelerometer), is it necessary that it won't boot ?

i am saying this because i am having another android device (karbonn a5) and karbonn a7 kernel having different touch driver boot on my a5 too but touch doesn't work.

Guest prshkr07
Posted (edited)

coolpad f1 accelerometer driver in all their kernels (except laek v3 kernel):

post-1048448-14167666973382_thumb.png

Edited by prshkr07
Guest prshkr07
Posted (edited)

mmx nitro accelerometer driver in its own kernel (rest all drivers are same):

post-1048448-1416766948641_thumb.png

Edited by prshkr07
Guest prshkr07
Posted (edited)

hardware disabler and sensor box for android

Edited by prshkr07
Guest m@nish123
Posted (edited)

yes u were ryt....that's why accelerometer not working on custom.and clones rom if we tried with changed kernel (mmx).....it stuck after logo....thanks for clear

bt still i got a doubt....if accelerometer hardware is diff,,,then how leaks v3 kernel working fine with all sensor in mmx and also in coolpad f1 too

Edited by m@nish123
Guest prshkr07
Posted

yes u were ryt....that's why accelerometer not working on custom.and clones rom if we tried with changed kernel (mmx).....it stuck after logo....thanks for clear

bt still i got a doubt....if accelerometer hardware is diff,,,then how leaks v3 kernel working fine with all sensor in mmx and also in coolpad f1 too

yes that thing is mystery for me too! (seems like their accelerometer hardware is compatible with both drivers but ours not)
Guest m@nish123
Posted

yes that thing is mystery for me too! (seems like their accelerometer hardware is compatible with both drivers but ours not)

well gn...tommorrow is my exam....will check and confirm tommorrow....whether driver is diff or same....
Posted

You know, it is really nice to see several folks here that have a deeper

android knowledge :)

Thanks guys for sharing and discussing that stuff here! :D

Guest Alg0r1thm
Posted

I an on laek v4 using v3 kernel. This kernel is made by coolpad (as inforned by friends here). Since there is no lsmod command i searched for all avavailabe DYNAMICALLY loaded kernel modules:

root@Coolpad8297W:/ # find / -name '*.ko'

/system/lib/modules/lowmemorydetect.ko

/system/lib/modules/p2p.ko

/system/lib/modules/wlan.ko

As you see there is almost nothing built as a module and probable everything resides in the kernel.

I am studying the feasibility of ripping statically linked modules from an already compiled kernel and making things dynamic with rc hacks but don't know if this will lead anywhere.

I need to get on my laptop and rip apart the boot.img from my rom as well the micromax one.

Guest m@nish123
Posted

I an on laek v4 using v3 kernel. This kernel is made by coolpad (as inforned by friends here). Since there is no lsmod command i searched for all avavailabe DYNAMICALLY loaded kernel modules:

root@Coolpad8297W:/ # find / -name '*.ko'

/system/lib/modules/lowmemorydetect.ko

/system/lib/modules/p2p.ko

/system/lib/modules/wlan.ko

As you see there is almost nothing built as a module and probable everything resides in the kernel.

I am studying the feasibility of ripping statically linked modules from an already compiled kernel and making things dynamic with rc hacks but don't know if this will lead anywhere.

I need to get on my laptop and rip apart the boot.img from my rom as well the micromax one.

hey algorithm....can u share me v3 kernel's uboot.bin (lk.bin)....and for modules ....in kk modules removed from mtk...so no more module except wlan and some other........bt we mmx user facing grt problem....even we can't use own mmx kernel in other rom as it stuck after logo
Guest Alg0r1thm
Posted

I tried booting mmicromax kernel on laek rom but it hangs waiting so it must be missing drivers.

Regarding uboot.bin that you asked for: you mean extract it using mtk droid tools?

I need to get to my laptop at home to do that. I "ll try when i get home.

Guest Alg0r1thm
Posted

Probably only sp flash tool can dump uboot.bin as i see. I ll try later :-)

Guest m@nish123
Posted

Probably only sp flash tool can dump uboot.bin as i see. I ll try later :-)

thanks..this file will fix high brightness(mean light and power sensor won't work) bug on emui 3.0 which is due to aal services error

Guest m@nish123
Posted

Probably only sp flash tool can dump uboot.bin as i see. I ll try later :-)

thanks..this file will fix high brightness(mean light and power sensor won't work) bug on emui 3.0 which is due to aal services error

Guest m@nish123
Posted (edited)

Guys...so the diff in between mmx nitro a310 and in coolpad f1 is accelerometer....mmx used diff accerelomerter sensor thats why we face accerelometer bug on custom roms...

bt via using leaks v3 kernel...we won't face cuz in leaks v3 kernel there is accerelometer sensor of mmx not coolpad f1....

 

coolpad f1- accerelometer sensor name --->BMA250

 

micromax nitro-accerelometer sensor name -->lis3dhtr

 

still there is doubt ....in leaks v3 kernel,mmx kernel there is no accerelometer sensor of coolpad f1 then how it works well on coolpad f1 ....but may be in future leaks v3 kernel , mmx ,coolpad f1 user face accerelometer sensor hardware failure......

Edited by m@nish123
Guest Alg0r1thm
Posted (edited)

Ok m@nish123 :
I did a full backup using mtk droid tools and as it seems i now have an lk.bin file 393.216 bytes.
Here it is :https://www.sendspace.com/file/1t32ht

 

I hope this is the one you are looking for.

 

Edit: I also just checked my coolpad f1 accelerometer driver and it is LIS3DH. (Ok this seems to be the case in laek roms according to a previous post i missed).

Edited by Alg0r1thm
Guest m@nish123
Posted (edited)

Ok m@nish123 :

I did a full backup using mtk droid tools and as it seems i now have an lk.bin file 393.216 bytes.

Here it is :https://www.sendspace.com/file/1t32ht

I hope this is the one you are looking for.

Edit: I also just checked my coolpad f1 accelerometer driver and it is LIS3DH. (Ok this seems to be the case in laek roms according to a previous post i missed).

Thanks for uboot.bin

here me too confused if accelerometers r same then why we face bug of all custom roms ....if we patch wid leaks v3 kernel then no sensor bug......also is any similar jb 4.2.2 kernel like leaks v3

also,even i tried all kernel released from coolpad f1 till latest both 8297 and 8297w.....only leaks kernel has fix of accelerometer for mmx devices

Edited by m@nish123
Guest prshkr07
Posted

Ok m@nish123 :

I did a full backup using mtk droid tools and as it seems i now have an lk.bin file 393.216 bytes.

Here it is :https://www.sendspace.com/file/1t32ht

I hope this is the one you are looking for.

Edit: I also just checked my coolpad f1 accelerometer driver and it is LIS3DH. (Ok this seems to be the case in laek roms according to a previous post i missed).

u can check the name of ur accelerometer (not driver)with this app : https://play.google.com/store/apps/details?id=imoblife.androidsensorbox
Guest jay joshi
Posted

hi manish,

 

im a micromax a310 user, i downloaded many roms of coolpad f1 it works nicely but only 1 problem i faced thats auto rotation problem. do u have any fix for this??? plz send me link of it.

Guest m@nish123
Posted

Screenshot_2014-11-25-15-41-26_zpsrbqmct

A310 v2

check coopad f1.....we know in mmx this one is der

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.