Database Info

Sensorhub and Note 2 recovery maintainers

Please compile, if possible, your embedded recovery kernels without the sensorhub defconfig options.
CONFIG_SENSORS_SSP=y
CONFIG_SENSORS_SYSFS=y
CONFIG_SENSORS_SSP_ACCELEROMETER_POSITION=7
CONFIG_SENSORS_SSP_GYROSCOPE_POSITION=7
CONFIG_SENSORS_SSP_MAGNETOMETER_POSITION=7
CONFIG_SENSORS_SSP_LSM330=y
CONFIG_SENSORS_SSP_CM36651=y
CONFIG_SENSORS_SSP_AK8963C=y
CONFIG_SENSORS_SSP_BMP182=y
CONFIG_SENSORS_SSP_AT32UC3L0128=y
CONFIG_SENSORS_SSP_SENSORHUB=y
The kernel flashes over the sensorhub firmware on every single entry of recovery, and rebooting into the normal kernel, if the embedded kernel firmware mismatches the live hardware firmware. I consider this dangerous because firstly I don't know what happens if a firmware flash fails on boot, and secondly, the whole procedure is done over the I2C bus and takes about 22 seconds, increasing the boot time (and recovery entry) dramatically. The firmware changes relatively often and we have like 4 different versions out there in the wild at this moment and they will surely increase.
Off-topic: The sensorhub is a new dedicated micro-controller chip found on the Note 2 which handles all device sensors, instead of them being handled by the main CPU itself. The point of the thing is to offload that work from the CPU to vastly improve battery life.

Thank you a lot for the feedback and input about this issue
When compiling recoveries, we get the binary (recovery file) and the kernel. Sorry if I seem noob here, but I do not compile kernels, I am only used to cwm source. And in the recovery binary sources, there is no sensors flashed, it is the kernel that is repacked with it.
Now, if I take a recovery.img as it is outputted when compiled from cm10 sources, that is packed with a cm10 kernel, the recovery will boot without a delay.
However, that will break exfat support since we cannot insmod the external modules
So, the only choice is to repack the recovery ramdisk with a stock Samsung kernel, and that's what I do in my recoveries. However, this seems to induce the boot delay for people using custom kernels built around some sources (redpill, Perseus)
These recoveries repacked with a Samsung kernel will run fine along stock kernels and Note2core custom kernel (also a 4.1.2 source).
One of the potential causes is this part of code I believe (have no Note 2 to debug it)
drivers/sensor/ak8963.c
Code:
if (retry_count < 5) {
retry_count++;
pr_warn("############################################");
pr_warn("%s, retry_count=%d\n", __func__, retry_count);
pr_warn("############################################");
goto retry;
} else {
There is a check routine repeated 5 times, and on each repeat count a goto loop. The retry loop restarts much above in the code
retry:
Code:
#ifdef FACTORY_TESTstatic int ak8963c_selftest(struct akm8963_data *ak_data, int *sf){
.
.
.
retry:
/* read device info */
i2c_smbus_read_i2c_block_data(ak_data->this_client,
AK8963_REG_WIA, 2, buf);
pr_info("%s: device id = 0x%x, info = 0x%x\n",
__func__, buf[0], buf[1]);
/* set ATSC self test bit to 1 */
i2c_smbus_write_byte_data(ak_data->this_client,
AK8963_REG_ASTC, 0x40);
/* start self test */
i2c_smbus_write_byte_data(ak_data->this_client,
AK8963_REG_CNTL1,
AK8963_CNTL1_SELF_TEST);
/* wait for data ready */
while (1) {
msleep(20);
if (i2c_smbus_read_byte_data(ak_data->this_client,
AK8963_REG_ST1) == 1) {
break;
}
}
i2c_smbus_read_i2c_block_data(ak_data->this_client,
AK8963_REG_HXL, sizeof(buf), buf);
/* set ATSC self test bit to 0 */
i2c_smbus_write_byte_data(ak_data->this_client,
AK8963_REG_ASTC, 0x00);
x = buf[0] | (buf[1] << 8);
y = buf[2] | (buf[3] << 8);
z = buf[4] | (buf[5] << 8);
/* Hadj = (H*(Asa+128))/256 */
x = (x*(ak_data->asa[0] + 128)) >> 8;
y = (y*(ak_data->asa[1] + 128)) >> 8;
z = (z*(ak_data->asa[2] + 128)) >> 8;
pr_info("%s: self test x = %d, y = %d, z = %d\n",
__func__, x, y, z);
if ((x >= -200) && (x <= 200))
pr_info("%s: x passed self test, expect -200<=x<=200\n",
__func__);
else
pr_info("%s: x failed self test, expect -200<=x<=200\n",
__func__);
if ((y >= -200) && (y <= 200))
pr_info("%s: y passed self test, expect -200<=y<=200\n",
__func__);
else
pr_info("%s: y failed self test, expect -200<=y<=200\n",
__func__);
if ((z >= -3200) && (z <= -800))
pr_info("%s: z passed self test, expect -3200<=z<=-800\n",
__func__);
else
pr_info("%s: z failed self test, expect -3200<=z<=-800\n",
__func__);
sf[0] = x;
sf[1] = y;
sf[2] = z;
if (((x >= -200) && (x <= 200)) &&
((y >= -200) && (y <= 200)) &&
((z >= -3200) && (z <= -800))) {
pr_info("%s, Selftest is successful.\n", __func__);
return 1;
} else {
if (retry_count < 5) {
retry_count++;
pr_warn("############################################");
pr_warn("%s, retry_count=%d\n", __func__, retry_count);
pr_warn("############################################");
goto retry;
}
These are many retries using a non efficient goto loop.
Basically, here's the current possibilities I see:
- if we repack the recovery with your kernel or redpill, people will get delay issues on stock ROMs/Kernels
- if we use cm10 kernel: no delays but we loose exfat support
- if we use note2core kernel we'll probably loose exfat support
- if I recompile kernel from samsung sources without the sensors, it seems it will also break exfat
So, at the end I do not see a good choice that will satisfy every one. Either I wait for Samsung to release their sources so that you fix the kernel or I repack with 2 kernels: Samsung stock and redpill, so people can chose
Hope I am not getting it all wrong, but that's how I understand it

All that code is totally irrelevant and has nothing to do with the issue. I also don't understand what you want to say about that loop? Goto is inefficient? Nonsense.
The firmware flash and logic happens in /drivers/sensorhub/ssp_firmware.c and its just a few lines of code. The whole flash process is logged in kmsg at boot so you can just retrieve that and see for yourself.
And you're missing the point, as long as you embed ANY kernel with the sensorhub drivers, they will flash it. There are stock kernels out there with versions 91100, 92600, 92800, 102600 (just from the top of my head, might differ). If you use any recovery kernel whose version mismatches the boot.img kernel firmware, you will get the issue.
And to be honest, I don't understand what the fuss is about fixing it, TWRP includes now a kernel with exFat and removed sensor drivers. You just have to do the same.
Phil3759 said:
Either I wait for Samsung to release their sources so that you fix the kernel
Click to expand...
Click to collapse
There is nothing to fix from the live kernel side, I hope you understand that...

AndreiLux said:
All that code is totally irrelevant and has nothing to do with the issue. I also don't understand what you want to say about that loop? Goto is inefficient? Nonsense.
The firmware flash and logic happens in /drivers/sensorhub/ssp_firmware.c and its just a few lines of code. The whole flash process is logged in kmsg at boot so you can just retrieve that and see for yourself.
And you're missing the point, as long as you embed ANY kernel with the sensorhub drivers, they will flash it. There are stock kernels out there with versions 91100, 92600, 92800, 102600 (just from the top of my head, might differ). If you use any recovery kernel whose version mismatches the boot.img kernel firmware, you will get the issue.
And to be honest, I don't understand what the fuss is about fixing it, TWRP includes now a kernel with exFat and removed sensor drivers. You just have to do the same.
There is nothing to fix from the live kernel side, I hope you understand that...
Click to expand...
Click to collapse
AndreiLux said:
Sorry but you're a bit out of bound here with accusing kernel developers and doing such claims about the source of the issue while you seem pretty ignorant about the technical aspects of the problem.
As I said and explained in the thread you linked, the problem lies with the recovery and not the boot kernel. You're the one who will have to adapt your embedded kernel that you include here.
Click to expand...
Click to collapse
You also seem a bit ignorant about recoveries
TWRP doesn't included any custom kernel with exfat support. It comes with cm9 kernel and maybe now cm10.1 since they moved sources to 4.2 recently. Their source is just the android/bootable/recovery part built around cyanogenmod source. CM kernel, as I said in my answer, doesn't flash the sensors that's why there is no delay. That's the only reason why twrp won't have the delay. I can also include cm10 kernel and no more delays, but say good bye to exfat.
TWRP includes native exfat support where as CM and AOKP choose to not include it in their source (thus cwm) because it is not legal (MS patent). Only thing cwm devs can do:
- import twrp source for exfat support and break the MS patent
- use Samsung genuine kernel to get exfat support
So, not an easy decision / move as you suggest

Phil3759 said:
TWRP doesn't included any custom kernel with exfat support. It comes with cm9 kernel and maybe now cm10.1 since they moved sources to 4.2 recently. Their source is just the android/bootable/recovery part built around cyanogenmod source. CM kernel, as I said in my answer, doesn't flash the sensors that's why there is no delay. That's the only reason why twrp won't have the delay. I can also include cm10 kernel and no more delays, but say good bye to exfat.
TWRP includes native exfat support where as CM and AOKP choose to not include it in their source (thus cwm) because it is not legal (MS patent). Only thing cwm devs can do:
- import twrp source for exfat support and break the MS patent
- use Samsung genuine kernel to get exfat support
So, not an easy decision / move as you suggest
Click to expand...
Click to collapse
Sorry but almost everything you said its wrong.
TWRP includes a modified CM kernel with added exFat and since I've made Bigbiff aware, also removes the sensorhub drivers.
CM kernel, as I said in my answer, doesn't flash the sensors that's why there is no delay.
Click to expand...
Click to collapse
The CM kernel is based on the Samsung sources and has the flash logic intact, because it's obviously needed in the OS to even have functioning sensors. It's not flashing in your case because you have matching firmwares, and that's all.
Sorry but I suggest you inform yourself here a bit more, I've explained it pretty clearly yet you seem to be ranting about things which are just not correct.

delete

4.4.4-CM11 for huawei honor & Ideos X5 U8800 Pro & others KitKat flavours

Hi all. Time to open new Lollipop thread for honor.
http://forum.xda-developers.com/and...u8860-legacyhuawei-roms-t3032641#post58893010
[/COLOR]Huawei Honor u8860 Development​
HI all. after many of you asked me to open a thread about my cm11 builds for honor, i finally decided to do it...
so here is my latest build of cm11 and i will provide also some others kitkat flavour as beanstalk and mokee os and many others....
bugs, wifi tether not working but ok with third party app.
U8800pro users: read post 3
Mini How-to compile 4.4.2 for Huawei honor (u8860) : http://forum.xda-developers.com/showpost.php?p=52922053&postcount=897
see here for wifi tethering
http://forum.xda-developers.com/showpost.php?p=50156494&postcount=3710 (i attached tethering apk)
B919 stock rom base
http://www.mediafire.com/download/z136402ocabf4t6/b919.rar
TWRP-2.8.0.0: http://forum.xda-developers.com/showpost.php?p=55266722&postcount=1444
TeamWin recovery 2.7.1.0-u8860 update= fixed usb storage and file manager http://forum.xda-developers.com/showpost.php?p=54552750&postcount=1282
older : http://forum.xda-developers.com/showpost.php?p=53376000&postcount=1046
TeamWin recovery 2.7.1.0-u8800pro
http://forum.xda-developers.com/showpost.php?p=53378089&postcount=1047
TeamWin recovery 2.7.0.0
http://www.mediafire.com/download/hre1fd1czaq88gw/TWRP2.7-HUAWEIU8860-recovery.img
TeamWin recovery 2.6.0.0
http://www.mediafire.com/download/gi1ng2tp5rd0d8e/recovery-twrp-2.6.0.0-u8860.img
Changelog
http://forum.xda-developers.com/showpost.php?p=51510415&postcount=284
Downloads:
4.4.4
NEW!=Dirty_Unicorn: http://www.mediafire.com/download/kww6t63nbm1rnan/DU_u8860_4.4.4_20140901-1128.v7.9-UNOFFICIAL.zip
new=AOSB http://www.mediafire.com/download/x6m3aqx74nbpc71/aosb_kk_1.3.7_u8860.zip
NEW!=SOKP : http://www.mediafire.com/download/aklta4l3yb6qauk/SOKP-KK444-V-01-20140808-u8860.zip
PacMAn : http://www.mediafire.com/download/yspcsrir7aii7ec/pac_u8860_4.4.4.Beta-1.0_20140702-140013.zip
BeanStalk: http://www.mediafire.com/download/bby7bfpurifbx41/BeanStalk-4.4.4001-20140701-u8860.zip
http://www.mediafire.com/download/36zs4gx3pmc3o2o/BeanStalk-4.4.4001-20140621-u8860.zip
CyanogenMod: http://www.mediafire.com/download/9o8zl2cv8x9ephx/cm-11-testApps2SD-u8860-DAZ.zip --->Apps 2 Sd fixed
older: http://www.mediafire.com/download/1ukim9k4wx55vto/cm-11-444-20140621-UNOFFICIAL-u8860.zip
BlueLightning: http://www.mediafire.com/download/10wzaqvylq6zzx5/BlueLightning-444-20140620-u8860.zip
MokeeOs: http://www.mediafire.com/download/eihlpupd11hz949/MK44.4-u8860-201406201753-UNOFFICIAL.zip
NamelessRom: To come... ^^
Before 4.4.4:http://forum.xda-developers.com/showpost.php?p=53626292&postcount=1142
kernel source: https://github.com/desalesouche/Project-X5pro-Kernel-u8860-u8800pro
TeamWin recovery 2.6.0.0 http://www.mediafire.com/download/gi....0.0-u8860.img
Thread for gamers : http://forum.xda-developers.com/showthread.php?t=2615514
Credits:
- @CrysisLTU
- @Rittick
- @herna
- @gold-concert
- @h33x
- @j.Moihack
-Dazzozo
-ShenduOs
-Fredvj
and many others that i will add as soon as i remember.
thread about google now : http://forum.xda-developers.com/showthread.php?t=2649349
op in construction........
to mods, move that thread to devdb if needed...
in devdb thread my device is not represented .

HOW TO INSTALL
Make sure you're running a proper working ClockworkMod-Recovery/TWRP and that you are on B919 stock rom
Copy Gapps and CM11 ZIPs to your SDCard
Boot into Recovery
Wipe data/factory reset
Wipe Cache and Dalvik Cache
Format System
Flash CM11 zip from SDCard
Reboot
HOW TO COMPILE 4.4.2 ROM FOR HUAWEI HONOR------> http://forum.xda-developers.com/showpost.php?p=52922053&postcount=897

u8800pro users: how-to port rom from u8860 to u8800pro
U8800 pro more to come...
4.4.3 cm11 for u8800pro : http://www.mediafire.com/download/1one0utzb198uh2/cm-11-20140605-UNOFFICIAL-u8800pro.zip
mokee: http://www.mediafire.com/download/jcwcjacnonq32qq/MK44.2-u8800pro-201403150029-UNOFFICIAL.zip
cm11 m3 : http://www.mediafire.com/download/8ikou81fswnkli8/cm-11-m3-20140225-u8800pro-DynamiVSync2.zip
edit: i uploaded here for u8800pro user the bcm4329 wifi module in case some have problem with wifi...
see here how-to port rom from u8860 to u8800pro:
http://forum.xda-developers.com/showpost.php?p=53176802&postcount=961
NEW!our member @Lihis is porting all news rom for u8800pro follow the link...
don't forget to thank him
http://forum.xda-developers.com/showpost.php?p=53520636&postcount=1092

hello, des. thx for great work. i have some ideas, what need the rom:
1. sound for kernel is bad (bass not clear, angel's kernel have good sound)
2. poor sensitivity of the microphone, I was hard to hear. not only me, many users 4pda ask, how to up sensity of micro.
3. if u have time and desire, pls, build for us CarbonROM.
4. pls, need changlog in upper post
thx

for the tether app, what should i put in settings for it to work ?
Sent from my U8860 using Tapatalk

bublz654 said:
for the tether app, what should i put in settings for it to work ?
Sent from my U8860 using Tapatalk
Click to expand...
Click to collapse
link is on op

--

finr0d said:
does the cm11.0m3 include gapps? if not, could you link it in the OP?
Click to expand...
Click to collapse
cm does not support gapps. and here is the link gapps = http://www.mediafire.com/download/79s75mdbmb9bx0l/12-14_GApps_Standard_4.4.2_signed.zip
Sent from my U8860 using Tapatalk

bublz654 said:
cm does not support gapps. and here is the link gapps = http://www.mediafire.com/download/79s75mdbmb9bx0l/12-14_GApps_Standard_4.4.2_signed.zip
Sent from my U8860 using Tapatalk
Click to expand...
Click to collapse
Better to use gapps core for this device due low /system free space.
Here is an xda thread for all 4.4 gapps packages: http://forum.xda-developers.com/showthread.php?t=2012857
Here you will find gapps core and calendar/browser sync (not included in rom/gapps).
Sent from my U8860

that was gapps core, it says standard but all it includes is Google play
Sent from my U8860 using Tapatalk

Could you reupload the recovery image?

T3K0 said:
Could you reupload the recovery image?
Click to expand...
Click to collapse
cwm one?

Just have to paste the link to TWRP again.
I think something went wrong when you copied it. (It tries to open the link with the dots in it)

T3K0 said:
Just have to paste the link to TWRP again.
I think something went wrong when you copied it. (It tries to open the link with the dots in it)
Click to expand...
Click to collapse
Yep. That link on OP is corrupted. I think that was copied from here: http://forum.xda-developers.com/showpost.php?p=50136545&postcount=3703
@desalesouche , in OP should be mentioned that before flashing we need to be on b919 ROM.

I duplicate my message from main thread and in future continue posting here.
---------------START QUOTE--------------------
desalesouche said:
hello camera record doesn't work on 720P , but work on 480P . do you think that not enough ram might be cause for 720P video record? or is there other cause?...
Click to expand...
Click to collapse
Not sure, that I continue test and find this:
1) free memory size in settings apk and /proc/meminfo not equal. In settings i view, that I have 150MB free mem. In meminfo size is 64MB.
2) After record start I found in logs this errors:
Code:
E/OMXCodec( 125): [OMX.qcom.video.encoder.avc] Found supported color format: 21
E/OMX-VENC-720p( 125): get_parameter: OMX_IndexParamVideoProfileLevelQuerySupported for Input port returned Profile:1, Level:512
E/OMX-VENC-720p( 125):
E/OMX-VENC-720p( 125): venc_set_intra_period: nPFrames = 29 nBFrames = 0
I/str_params( 125): key: 'tunneled-input-formats' value: 'get'
D/AudioHardware7x30( 125): AudioHardware::openInputStream devices 8000000 format 1 channels 16 samplerate 48000
D/AudioSource( 125): Start autoramp from 108000
D/AudioHardware7x30( 125): AudioStreamInMSM72xx::standby()
D/AudioHardware7x30( 125): AudioStreamInMSM72xx::standby()
I/MPEG4Writer( 125): limits: 702779264/0 bytes/us, bit rate: 8156000 bps and the estimated moov size 405000 bytes
I/MPEG4Writer( 125): Start time offset: 1000000 us
E/OMX-VENC-720p( 125):
[COLOR="Red"][B]E/OMX-VENC-720p( 125): ERROR: MMAP_FAILED in o/p alloc buffer[/B][/COLOR]
E/OMXNodeInstance( 125): OMX_AllocateBuffer failed with error -2147479552 (0x80001000)
E/OMXCodec( 125): allocate_buffer_with_backup failed
E/OMXCodec( 125): [OMX.qcom.video.encoder.avc] Allocate Buffer failed - error = -2147483648
E/OMXCodec( 125): [OMX.qcom.video.encoder.avc] init failed: -2147483648
E/MediaRecorder( 3770): start failed: -2147483648
E/CAM_VideoModule( 3770): Could not start media recorder.
E/CAM_VideoModule( 3770): java.lang.RuntimeException: start failed.
E/CAM_VideoModule( 3770): at android.media.MediaRecorder.start(Native Method)
E/CAM_VideoModule( 3770): at com.android.camera.VideoModule.startVideoRecording(VideoModule.java:1194)
E/CAM_VideoModule( 3770): at com.android.camera.VideoModule.onShutterButtonClick(VideoModule.java:532)
E/CAM_VideoModule( 3770): at com.android.camera.ShutterButton.performClick(ShutterButton.java:126)
E/CAM_VideoModule( 3770): at android.view.View$PerformClick.run(View.java:18429)
E/CAM_VideoModule( 3770): at android.os.Handler.handleCallback(Handler.java:733)
E/CAM_VideoModule( 3770): at android.os.Handler.dispatchMessage(Handler.java:95)
E/CAM_VideoModule( 3770): at android.os.Looper.loop(Looper.java:136)
E/CAM_VideoModule( 3770): at android.app.ActivityThread.main(ActivityThread.java:5081)
E/CAM_VideoModule( 3770): at java.lang.reflect.Method.invokeNative(Native Method)
E/CAM_VideoModule( 3770): at java.lang.reflect.Method.invoke(Method.java:515)
E/CAM_VideoModule( 3770): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:781)
E/CAM_VideoModule( 3770): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:597)
E/CAM_VideoModule( 3770): at dalvik.system.NativeStart.main(Native Method)
V/CAM_VideoModule( 3770): Releasing media recorder.
this error really caused memory deficit.
I view current codecs and profiles, they identical with official firmware.
I try install and start old Huawei camera app and report about this.
------------------END QUOTE-----------------
I install stock camera application and have same error. symbol-to-symbol.
when I find information about qualcomm SoC hardware decoder I find this post.
Braccoz said:
hey guys, i would like to share some of my findings about the 1080p camera issue
prologue: scverhagen's 1080p hack works but only with the m4v encoder which puts out an h263 file (basically, divx quality). i also found out that the stock rom encodes both 720p and 1080p @h264 baseline lvl 4.0 while CM only encodes h264 baseline level 3.2
the findings: when you try to record 1080p h264 the camera app crashes and this is the logcat:
.....
some log code listing delete. h33x
.....
after some digging i found out that basically every phone (soc) has specific video hardware encoding capabilities and that there is a "standard" layer much like Direct3D/OpenGL for that, and is called OpenMAX (OMX).
it seems that omx implementation for every soc is, of course, closed source, but fortunately there is enough open source stuff to be able to use proprietary binary blobs (i may not be correct here, i am making educated guesses taking the info i found as a base)
so what i'm thinking currently is that the libOmxVenc.so that is provided with CM (seems like qualcomm donated/helped with the code) is intentionally limited to 720p max (and probably level 3.2 too, this would explain why the media_profiles.xml setting has no effect) and it just crashes when trying to encode anything >720p
so what i would like to try is take libOmxVenc.so from an ICS sensation stock rom and see if that is capable of encoding 1080p without modifications to the code (unlikely... 50% probability maybe but still worth a try)
Click to expand...
Click to collapse
Any ideas?
PS. I download official codec samples and documentation and try find answer inside.

jopsinas said:
Yep. That link on OP is corrupted. I think that was copied from here: http://forum.xda-developers.com/showpost.php?p=50136545&postcount=3703
@desalesouche , in OP should be mentioned that before flashing we need to be on b919 ROM.
Click to expand...
Click to collapse
I have updated to the official ICS and nothing else installed.
What are the steps to install this?
Do I have have to install b919 before I can install TWRP?
I dont have the phone here right now so I would like to download everything now so I dont have to when I install everything next week.

hmm i'm not sure what we're talking about here but since that post of mine was quoted i think you'd find the followup helpful.
the real issue was the camera outputting 31 fps while the encoder supported max 30. hacks have gone into the framework to trick the camera to tell it outputs 30 fps so the encoder was happy. you can browse through commits on my github to see what was done. but that is for doubleshot so it may not have anything to do with your huawei...

h33x said:
I duplicate my message from main thread and in future continue posting here
Any ideas?
PS. I download official codec samples and documentation and try find answer inside.
Click to expand...
Click to collapse
the only clue i have is that our media-codecs and media profiles are not good...

desalesouche said:
the only clue i have is that our media-codecs and media profiles are not good...
Click to expand...
Click to collapse
I think, that error reason in kernel code.
if grep "vidc_720p_mp4_enc_mc.fw" in official kernel code, found "./drivers/video/msm/vidc/720p/resource_tracker/vcd_res_tracker.c" file. this file and it top source files should be load proprietary blobs in memory and provides interfaces for using some functions.
I try find this in 3.4 kernel.

T3K0 said:
I have updated to the official ICS and nothing else installed.
What are the steps to install this?
Do I have have to install b919 before I can install TWRP?
I dont have the phone here right now so I would like to download everything now so I dont have to when I install everything next week.
Click to expand...
Click to collapse
first install b919 stock rom.
then go in pink screen and install cmw.
then you can flash the rom following second op post

Porting Android to Gear 2

Hello everyone!
Android Wear for Gear 2 / Gear 2 Neo​
This thread is about development of Android Wear for Gear 2 & Gear 2 Neo
IF YOU HAVE A QUESTION, ASK IT HERE: http://forum.xda-developers.com/gear-2/help/qa-porting-android-to-gear-2-t3018159​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
DISCLAIMER
Code:
Your warranty is now void. Not only void,
it's not comming back. The moment you
flash anything on this thread you can say
goodbye to it. I almost hard bricked my
watch once. It can happen to you too.
I do my best to post things that aren't
dangerous for the device, but anything
as simple as a 9 instead of a 4 in the GPU
driver might make it overheat and kill it.
Everything here is at your own risk.
You have been warned.
Current development stage
Kernel:: Still work in progress. Most functions are working correctly. Expect some bugs.
GITHUB REPO: Github Android B2 Repository
Recovery:: Minimal image. Not actively worked on, but enough to wipe and access ADB: MediaFire
Android: Most of it is working, and for me at least, IS usable. Some things are still missing and will need to be worked out though.
Working:
Boot
USB: ADB, MTP [july 19th]
Display: Software rendering, OpenGL and mixed compositions
Screen dimming
Screen always on
Battery reporting and charging
Oportunistic Sleep (kernel)
Bluetooth: basic functionality (working for notifications, music control etc), Tethered internet access (still some bugs to work out though)
Vibration
Heart Rate Monitor
Accelerometer sensor
Step counter
Gyroscope (this includes tilt to wake)
Power management: CPU Hotplugging, frequency scaling, Amoled LPM, runtime suspend and opportunistic sleep.
Depending on use, can give from 12 to 48 hours of battery life. Normal use gives me about 18-20 hours with screen always on
Audio: Input and Output
Infrared
Basic TWRP recovery functions
Not working:
Camera
There's no way of playing music to the speaker directly from the watch
There's no gallery app
Palm-on-screen to suspend
Anything that's not specifically put as "working"
Android Wear 6
Remember: These are BETA, things may or may not work. No support, no nothing, just sharing them with you so you can play with them. I already know what works and what doesn't, and I'm trying to fix everything
March 4, 2016: https://mega.nz/#!QQwXQKCD!U-y82wTuBflzdBTrLccxrSLoLkTJUGWtEXMZ6TPikQU
Fixes over previous builds: Text To Speech, IR Support & New Gear Kernel Settings
Previous builds:
Beta #3 (Zenwatch based): https://mega.nz/#!FFYjQCxR!Et4bc8QSXstO1oxlAdXNfq82f7QH4cKsj5tnBNLPZog
Beta #2 (Gear Live based): https://mega.nz/#!IExADLQC!HThMj1Sc_BcPsywQXM0LZopvZd3y1aXiaW-5a5_CHuM
Beta #1 (Gear Live based): https://mega.nz/#!tQJFxSLS!Xu4_xJkW7qlXgz4IUTbFa2RqN8kWcIf0-UZfRTJ0LyM
Android Wear 5.1.1
September 24th, 2015: Android Wear Lollipop - 5.1.1 (build LCA43)
Full flash Package:
Mediafire: http://www.mediafire.com/download/aces995ufltx3vb/Wear_511_LCA43__09_24_2015.zip
Includes: Kernel Settings application, IR App:
** PREROOTED, no need to install anything else
Translate app DOES NOT WORK!
Previous builds:
August 13th, 2015: Android Wear Lollipop - 5.1.1 (build LDZ22J)** Bugfix release,
Full flash Package:
Mediafire: http://www.mediafire.com/download/ar8ir73m32yx05n/Wear_511__08_13_2015.tar
Includes: Kernel Settings application:
* Control vibration intensity
* Control brightness in ambient mode
* Enable / Disable Partial Redraws (enable for best battery life)
* Enable / Disable Idle Mode (reduces color depth in ambient mode to enhance battery life)
July 22nd, 2015: Android Wear Lollipop - 5.1.1 (build LDZ22J)** Bugfix release
Full flash Package:
Mediafire: http://www.mediafire.com/download/pr3vljpdecep0dd/wear_511__07_22_2015.tar
md5: def249f18214c7ca00a5bc65391d0c0f wear_511__07_22_2015.tar
After flashing the big file, flash one of these, depending on what you need:
ADB only boot image: http://www.mediafire.com/download/cuo5fa95d5tgmv5/bootimage_ADB_ONLY.tar
ADB+MTP boot image: http://www.mediafire.com/download/bs6rwapqcc35sc6/bootimage_MTP_AND_ADB.tar
July 17th, 2015: Android Wear Lollipop - 5.1.1 (build LDZ22J)** Screen always on in Low Power Mode, MTP Support, @bitstra IR App Updated
Full flash Package:
Mega: https://mega.co.nz/#!0ZxgQYZA!7m986voG9NLYUUx7Nxzx8EiYbdgXxwFi56otuxQFZbM
Mediafire: http://www.mediafire.com/download/k71o1m16g32x65y/Wear__5_1_1__07_19_2015.zip
MD5: deffb5160968d81a4e560416315791eb Wear__5_1_1__07_19_2015.zip
July 13th, 2015: Android Wear Lollipop - 5.1.1 (build LDZ22J)** Infrared support (thanks @bitstra for your IR app!)
Full flash Package:http://www.mediafire.com/download/6mmb33lftfrr8w8/Wear_511__07_13_2015_Try2.zip
July 12th, 2015: Android Wear Lollipop - 5.1.1 (build LDZ22J) ** Screen always on + Audio IN/OUT modifications
Full flash Package: http://www.mediafire.com/download/myzqnv4bkwa55b3/Wear_5_1_1_07_12_2015.zip
July 5th, 2015: Android Wear Lollipop - 5.1.1 (build LDZ22J) ** Audio support!
Full flash Package: http://www.mediafire.com/download/eths38jax91sgnd/Wear_511_07_05_2015.zip
July 1st, 2015: Android Wear Lolipop - 5.1.1 (buildLDZ22J)
Full Flash Package: http://www.mediafire.com/download/6rzpfswta2s8fg3/Wear_511_07_01_2015.zip
June 27th, 2015: Android Wear Lolipop - 5.1.1 (build LDZ22J)
Full Flash Package: http://www.mediafire.com/download/bmcjbaikve5sob2/Gear2_Wear_Lolipop_5.1.1_06292015.tar.zip
June 27th, 2015: Android Wear Kitkat - 4.4.2W (build KNX01Q)
Full Flash Package: http://www.mediafire.com/download/2ar5ye1vla8g8gf/full_06_27_2015.zip
Everything I have/done with the Gear 2 is available on this folder: https://www.mediafire.com/folder/092gaz7gudh0f/Gear2, in case you want to dig a bit deeper
Installing
Odin: http://www.mediafire.com/download/v67itqpjitxxogi/Odin3_v3.09(1).zip
User @alvaromartinezb has made a really good video explaining what you have to do, check it out! https://www.youtube.com/watch?v=bBqg72z8LOk&feature=youtu.be
@alvaromartinezb Walkthrough video on audio: https://www.youtube.com/watch?v=klYqseFd90g
KNOWN ISSUES
USB doesn't work! --> Check if you're running latest build, check your drivers. Windows 7 may have some issues with MTP
ADB doesn't work! --> You might need to manually install the driver on the device manager in Windows (you can use Google SDK's bundled driver)
Battery doesn't last! --> Be careful with battery hog watchfaces, some will prevent the watch from entering suspend, or keep the heart rate sensor active at all times.
I can't play music from the watch to the speaker --> I haven't found an app that works. We're the only people with a speaker on an Android Wear device, and there aren't many 3rd party apps for that. Driver level is OK
I can't take photos! --> Work in progress, everything takes time, and my watch doesn't even have a camera!
Calls don't get routed through the watch and without it I will die! --> Then go back to Tizen. That functionality doesn't exist in Android Wear, and hundreds of hours of work for a function that probably wouldn't end up working anyway. And I hated it when I had it on Tizen, it only gave my phone issues when connecting to my car's bluetooth handsfree, and forcing me to choose back my phone on each and every call. I'm not developing that. If you want to try to code it yourself and you succeed, I can link to your work if you want, but I'm not wasting my time on that.
Going back to Tizen
BE ADVISED: GOING BACK TO TIZEN MIGHT PROVE DIFFICULT TO ANYBODY WITHOUT KNOWLEDGE OF THE WATCH, SDB, ADB, AND ANYONE WHO DOESN'T USE ODIN. DON'T PM ME FOR IT. IT'S WRITTEN BELOW. ASK IN THE Q&A SECTION PLEASE. THIS IS A DEVELOPMENT THREAD, AND THESE IMAGES ARE FOR DEVELOPMENT ONLY.
BE ADVISED (again): There's no PIT file for this watch. If your favourite flashing app for samsung phones requests one, use Odin. I know, I don't like it either. But we live in a world full of virtual machines with the ability to share USB ports. Now it's your chance to use them if you don't feel like installing Windows in your machine.
*. Walkthrough video by @alvaromartinezb : https://www.youtube.com/watch?v=LhzIqFopQNY&feature=youtu.be
1. Flash this file: http://www.mediafire.com/download/3cg2eazoouur0bs/Tizenmod-Full-Restore.tar
2. When it fails to boot and the screen goes blank, reboot to the bootloader menu and select recovery.
Extreme Recovery mode - Only use if above method doesn't work
YOU NEED TO KNOW HOW TO USE ADB/SDB FOR THIS.
It may happen that you try to recover your watch but for whatever reason it still enters a bootloop when attempting to boot Tizen. This might happen if you played with partitions, if some permissions were set where they shouldn't be, etc. If you enter recovery mode in Tizen and you don't see a confirmation that the watch is being restored to default, you can try this:
*NOTE* This is highly destructive. You do this wrong, your watch might not boot again. I'm not responsible for whatever damage you do to your watch.​
First of all download everything from this folder:
https://www.mediafire.com/folder/a1tcatuw1a8t3/Full_Restore
And then follow these steps:
Code:
1. Flash TizenModFull
It will start rebooting itself
2. Flash recovery_fota_cache
3. Enter recovery, and run the following commands through ADB:
adb shell ->
umount /data
mount /dev/block/mmcblk0p15 /system
mount /dev/block/mmcblk0p13 /system/opt
mount /dev/block/mmcblk0p14 /system/opt/usr
rm -rf /system/opt
cp /system/usr/system/RestoreDir/opt.zip /system
cd /system
unzip opt.zip
sync
cd /
umount /system/opt/usr
umount /system/opt
umount /system
Exit the shell and select "Reboot -> PowerOff" from TWRP
4. Now press and hold the power button until "Rebooting..." appears, then enter Download mode
5. Flash kernel_tizen.tar
6. Reboot again to download mode
7. Flash tizenmod2.tar
Some info about the device
Gear 2 specifications
Samsung Exynos 3250, dual core up to 1GHz
512 Mb of RAM
4 Gb of flash, divided in 15 partitions (see below)
Mali 400 GPU, using Exynos DRM driver
YMU381 audio, supported by ALSA
BCM4334W Bluetooth/WLAN controller, already supported by Android in a bunch of phones
Samsung SensorHub (STM32) controlling Gyro/accelerometer and HRM. Supported in the kernel and seen in Android HAL.
Partition layout
bota0 -> ../../mmcblk0p1
bota1 -> ../../mmcblk0p2
csa -> ../../mmcblk0p3 --> ext4 -> /csa
boot -> ../../mmcblk0p5 --> Main Kernel
csc -> ../../mmcblk0p12 --> ext4 -> /system/csc
fota -> ../../mmcblk0p10 --> seems empty
ramdisk-recovery -> mmcblk0p8 -> ext4 -> Unused in tizen --> USED AS BOOT PARTITION IN ANDROID
module -> ../../mmcblk0p9 --> ext4 -> /lib/modules --> USED FOR TWRP IN ANDROID
rootfs -> ../../mmcblk0p15 ext4 "/" --> Root file system, recovery works from here too. If you break it it will only boot to download mode. --> USED AS SYSTEM PARTITION IN ANDROID
system -> ../../mmcblk0p11 EMPTY --> Did samsung start with Android on this thing then changed their minds?
system-data -> ../../mmcblk0p13 --> ext4, /opt --> If you erase this partition, your watch won't boot back into Tizen. Do not touch it unless you have a backup and know your way into restoring it.
user -> ../../mmcblk0p14 EXT4, /opt/usr --> all user data, including the MTP available part (/opt/usr/media) --> USED AS DATA & SDCARD IN ANDROID

Hey,
I am no expert nor able to understand the details but I would like to thank you for this interesting work and I hope a skilled developper will help you through this. I am following this very closely!

Well done!

A little progress update...
I've built a base image for wear with all the required libraries I could find. It wonderfully crashes on the first boot stage:
Code:
- waiting for device -
--------- beginning of main
F/libc ( 94): Fatal signal 6 (SIGABRT) at 0x5e (code=-6), thread 94 (surfaceflinger)
F/libc ( 182): Fatal signal 6 (SIGABRT) at 0xb6 (code=-6), thread 182 (surfaceflinger)
F/libc ( 250): Fatal signal 6 (SIGABRT) at 0xfa (code=-6), thread 250 (surfaceflinger)
F/libc ( 322): Fatal signal 6 (SIGABRT) at 0x142 (code=-6), thread 322 (surfaceflinger)
F/libc ( 379): Fatal signal 6 (SIGABRT) at 0x17b (code=-6), thread 379 (surfaceflinger)
F/libc ( 435): Fatal signal 6 (SIGABRT) at 0x1b3 (code=-6), thread 435 (surfaceflinger)
F/libc ( 489): Fatal signal 6 (SIGABRT) at 0x1e9 (code=-6), thread 489 (surfaceflinger)
F/libc ( 544): Fatal signal 6 (SIGABRT) at 0x220 (code=-6), thread 544 (surfaceflinger)
F/libc ( 600): Fatal signal 6 (SIGABRT) at 0x258 (code=-6), thread 600 (surfaceflinger)
As far as I can guess, surfaceflinger can't start the hw composite device (the mali gpu) and crashes all the time. I think it's all related to the kernel but not too sure if I messed up somewhere else too (probably yes )
Right now I'm trying to clean up the kernel config to get rid of all the useless drivers and get ION working. Any kernel developers out there?
I will be leaving some stuff in Mediafire in case someone's willing to take a look:
https://www.mediafire.com/folder/wts6i0b4byxy0/Wear
Right now:
droid.tar.md5 --> minimal kernel to boot with android adb support
Kernel-Config-Android-ADB-minimal --> config file for the kernel (with mimal android support and part of the settings -no video-)
system.tar.md5 --> trashed up image of Android Wear with at least part of the exynos and mali libraries to help it boot. It crashes on boot but adb is available. Also fstab is messed up, but each thing at a time...
CAUTION: As it's always said, I'm in no way responsible for any damage done to your device if things go wrong. Do NOT touch the bootloader. And keep a ODIN package for restore when you want to go back. This will wipe your Tizen system partition.

Great work!
@biktor_gj i appreciate your development and your hard work! I really hope that you will succeed! My personal life is very stressing, and my laptop is down to help you in any way! I just wrote this to congrats your ambition and continuous work on this amazing smartwatch, that i just bought it for 1 week!

Awesome to see some development for our Gear 2! Congrats @biktor_gj and please keep it up! :good:
Looking forward to test something new, please count me in. :good:

I'm really eager to know how development is going on. :good:

Skin1980 may help. He is an awesome developer

Hey, right now stuck in here:
Code:
CHK include/linux/version.h
CHK include/generated/utsrelease.h
make[1]: 'include/generated/mach-types.h' is up to date.
CALL scripts/checksyscalls.sh
CHK include/generated/compile.h
CC drivers/gpu/ion/ion_chunk_heap.o
drivers/gpu/ion/ion_chunk_heap.c: In function ‘ion_chunk_heap_free’:
drivers/gpu/ion/ion_chunk_heap.c:108:4: error: implicit declaration of function ‘__dma_page_cpu_to_dev’ [-Werror=implicit-function-declaration]
cc1: all warnings being treated as errors
scripts/Makefile.build:307: recipe for target 'drivers/gpu/ion/ion_chunk_heap.o' failed
make[3]: *** [drivers/gpu/ion/ion_chunk_heap.o] Error 1
scripts/Makefile.build:443: recipe for target 'drivers/gpu/ion' failed
make[2]: *** [drivers/gpu/ion] Error 2
scripts/Makefile.build:443: recipe for target 'drivers/gpu' failed
make[1]: *** [drivers/gpu] Error 2
Makefile:948: recipe for target 'drivers' failed
make: *** [drivers] Error 2
I really don't know if kernel source is messed up in purpose, if it's simply an old tree and should be trying to port the board config to a newer release (exynos 3250 support is merged in newer releases I think) or why the h*** it can't find a function that is declared in dma-mapping but not found by the ion driver.
OR it maybe colliding with the exynos drm driver, which seems to not be the same as the one defined in CONFIG_EXYNOS_HW_DRM (which is used by the exynos 3470) and in which the tizen-display module (gear2/neo display driver) depends...
Brain hurts

Wow I would be so happy if I could start using my watch again. Could not handle being on a samsung based rom, and the workarounds have been unpleasant to use.
I hope you are making progress, as soon as this can do anything useful I will flash it to my watch. Wish I could help but I am not a skilled programmer.

Also since the Gear Live is similar though not identical, would using that as a base make it easier to port Android? Might be too dissimilar

biktor_gj said:
Hey, right now stuck in here:
Code:
CHK include/linux/version.h
CHK include/generated/utsrelease.h
make[1]: 'include/generated/mach-types.h' is up to date.
CALL scripts/checksyscalls.sh
CHK include/generated/compile.h
CC drivers/gpu/ion/ion_chunk_heap.o
drivers/gpu/ion/ion_chunk_heap.c: In function ‘ion_chunk_heap_free’:
drivers/gpu/ion/ion_chunk_heap.c:108:4: error: implicit declaration of function ‘__dma_page_cpu_to_dev’ [-Werror=implicit-function-declaration]
cc1: all warnings being treated as errors
scripts/Makefile.build:307: recipe for target 'drivers/gpu/ion/ion_chunk_heap.o' failed
make[3]: *** [drivers/gpu/ion/ion_chunk_heap.o] Error 1
scripts/Makefile.build:443: recipe for target 'drivers/gpu/ion' failed
make[2]: *** [drivers/gpu/ion] Error 2
scripts/Makefile.build:443: recipe for target 'drivers/gpu' failed
make[1]: *** [drivers/gpu] Error 2
Makefile:948: recipe for target 'drivers' failed
make: *** [drivers] Error 2
I really don't know if kernel source is messed up in purpose, if it's simply an old tree and should be trying to port the board config to a newer release (exynos 3250 support is merged in newer releases I think) or why the h*** it can't find a function that is declared in dma-mapping but not found by the ion driver.
OR it maybe colliding with the exynos drm driver, which seems to not be the same as the one defined in CONFIG_EXYNOS_HW_DRM (which is used by the exynos 3470) and in which the tizen-display module (gear2/neo display driver) depends...
Brain hurts
Click to expand...
Click to collapse
Maybe I got a hint..
Code:
drivers/gpu/ion/ion_chunk_heap.c:108:4: error: implicit declaration of function ‘__dma_page_cpu_to_dev’ [-Werror=implicit-function-declaration]
A friend of a friend of mine told me this:
"Well either the function is missing or its renamed.."
Made it any sense?

If you make this happen I will gladly pay you. I will finally be able to use this watch again. Its been sitting ever since I realized it was basically a dead platform (Tizen) and I moved away from Samsung phones.

So is it real to port Android wear with working heart rate? camera and IR doesn't matter for me. Want donate to dev if he can make it real

Its the if and camera will become use less what the point. Just buy an android wear watch.

diamantericos said:
Its the if and camera will become use less what the point. Just buy an android wear watch.
Click to expand...
Click to collapse
Hey, i live in Russia where smartwatch on Android Wear with heart meter will cost twice more (2x) than Gear 2

Kniazkoff said:
So is it real to port Android wear with working heart rate? camera and IR doesn't matter for me. Want donate to dev if he can make it real
Click to expand...
Click to collapse
+1 I'll donate too in case if it's became real.

Me too, will donate if successful so keep trying friend we all behind you.

diamantericos said:
Its the if and camera will become use less what the point. Just buy an android wear watch.
Click to expand...
Click to collapse
In my case I got my gear neo before android wear got physical products launched in my country, and theyre quite pricey for what they have... Anyway I guess its a matter of personal taste, I prefer a dual core than an old omap 3 cpu, and before the gear I had a Motoactv and the screen burnt. By itself. Big black spot in the middle... Just as the warranty period ended. So not buying from them anytime soon
Now back to the point, I temporarily had to stop this because it was driving me nuts, I was using an old mac mini as a development machine and it took me 5 hours to compile cyanogenmod. Just got new hardware so this week I hope Ill find some time to get back to testing!
Will keep you tuned if I can accomplish something more than getting a kernel crash
Sent from my Xperia Z using XDA Free mobile app

biktor_gj said:
In my case I got my gear neo before android wear got physical products launched in my country, and theyre quite pricey for what they have... Anyway I guess its a matter of personal taste, I prefer a dual core than an old omap 3 cpu, and before the gear I had a Motoactv and the screen burnt. By itself. Big black spot in the middle... Just as the warranty period ended. So not buying from them anytime soon
Now back to the point, I temporarily had to stop this because it was driving me nuts, I was using an old mac mini as a development machine and it took me 5 hours to compile cyanogenmod. Just got new hardware so this week I hope Ill find some time to get back to testing!
Will keep you tuned if I can accomplish something more than getting a kernel crash
Sent from my Xperia Z using XDA Free mobile app
Click to expand...
Click to collapse
Much appreciated thanks.

[WIP] Building custom ROM for Lenovo Tab2A7-10F

This thread is meant to share informations about trying to build a custom rom (CM, Omnirom...) for Lenovo Tab2 A7-10F
I'm currently trying to build CM12.1 using source
Any comment, hint, link, collaboration is welcome

Previously...
Previously...
[email protected] said:
Now time for new rom , i think you should try out building any cm based rom , omni is 75% Aosp so there might be some issues.
Sent from my A311 using XDA-Developers mobile app
Click to expand...
Click to collapse
pix106 said:
How can AOSP be an issue ? I always choose opensource when possible.
Click to expand...
Click to collapse
[email protected] said:
For mediatek open sources are not totally compatible with aosp's . every mtk chipset has same issue. So you can try out other others.
Sent from my A311 using XDA-Developers mobile app
Click to expand...
Click to collapse
pix106 said:
Ok, i may try some other rom though.
Thanks for your advice.
Do you have any info/link to mediatek sources ?
Click to expand...
Click to collapse
MaRtYy01 said:
Yep,agreed.With the years cyanogenmod went on its own and its not really based on aosp right now,while omni is more aosp based rom.
Click to expand...
Click to collapse
[email protected] said:
You can try out official sources with stock kernel , i have only links for mt6582 and mt6592 sources for now.
Sent from my A311 using XDA-Developers mobile app
---------- Post added at 03:31 AM ---------- Previous post was at 02:52 AM ----------
Can you link me any device/vendor tree . I'll try to compile cm12.1.
Sent from my A311 using XDA-Developers mobile app
Click to expand...
Click to collapse
pix106 said:
A few month ago, with a friend we did this for omnirom, we got boot (prebuilt kernel), graphics, but no wifi etc... : https://github.com/PixNDom/android_device_lenovo_Tab2A710F https://github.com/PixNDom/android_vendor_lenovo_Tab2A710F (other repos https://github.com/PixNDom).
We stopped as we did not know how to go on.
Yesterday after your advice i started a cm12.1 branch on my github (https://github.com/pix106/android_device_lenovo_Tab2A710F/blob/cm12.1), and got TWRP running using cm12.1 sources (with wrong device id, but it does not matter now).
I tried building the kernel again using lenovo sources (https://github.com/pix106/android_kernel_lenovo_Tab2A710F/tree/lenovo_osc_201511), with cm12, i got the same result than i got with omnirom : no graphics, "GTP Reset", i2C errors...
Thanks for your help
Click to expand...
Click to collapse

pix106 said:
Previously...
Click to expand...
Click to collapse
Try compiling with stock kernel ,
Sent from my A311 using XDA-Developers mobile app

That's what i do, i use prebuilt stock kernel.
But i would like to use kernel sources to build kernel with rom

If cm12 has the same problems as omni its most likely a kernel issue.Or there is something wrong with the sources.

I have worked on building CM12.1 today, and updated the first post
System is booting, adb and logcat work.
I added a few mali and hw related blobs, and a script to extract blobs from a file system dump instead of using adb to extract them from a running stock rom.
Any comment, hint, link, collaboration is welcome

pix106 said:
I have worked on building CM12.1 today, and updated the first post
System is booting, adb and logcat work.
I added a few mali and hw related blobs, and a script to extract blobs from a file system dump instead of using adb to extract them from a running stock rom.
Any comment, hint, link, collaboration is welcome
Click to expand...
Click to collapse
Cm12.1 booted succesfully. Then what are issues.
Sent from my A311 using XDA-Developers mobile app

[email protected] said:
Cm12.1 booted succesfully. Then what are issues.
Click to expand...
Click to collapse
Yesterday only adb and logcat were working.
Today, with a few MTK related flags, and a fresh build while i was at work, bootanimation starts
I'm going to add the missing files i detect from logcat and see what happens next...

After adding libxlog to PRODUCT_PACKAGES and providing a source for it, to avoid : cannot locate symbol "__xlog_buf_printf" referenced by "libdpframework.so", I got bootanimation.
I then added a few missing files as blobs.
Here are some errors i get :
Code:
E/audit_rules( 135): Could not read audit rules /data/misc/audit/audit.rules: No such file or directory
I/Vold ( 131): Vold 2.1 (the revenge) firing up
D/Vold ( 131): Volume sdcard0 state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 131): Volume sdcard1 state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 131): Volume usbotg state changing -1 (Initializing) -> 0 (No-Media)
I/Cryptfs ( 131): Check if PFE is activated on Boot
E/Cryptfs ( 131): Bad magic for real block device /[email protected]
E/Cryptfs ( 131): Error getting crypt footer and key
W/DirectVolume( 131): Deprecated implied prefix pattern detected, please use '/devices/platform/mtk-msdc.0/mmc_host*' instead
I/[MALI][Gralloc]( 132): dlopen libtz_uree.so fail
E/HAL ( 132): dlopen failed: library "libtz_uree.so" not found
I/[MALI][Gralloc]( 207): dlopen libtz_uree.so fail
E/Netd ( 520): Failed to open /proc/sys/net/ipv6/conf/default/use_optimistic: No such file or directory
E/Netd ( 520): Failed to open /proc/sys/net/ipv6/conf/ifb0/use_optimistic: No such file or directory
E/Netd ( 520): Failed to open /proc/sys/net/ipv6/conf/ifb1/use_optimistic: No such file or directory
E/Netd ( 520): Failed to open /proc/sys/net/ipv6/conf/ip6tnl0/use_optimistic: No such file or directory
E/Netd ( 520): Failed to open /proc/sys/net/ipv6/conf/lo/use_optimistic: No such file or directory
E/Netd ( 520): Failed to open /proc/sys/net/ipv6/conf/sit0/use_optimistic: No such file or directory
E/android.os.Debug( 522): failed to load memtrack module: -2
E/MediaPlayerFactory(15733): calling dlopen on FACTORY_LIB
E/MediaPlayerFactory(15733): Failed to open FACTORY_LIB Error : dlopen failed: library "libdashplayer.so" not found
E/CameraService(15733): setUpVendorTags: Vendor tag operations not fully defined. Ignoring definitions.
E/HAL (15733): load: module=/system/lib/hw/audio.primary.mt8127.so
E/HAL (15733): dlopen failed: cannot locate symbol "_ZN7android11AudioSystem24getVoiceUnlockDLInstanceEv" referenced by "audio.primary.mt8127.so"...
E/AudioFlinger(15733): int android::load_audio_interface(const char*, audio_hw_device_t**) couldn't load audio hw module audio.primary (Invalid argument)
E/MonoPipe(15733): Failed to fetch local time frequency when constructing a MonoPipe (res = -32). getNextWriteTimestamp calls will be non-functional
E/AudioPolicyManager(15733): Default device 00000002 is unreachable
E/AudioPolicyManager(15733): Failed to open primary output
If add libtz_uree.so, hwcomposer (blob) fails, bootanimation does not start anymore.
I also tried adding libdashplayer to PRODUCT_PACKAGES, but it didn't help. And i have no source.
During a previous omnirom 5.1 build with a friend (https://github.com/PixNDom/android_device_lenovo_Tab2A710F), we used https://github.com/aomp/android_mediatek_frameworks
It allowed to build some libs, but it's rather old, i think.
Does anyone have a recent repository for mediatek sources, so hwcomposer (and other files that are blobs for now) could be built ?

pix106 said:
After adding libxlog to PRODUCT_PACKAGES and providing a source for it, to avoid : cannot locate symbol "__xlog_buf_printf" referenced by "libdpframework.so", I got bootanimation.
I then added a few missing files as blobs.
Here are some errors i get :
Code:
E/audit_rules( 135): Could not read audit rules /data/misc/audit/audit.rules: No such file or directory
I/Vold ( 131): Vold 2.1 (the revenge) firing up
D/Vold ( 131): Volume sdcard0 state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 131): Volume sdcard1 state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 131): Volume usbotg state changing -1 (Initializing) -> 0 (No-Media)
I/Cryptfs ( 131): Check if PFE is activated on Boot
E/Cryptfs ( 131): Bad magic for real block device /[email protected]
E/Cryptfs ( 131): Error getting crypt footer and key
W/DirectVolume( 131): Deprecated implied prefix pattern detected, please use '/devices/platform/mtk-msdc.0/mmc_host*' instead
I/[MALI][Gralloc]( 132): dlopen libtz_uree.so fail
E/HAL ( 132): dlopen failed: library "libtz_uree.so" not found
I/[MALI][Gralloc]( 207): dlopen libtz_uree.so fail
E/Netd ( 520): Failed to open /proc/sys/net/ipv6/conf/default/use_optimistic: No such file or directory
E/Netd ( 520): Failed to open /proc/sys/net/ipv6/conf/ifb0/use_optimistic: No such file or directory
E/Netd ( 520): Failed to open /proc/sys/net/ipv6/conf/ifb1/use_optimistic: No such file or directory
E/Netd ( 520): Failed to open /proc/sys/net/ipv6/conf/ip6tnl0/use_optimistic: No such file or directory
E/Netd ( 520): Failed to open /proc/sys/net/ipv6/conf/lo/use_optimistic: No such file or directory
E/Netd ( 520): Failed to open /proc/sys/net/ipv6/conf/sit0/use_optimistic: No such file or directory
E/android.os.Debug( 522): failed to load memtrack module: -2
E/MediaPlayerFactory(15733): calling dlopen on FACTORY_LIB
E/MediaPlayerFactory(15733): Failed to open FACTORY_LIB Error : dlopen failed: library "libdashplayer.so" not found
E/CameraService(15733): setUpVendorTags: Vendor tag operations not fully defined. Ignoring definitions.
E/HAL (15733): load: module=/system/lib/hw/audio.primary.mt8127.so
E/HAL (15733): dlopen failed: cannot locate symbol "_ZN7android11AudioSystem24getVoiceUnlockDLInstanceEv" referenced by "audio.primary.mt8127.so"...
E/AudioFlinger(15733): int android::load_audio_interface(const char*, audio_hw_device_t**) couldn't load audio hw module audio.primary (Invalid argument)
E/MonoPipe(15733): Failed to fetch local time frequency when constructing a MonoPipe (res = -32). getNextWriteTimestamp calls will be non-functional
E/AudioPolicyManager(15733): Default device 00000002 is unreachable
E/AudioPolicyManager(15733): Failed to open primary output
If add libtz_uree.so, hwcomposer (blob) fails, bootanimation does not start anymore.
I also tried adding libdashplayer to PRODUCT_PACKAGES, but it didn't help. And i have no source.
During a previous omnirom 5.1 build with a friend (https://github.com/PixNDom/android_device_lenovo_Tab2A710F), we used https://github.com/aomp/android_mediatek_frameworks
It allowed to build some libs, but it's rather old, i think.
Does anyone have a recent repository for mediatek sources, so hwcomposer (and other files that are blobs for now) could be built ?
Click to expand...
Click to collapse
Can't you use something from the fire 2015 device tree?Its fully complete,the cm12.1 for it is bugless.Not sure if building roms works like that,but if you are missing drivers or something since it has the same chipset and kernel the stuff from it might work,I guess.
https://bitbucket.org/amazonfire2015/cm_device_amazon_ford
BTW as far as I know mediatek has no official source like qualcomm,thats why building roms for it is an issue.

MaRtYy01 said:
Can't you use something from the fire 2015 device tree?Its fully complete,the cm12.1 for it is bugless.Not sure if building roms works like that,but if you are missing drivers or something since it has the same chipset and kernel the stuff from it might work,I guess.
https://bitbucket.org/amazonfire2015/cm_device_amazon_ford
BTW as far as I know mediatek has no official source like qualcomm,thats why building roms for it is an issue.
Click to expand...
Click to collapse
Thanks, i'll have a look at this.
Either try to build it changing hardware related stuff, or pick a few things from it... or both.
I had already looked on fire 2015 source on github in 2015, it has changed since then too.
At the moment, i'm trying to build with some other mt8127 github repo (https://github.com/neporood/android_device_viking_mt8127), changing hardware stuff.
Thanks

pix106 said:
During a previous omnirom 5.1 build with a friend (https://github.com/PixNDom/android_device_lenovo_Tab2A710F), we used https://github.com/aomp/android_mediatek_frameworks
It allowed to build some libs, but it's rather old, i think.
Click to expand...
Click to collapse
sorry, i actualy wanted to mention https://github.com/aomp/android_mediatek_hardware

pix106 said:
sorry, i actualy wanted to mention https://github.com/aomp/android_mediatek_hardware
Click to expand...
Click to collapse
I'm now trying to build using this hardware/mediatek repo, it should provide libs that are blobs for now.
After adding a few .h files, it builds fine, but i don't get all the libs that should be built from this repo, although i added them to PRODUCT_PACKAGES.
I'll push these changes to github.
Even with a linux and python dev experience, i'm quite new to building roms, i may have missed a few things.

I made some ROMs for my Nexus4 and even there, you needed some closed source libs from LG which was not so easy to obtain.. On a damn nexus device..
Some people mentioned that an Amazon Fire tablet is mostly the same tablet..
The CPU looks the same for the Fire HD 7" (4th gen - 2014) and the GPU is the same from FireHD 8.9" (2.5th Gen) and Fire HD 7 (3rd Gen).
Does CM and/or other Custom ROMs work with Amazon-Fire tablets?

thE_29 said:
I made some ROMs for my Nexus4 and even there, you needed some closed source libs from LG which was not so easy to obtain.. On a damn nexus device..
Some people mentioned that an Amazon Fire tablet is mostly the same tablet..
The CPU looks the same for the Fire HD 7" (4th gen - 2014) and the GPU is the same from FireHD 8.9" (2.5th Gen) and Fire HD 7 (3rd Gen).
Does CM and/or other Custom ROMs work with Amazon-Fire tablets?
Click to expand...
Click to collapse
apparently it does, so there's hope.
I tried building using a mt8127 device tree and vendor from github, with my device tree and his vendor.
I have also made a "noblob" build (before using the hardware/mediatek repo) so that blobs can be pushed.

pix106 said:
apparently it does, so there's hope.
I tried building using a mt8127 device tree and vendor from github, with my device tree and his vendor.
I have also made a "noblob" build (before using the hardware/mediatek repo) so that blobs can be pushed.
Click to expand...
Click to collapse
Can you provide cm12.1 meta inf folder and boot.img?I feel like the one from the amazon fire is superpatched because of fire os crap and cant be ported and Im trying to make a flashable version of your modified stock rom but I dont have meta inf folder(tried one from cm12.0 from one mt6582 device,it did boot but it got stuck at the first boot loading screen).

MaRtYy01 said:
Can you provide cm12.1 meta inf folder and boot.img?I feel like the one from the amazon fire is superpatched because of fire os crap and cant be ported and Im trying to make a flashable version of your modified stock rom but I dont have meta inf folder(tried one from cm12.0 from one mt6582 device,it did boot but it got stuck at the first boot loading screen).
Click to expand...
Click to collapse
I tried too a few months ago, neither did it boot.
The "noblobs" build i did a few days ago : https://mega.nz/#F!i5h23AKY!jnsxiU8Ob0WiDt1YnSabLg
I'm quite sure a few needed init scripts are missing from this build, and from the device tree in general.
Happy testing .

pix106 said:
I tried too a few months ago, neither did it boot.
The "noblobs" build i did a few days ago : https://mega.nz/#F!i5h23AKY!jnsxiU8Ob0WiDt1YnSabLg
I'm quite sure a few needed init scripts are missing from this build, and from the device tree in general.
Happy testing .
Click to expand...
Click to collapse
is this build boots or not . (just asking) by the way :good::good:

[email protected] said:
is this build boots or not . (just asking) by the way :good::good:
Click to expand...
Click to collapse
Its stuck on the bootlogo,since it has no blobs.
BTW the results of my "testing"
-changing the boot.img didnt help,the frecking amazon fire cm12.1 refuses to boot no matter what I do
-the updater script seemed useless,since the system folder in the roms built from source is in just one file
Anyway,got another idea.If I do a backup of system via twrp I probably can use the updater script with it.

[email protected] said:
is this build boots or not . (just asking) by the way :good::good:
Click to expand...
Click to collapse
MaRtYy01 said:
Its stuck on the bootlogo,since it has no blobs.
Click to expand...
Click to collapse
Exactly. It boots, adb and logcat work, but nothing more.
Missing files can be looking for errors in logcat, and be pushed "live" from stock rom dump.
MaRtYy01 said:
BTW the results of my "testing"
-changing the boot.img didnt help,the frecking amazon fire cm12.1 refuses to boot no matter what I do
Click to expand...
Click to collapse
no adb nor logcat ?
MaRtYy01 said:
-the updater script seemed useless,since the system folder in the roms built from source is in just one file
Click to expand...
Click to collapse
is /system mounted ?
MaRtYy01 said:
Anyway,got another idea.If I do a backup of system via twrp I probably can use the updater script with it.
Click to expand...
Click to collapse
i did not understand what you are planning to do... anyway good luck with it

[ROM][7.1.2][i9305]Unofficial LineageOS 14.1 by Exynos4 Team

[ROM][7.1.2][i9305]Unofficial LineageOS 14.1 by Exynos4 Team
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
What is Exynos4 Team?
The Exynos4 team is composed of the current maintainers for T0LTE/T0LTEKOR for both LineageOS and Resurrection Remix.
(@Option58, @kozmo21 and @PoisonNinja)
Difference between this and official Lineage 14.1
This is more like a bleeding edge build. Upcoming changes/fixes will show up here first, and eventually make it into Lineage official. So, if you want the latest and greatest changes for the Note 2 and than ported to the i9305, if possible, flash this instead of official.
Due to LineageOS rules, if you are switching between official and unofficial builds you will have to clean flash.
Exynos4 Team like to say thanks to:
The great developer community out there. We've had a lot of help from other people.
- the LineageOS team
- the Galaxy S3 LineageOS maintainer github.com/fourkbomb.
- the NamelessROM project github.com/namelessrom.
- xda users for testing and bug reports.
And I want to say thanks to:
PoisonNinja and Option58, who helped me a lot to set up the device tree and vendor blobs for that Exynos4 rom,
which is mainly created or grown out of the hwc idea.
and credits to @p.a.n for his work and providing his changes and patches.
Working
Graphics
Wifi
Data
RIL
Bluetooth (?!?)
Sensors
Vibration
Camera
NFC
Audio
Video Playback
Not working/Bugs/Unknown
[*]GPS is not working currently Fix is in second post!!
Bluetooth audio (may or may not work for you), please check and report back
MTP crashes when uninstalling an app
Installation
Read the FAQ to familiarize yourself with any issues that may come up
Make sure you're using the latest TWRP version
Download and copy latest rom version to the phone, preferably on internal storage
Factory reset in TWRP (Very important! Do not skip)
Format system, cache, dalvik, data
Flash unofficial LineageOS 14.1
Flash Gapps
Optional: Flash root package
Reboot
Be patient. The first boot will take between 5 - 15 minutes.
See the FAQ to avoid common issues
For updates, it's OK to dirty flash. If you experience any issues however, it is recommended that you clean flash.
Download
lineage-14.1-20170618-UNOFFICIAL-i9305-HWC.zip: June 18, 2017
6/18/2017 (i9305)
Sync with the latest Lineage sources
Hardware composer fixes
[*] Switch back to proprietary RIL 4.4 blobs
Properly fixed screencast
Lots of security patches in the kernel
Temporarily switched SELinux to permissive
XDA:DevDB Information
LineageOS 14.1 by Exynos4 Team, ROM for the Samsung SIII LTE (i9305)
Contributors
PoisonNinja, Option58, kozmo21, LineageOS team
Source Code: https://github.com/Exynos4
ROM OS Version: 7.x Nougat
Based On: LineageOS
Version Information
Status: Beta
Created 2017-06-18
Last Updated 2017-06-18

Just a few info
Root
LineageOS removed builtin root, so you need to flash the root package linked above.
Please test especially calls, incoming and outgoing, mobile data and bluetooth.
The rom/build is based on pans vendor proprietary (ril) blobs and should improve our ril and hopefully fix our reboot problem.
Kernel is set to permissive at the moment. Stickt version also ok.
Please also test bluetooth (audio transfer), because I am not sure, whether it works correct.
GPS is currently not working. Will try to fix that with one of the next builds.
Edit: previous GPS fix is working and solve the problem. Changes will be added in next update.
You can also find it here attached fixed in version: 0702
Other than the HWC and blob changes, the rom is based on pure lineageos sources/repos.

if I need another one

I'm getting bootloops with that build (it doesn't reach far enough for adb to pull the logs). I tried building a build with older blobs yesterday. My build was getting SIGSEGV caused by ks. I'll try building a non hwc version using your blobs and i9305 repository.

I also noticed some reboots, but none anymore during the last night. So I assume that the reboots could not be solved with changing the blobs and also not with that different ril sources/blobs. I doubt that the reboots will be gone with a non hwc version, but we will see. Beside of that are the other things working? Calls, mobile data etc?

Non hwc version booted ok. at_distributor is having problems :
Code:
06-19 03:06:25.941 2812 2812 F libc : CANNOT LINK EXECUTABLE "/system/bin/at_distributor": cannot locate symbol "supportExpandedNV" referenced by "/system/bin/at_distributor"...
06-19 03:06:25.941 2812 2812 F libc : Fatal signal 6 (SIGABRT), code -6 in tid 2812 (at_distributor)
but RIL works anyway (at least SMS). I'll try replacing it with stock i9305 at_distributor. I've got one reboot but I didn't launch logcat/kmsg before and had only short last_kmsg. We should try replacing the blobs with the stock i9305 ones because for now they are mixed. We could give a shot to persist.radio.apm_sim_not_pwdn=1 in system.prop too. I haven't tested anything beside RIL reboots (I'm testing it during night and hoping it will manage to reboot before next day because for daily usage I'm going back to the last stable rom).

Many thanks and when you managed to solve the mix up and your tests are ok, it would be good, if you can upload your changes to github. Think it doesn't make sense that we do all the work twice
Edit: seems to be again or still:
Code:
Kernel panic - not syncing: Fatal exception
and I think caused because of:
Code:
<6>[ 184.685341] c0 mdm_hsic_pm_notify_event: unblock request
<6>[ 184.685375] c0 notify_modem_fatal or shutdown
<6>[ 184.685403] c0 ap2mdm_status is high
<6>[ 184.685425] c0 ap2mdm_errfatal is high
<6>[ 184.685449] c0 mdm2ap_status is low
<6>[ 184.685471] c0 mdm2ap_errfatal is low
<6>[ 184.685492] c0 During shutdown, return notify_modem_fatal

rodman01 said:
Many thanks and when you managed to solve the mix up and your tests are ok, it would be good, if you can upload your changes to github. Think it doesn't make sense that we do all the work twice
Edit: seems to be again or still:
Code:
Kernel panic - not syncing: Fatal exception
and I think caused because of:
Code:
<6>[ 184.685341] c0 mdm_hsic_pm_notify_event: unblock request
<6>[ 184.685375] c0 notify_modem_fatal or shutdown
<6>[ 184.685403] c0 ap2mdm_status is high
<6>[ 184.685425] c0 ap2mdm_errfatal is high
<6>[ 184.685449] c0 mdm2ap_status is low
<6>[ 184.685471] c0 mdm2ap_errfatal is low
<6>[ 184.685492] c0 During shutdown, return notify_modem_fatal
Click to expand...
Click to collapse
Don't worry, I'll upload when I have something that's worth uploading. If you got
Code:
<6>[ 184.685425] c0 ap2mdm_errfatal is high
then the issue is still there.
Update
at_distributor from stock references the same function (supportExpandedNV) so the problem rather doesn't lie in the at_distributor itself but in a missing file that contains the missing function.
Update 2
Replacing ks blob with i9305 stock one alone won't work. That leads to the problem that @p.a.n had (https://forum.xda-developers.com/showpost.php?p=64395738&postcount=218) (https://forum.xda-developers.com/showpost.php?p=64448961&postcount=269)

mtr_ said:
Update 2
Replacing ks blob with i9305 stock one alone won't work. That leads to the problem that @p.a.n had (https://forum.xda-developers.com/showpost.php?p=64395738&postcount=218) (https://forum.xda-developers.com/showpost.php?p=64448961&postcount=269)
Click to expand...
Click to collapse
There is a simple solution (or hack to be more precise) to this and I believe I`ve also described it somewhere here - open the ks binary with some binary editor, find the connect string (it should be there twice) and replace it something else with the same length (I used xonnect).
This is a linker related problem, ks contains symbol connect, which replaces connect from libc (I hope it is there, if not it is some other system library), but with a totally different functionality, which causes a crash. Don`t ask me why this is happening in one environment and in other (the old one), I don`t know.

Maybe this last_kmsg looks better now?
Code:
Samsung S-Boot 4.0 for GT-I9305 (Sep 12 2014 - 13:40:58)
EXYNOS4412(EVT 1.1) / 2044MB / 0MB / Rev 2 / I9305XXUFNI3 /(PKG_ID 0xb070018)
BOOTLOADER VERSION : I9305XXUFNI3
PMIC rev = PASS2(4)
BUCK1OUT(vdd_mif) = 0x05
BUCK3DVS1(vdd_int) = 0x20
cardtype: 0x00000007
SB_MMC_HS_52MHZ_1_8V_3V_IO
mmc->card_caps: 0x00000311
mmc->host_caps: 0x00000311
[mmc] capacity = 30777344
MODEL_NAME:{{GT-I9305}}
eMMC_SERIAL_NUMBER:{{1501004D4147344642F74A00ABD19F03}}
- read_bl1
pit_check_signature (PIT) valid.
initialize_ddi_data: usable! (4:0xe)
[RPMB] emmc_rpmb_open:
Get DATA success.
[RPMB] emmc_rpmb_close:
initialize_rpmb_data: usable! (GT-I9305:VERSION_-+A3)
PARAM ENV VERSION: v1.0..
set_charger_current: chg curr(3f), in curr(17)
set_charger_state: buck(1), chg(1), reg(0x05)
microusb_get_attached_device: STATUS1:0x3f, 2:0x00
set_auto_current: ta_state(0), curr(700)
init_fuelgauge: fuelgauge power ok
init_fuelgauge: POR status
fuelgauge_por: POR start: vcell(3975), vfocv(4026), soc(79)
fuelgauge_por: update SDI M0 parameter
fuelgauge_por: RCOMP(0x0063), TEMPCO(0x0930)
fuelgauge_por: POR finish: vcell(3977), vfocv(4085), soc(73)
get_table_soc: vcell(3976) is caculated to t-soc(75.735)
init_fuelgauge: start: vcell(3976), vfocv(4081), soc(73), table soc(75)
init_fuelgauge: finish: vcell(3976), vfocv(4081), soc(73), table soc(75)
init_microusb_ic: before MUIC: CDETCTRL:0x2d
init_microusb_ic: after MUIC: CDETCTRL:0x2d
init_microusb_ic: MUIC: CONTROL1:0x00
init_microusb_ic: MUIC: CONTROL1:0x00
init_microusb_ic: MUIC: CONTROL2:0x3b
init_microusb_ic: MUIC: CONTROL2:0x3b
PMIC_ID = 0x02
PMIC_IRQSRC = 0x00
PMIC_IRQ1 = 0x02
PMIC_IRQ2 = 0x00
PMIC_IRQ1M = 0xff
PMIC_IRQ2M = 0xff
PMIC_STATUS1 = 0x13
PMIC_STATUS2 = 0x00
PMIC_PWRON = 0x01
PMIC_RTCINT = 0x11
PMIC_RTCINTM = 0x3f
s5p_check_keypad: 0x100000
s5p_check_reboot_mode: INFORM3 = 0 ... skip
s5p_check_upload: MAGIC(0xc1d0c0d6), RST_STAT(0x10000)
microusb_get_attached_device: STATUS1:0x3f, 2:0x00
s5p_check_download: 0
microusb_get_attached_device: STATUS1:0x3f, 2:0x00
check_pm_status: charger is not detected
check_pm_status: voltage(3978) is ok
cmu_div:1, div:7, src_clk:800000000, pixel_clk:38102400
s5p_dsim_display_config: VIDEO MODE
a2, 60, 90,
<start_checksum:481>CHECKSUM_HEADER_SECTOR :4096
<start_checksum:483>offset:50, size:6296
<start_checksum:485>CHECKSUM_HEADER_INFO : NeedChecksum:0 PartNo:20
Not Need Movinand Checksum
Movinand Checksum Confirmation Pass
[mobi_drv] add: 0x43e52500, size: 3933
MobiCore INIT response = 0
MobiCore RTM has initialized!
MobiCore IDLE flag = 0
MobiCore driver address 43e52500, size = 3933
MobiCore RTM Notified back!
MobiCore Driver loaded and RTM IDLE!
MobiCore RTM has been uninitialized!
load_kernel: loading boot image from 106496..
Verify_Binary_Signature: failed.
pit_check_signature (BOOT) invalid.
Set invalid sign flag
No need to update kernel type.
SMC Num = 0x83000001
mobismc success!!! [ret = 0]
[s5p_check_sboot_version_rpmb]cur_version:VERSION_-+A3, rpmb_version:VERSION_-+A3
rpmb_version:51, cur_version:51
ATAG_CORE: 5 54410001 0 0 0
ATAG_MEM: 4 54410002 20000000 40000000
ATAG_MEM: 4 54410002 20000000 60000000
ATAG_MEM: 4 54410002 20000000 80000000
ATAG_MEM: 4 54410002 1FC00000 A0000000
ATAG_SERIAL: 4 54410006 42f74a00 abd19f03
ATAG_INITRD2: 4 54420005 42000000 17b548
ATAG_REVISION: 3 54410007 2
check_rustproof [0]
ATAG_CMDLINE: b1 54410009 'console=ram loglevel=4 androidboot.baseband=mdm sec_debug.level=0 sec_watchdog.sec_pet=5 androidboot.debug_level=0x4f4c [email protected] [email protected] [email protected] s3cfb.bootloaderfb=0x5ec00000 lcdtype=96 consoleblank=0 lpj=3981312 vmalloc=176m oops=panic pmic_info=67 cordon=471c411f44a4d1cb9c99510ec7e578a1 connie=GT-I9305_OPEN_EUR_10e569b8255514f00b8793d908e78a26 androidboot.emmc_checksum=3 androidboot.boot_salescode= androidboot.odin_download=1 androidboot.bootloader=I9305XXUFNI3 androidboot.selinux=enforcing androidboot.warranty_bit=1 androidboot.sec_atd.tty=/dev/ttySAC2 androidboot.serialno=42f74a00abd19f03 snd_soc_core.pmdown_time=1000'
ATAG_NONE: 0 0
Starting kernel at 0x40008000...
SWITCH_SEL(3)

p.a.n said:
There is a simple solution (or hack to be more precise) to this and I believe I`ve also described it somewhere here - open the ks binary with some binary editor, find the connect string (it should be there twice) and replace it something else with the same length (I used xonnect).
This is a linker related problem, ks contains symbol connect, which replaces connect from libc (I hope it is there, if not it is some other system library), but with a totally different functionality, which causes a crash. Don`t ask me why this is happening in one environment and in other (the old one), I don`t know.
Click to expand...
Click to collapse
Thanks for hint, I know that you don't work on i9305 anymore. Isn't that connect that comes internally in ks used somewhere ? After all they had to have a reason to place an internal function like that. After you left the development, it seems that the current ks that is being used in LineageOS based roms seems to be taken from other device. The current situation is as follows: the modem crashes from time to time, ks during that crash is having issues during SAHARA protocol file transfer. I don't know whether it is the modem that causes the ks crash, or ks that causes modem crash.
rodman01 said:
Maybe this last_kmsg looks better now?
Click to expand...
Click to collapse
The pasted log contains only what happened after reboot. It shows the next boot. If you wanted to show a crash, it isn't saved. It could be truncated, because last_kmsg has limited buffer (for most of the modem issues it was just too small to show everything). You can use the methods to capture logs I posted somewhere else.

yes I noticed this too after pulling another one.
But with my current used blobs I do not have that:
Code:
<6>[ 184.685425] c0 ap2mdm_errfatal is high
anymore, but still reboots and:
Code:
<6>[ 1581.571051] c0 mdm_subsys_powerup: mdm modem restart timed out.
<0>[ 1581.571210] c0 Kernel panic - not syncing: subsystem_restart_wq_func[eac9d720]: Failed to powerup external_modem!

rodman01 said:
yes I noticed this too after pulling another one.
But with my current used blobs I do not have that:
Code:
<6>[ 184.685425] c0 ap2mdm_errfatal is high
anymore, but still reboots and:
Code:
<6>[ 1581.571051] c0 mdm_subsys_powerup: mdm modem restart timed out.
<0>[ 1581.571210] c0 Kernel panic - not syncing: subsystem_restart_wq_func[eac9d720]: Failed to powerup external_modem!
Click to expand...
Click to collapse
Still not good. Have you tried modyfing the stock ks as @p.a.n wrote ? I think that the blobs can be swapped on already installed Android, without recompiling everything. Doing adb push should work too. Something like: adb root, adb remount, adb push, reboot.

I know that this is not good.
No I haven't, I have no such editor and haven't searched for it. Have you tried that already?

rodman01 said:
I know that this is not good.
No I haven't, I have no such editor and haven't searched for it. Have you tried that already?
Click to expand...
Click to collapse
Any hex editor should be enough (for Windows you could try https://mh-nexus.de/en/hxd/ ). I haven't tried yet, I returned to stock rom.

mtr_ said:
Thanks for hint, I know that you don't work on i9305 anymore. Isn't that connect that comes internally in ks used somewhere ? After all they had to have a reason to place an internal function like that. After you left the development, it seems that the current ks that is being used in LineageOS based roms seems to be taken from other device. The current situation is as follows: the modem crashes from time to time, ks during that crash is having issues during SAHARA protocol file transfer. I don't know whether it is the modem that causes the ks crash, or ks that causes modem crash.
Click to expand...
Click to collapse
I actually do work on it, just don`t publish, since I was under impression that the official version is fine and the problem you are describing here is caused by old version of modem. I didn`t want to change it, so I solved the problem by using the KitKat RIL with the modification I mentioned.
As far as I know the connect symbol in the ks binary is used only internaly (and shouldn`t be exported at all). It seems like a simple name colision, which was handled differently in KitKat. I`ve been using the modified ks for a long time and it doesn`t seem to have any negative side effect.
I`ll try to put together all the changes against the official code I have and publish again some of my builds. LineageOS 14.1 is quite stable on my device, so I hope this will help you. I just cannnot promise, when this will be, since I am pretty bussy now (more I`ve ever been).

I am uploading at the moment a new test build, where in my logcat no at distributor error and no SIGABRT error or message is to be seen at the moment. Maybe someone is around who is willing to test it....?!?

New test build is uploaded now.
Its based on todays leos sources and nameless/crazyweasel 3.0 vendor/blobs.
Download
lineage-14.1-20170621-UNOFFICIAL-i9305-hwc.zip: https://www.androidfilehost.com/?fid=673368273298966239
Please report back about reboots and or any other error or bug.
GPS is fixed and should work now.

p.a.n said:
I actually do work on it, just don`t publish, since I was under impression that the official version is fine and the problem you are describing here is caused by old version of modem. I didn`t want to change it, so I solved the problem by using the KitKat RIL with the modification I mentioned.
Click to expand...
Click to collapse
Lucky. It seems that by doing that you avoided the RIL problems (and thus saved time ). The thing worth mentioning is that there are quite new stock releases available (I9305XXSFQ series).
rodman01 said:
New test build is uploaded now.
Its based on todays leos sources and nameless/crazyweasel 3.0 vendor/blobs.
Please report back about bootloops and or any other error or bug.
GPS is fixed and should work now.
Click to expand...
Click to collapse
Tested, unfortunately bootloops. Did you try it after a dirty flash or a clean one ?
I made a non hwc build with https://github.com/CrazyWeasel/proprietary_vendor_samsung/tree/n-3.0/i9305 and modified ks from https://github.com/p-an/android_device_samsung_i9305/blob/cm-14.1/proprietary/system/bin/ks . ks works, at_distributor doesn't whine about missing symbol, but that it can't connect to ATD.
Code:
06-22 04:24:28.916 5290 5290 V AT_Distributor_diag: can't connect to atd socket
06-22 04:24:29.046 5293 5293 V AT_Distributor_diag: ConnectToATD
I was running the build for an hour, so not long enough to tell whether the modem issue appears. 4:50 AM, time to get back to stock

I had a reboot during the night too. And now, since the last half an hour, several reboots again. So I would say, this test version is almost unusable at the moment. Did a clean flash after changing to crazyweasel blobs.