Related
it seems that is working, tried it on 4.4.2, but no OAD support..
to enable it add the following line to android/system/device/motorola/omap4-common/common.mk
frameworks/native/data/etc/android.hardware.bluetooth_le.xml:system/etc/permissions/android.hardware.bluetooth_le.xml
next to
frameworks/native/data/etc/android.hardware.usb.host.xml:system/etc/permissions/android.hardware.usb.host.xml \
and (device specific) system/device/motorola/maserati/bluetooth/bdroid_buildcfg.h
#define BTA_DM_COD {0x1A, 0x01, 0x14}
#define BTIF_HF_SERVICES (BTA_HSP_SERVICE_MASK)
#define BTIF_HF_SERVICE_NAMES { BTIF_HSAG_SERVICE_NAME }
#define PAN_NAP_DISABLED TRUE
#define BLE_INCLUDED TRUE
#define BTA_GATT_INCLUDED TRUE
#define SMP_INCLUDED TRUE
after
#define BTM_DEF_LOCAL_NAME "Motorola Droid 4"
tried with new bluetooth firmware from https://github.com/TI-ECS/bt-firmware, is working but is not stable.
the default firmware is working well with the sensor tags
lucize said:
it seems that is working, tried it on 4.4.2, but no OAD support..
Click to expand...
Click to collapse
Great
I've just pushed your changes to my repositories, so they will be included in tomorrows nightly.
Merry Christmas,
Michael
Merry Christmas to everyone !
All devices that have the TIInit_10.6.15.bts firmware should work so maybe this would be of help for someone else, maybe you can talk with Hashcode or David to enable it on every device. 4.3 should work too !
Regards
lucize said:
All devices that have the TIInit_10.6.15.bts firmware should work so maybe this would be of help for someone else, maybe you can talk with Hashcode or David to enable it on every device. 4.3 should work too !
Click to expand...
Click to collapse
Ok, short gerrit crash-course
Configure your local git to commit with the name and email-address you want to be visible in public repositories
Create an account on http://review.cyanogenmod.org/
Upload an ssh public key there
Clone the repository you want to change with something like:
Code:
git clone ssh://[email protected]:29418/CyanogenMod/android_device_motorola_omap4-common
(This is not necessary if you are working on a direct CM clone and have no other changes in your repository)
Make your changes, commit them
Push your changes to gerrit:
Code:
git push ssh://[email protected]:29418/CyanogenMod/android_device_motorola_omap4-common HEAD:refs/for/cm-11.0
This will tell you an URL where your change is visible.
Go to that URL and add reviewers to your change. For example: Hashcode, David Hacker and probably me (Michael Gernoth)
If your change is acceptable, it will get merged into the CM repository
That's all, no great magic
For more info, have a look at: http://review.cyanogenmod.org/Documentation/user-upload.html
Best regards & thanks for your work,
Michael
lucize said:
Merry Christmas to everyone !
All devices that have the TIInit_10.6.15.bts firmware should work so maybe this would be of help for someone else, maybe you can talk with Hashcode or David to enable it on every device. 4.3 should work too !
Regards
Click to expand...
Click to collapse
Is that firmware part of CM11 or something that I'd have to install manually onto my Droid 4? If so, how does one upgrade the Bluetooth firmware?
bofis said:
Is that firmware part of CM11 or something that I'd have to install manually onto my Droid 4? If so, how does one upgrade the Bluetooth firmware?
Click to expand...
Click to collapse
is part of cm11, you can find it in /etc/firmware/
you can find it here
https://github.com/TI-ECS/bt-firmware/commits/master this is the history page where you can find various versions, but the last version from December won't load and the rest will not work with the headset (no sound)
htc one x has the same bluetooth chip and has a newer version of firmware, but the sound on headset will not work either, everything else seems to work
you can see the version at the beginning of the file, motorola has TI_P6_15.56
to update, turn bluetooth off, simply overwrite the file and the turn it on again.
I noticed that this eventually made it to CM11 for all of Moto OMAP cousins, except for the Bionic (Targa). Any reason that the Targa was left out? A lack of hardware support, or was it just never tested?
guyincog said:
I noticed that this eventually made it to CM11 for all of Moto OMAP cousins, except for the Bionic (Targa). Any reason that the Targa was left out? A lack of hardware support, or was it just never tested?
Click to expand...
Click to collapse
I don't know if it has the proper chip but the firmware is correct so it should be possible. I don't have one to test.
Regards
lucize said:
I don't know if it has the proper chip but the firmware is correct so it should be possible. I don't have one to test.
Regards
Click to expand...
Click to collapse
Thanks for the reply. I've got one, maybe I'll see if I can talk one of the builders for the Bionic will make a test build with the necessary common.mk change.
I apprciate the work on this, and the kernel update you've got in progress. Any extra features we can add to these old devices is a huge bonus.
This might be the wrong place to ask this, but does CM11 or CM11 on our phone support the APTX codec via Bluetooth?
bofis said:
This might be the wrong place to ask this, but does CM11 or CM11 on our phone support the APTX codec via Bluetooth?
Click to expand...
Click to collapse
it has the hardware support
http://www.aptx.com/product/motorola-razr-maxx-smartphone
but don't know about the rest of the things
This module should fix WiFi 802.11ac or 5GHz frequencies not working (or working at half speed) on some custom rom.
This happens due to the wrong Wifi Country Code, which this module changes according to the system language.
N.B: if you've set your phone in a language different than yours (or if you've set your phone in your language, in a different country), probably this module is not going to help.
Without this fix maximum speed was 200 Mbps, after applying the changes 433 Mbps.
The file is stored in two different locations:
-/system/etc/wifi on Nougat
-/system/vendor/firmware on Oreo-Pie
that's why there are 2 versions of this module.
Tested on Sony Xperia Z3 Compact running CarbonRom 6.1 (OREO) and CarbonRom 7.0 (PIE).
Download it from the attachments, install in Magisk Manager and reboot.
P.S.: on the first boot, WiFi speed could be unstable for a while. Just let it settle
Hi, I need your help. I have a galaxy s7 and I need to change the wifi_country_code on the US I tried with the help of this -https://forum.xda-developers.com/nexus-6/help/wifi-channels-149-165-5ghz-t3099653 but it does not work.
How change this? - # bcmdhd.cal modifications
oldCC=$(cat /system/vendor/firmware/bcmdhd.cal | grep ccode | cut -f2 -d '=')
newCC=$(getprop | grep locale | cut -f2 -d ' ' | cut -f2 -d '-' | tr '[' ' ' | tr ']' ' ' | cut -f2 -d '-' | sed -n '1p')
I do not have such a file in oreo (ambasaddi rom)
I also have the same problem with wifi_country_code , for my samsung j5 prime model g570M In the version Nougat. Well, you can not see the wifi signal. To see the signal I have to activate airplane mode.
Working good.
works really great! thanks!!
Can you please support android 9?
marcogiannetta said:
This module should fix WiFi 802.11ac or 5GHz frequencies not working (or working at half speed) on some custom rom.
This happens due to the wrong Wifi Country Code, which this module changes according to the system language.
N.B: if you've set your phone in a language different than yours (or if you've set your phone in your language, in a different country), probably this module is not going to help.
Without this fix maximum speed was 200 Mbps, after applying the changes 433 Mbps.
The file is stored in two different locations:
-/system/etc/wifi on Nougat
-/system/vendor/firmware on Oreo
that's why there are 2 versions of this module.
Tested on Sony Xperia Z3 Compact running CarbonRom 6.1.
Download it from the attachments, install in Magisk Manager and reboot.
P.S.: on the first boot, WiFi speed could be unstable for a while. Just let it settle
Click to expand...
Click to collapse
Hi there, can you add support for pie, please?
saedkebbeh said:
Can you please support android 9?
Click to expand...
Click to collapse
Stogie87 said:
Hi there, can you add support for pie, please?
Click to expand...
Click to collapse
Done :good:
marcogiannetta said:
Done :good:
Click to expand...
Click to collapse
Thankus a lotus.
But there should be an option for deleting your comment which isn't present there
As I don't have a broadcom wifi in my phone, I haven't tested it. However I have found out thet there exists a property for wifi country code (I have checked android wifi service sources)
I have put this line in build.prop and toggled flight mode
Code:
ro.boot.wificountrycode=SK
Now I can conect to channel 13 AP
I suppose this only works without SIM/cellular connection, since android sets appropriate wifi county code from the cellular network. I use this specific phone in fligt mode only, so automatic setting didn't work.
im using [9] LineageOS 16.0 for z3. WI-FI does not work.
i installed this mode, But it doesn't work perfectly. It only works on AIREPLAN MODE.
mer5ad said:
im using [9] LineageOS 16.0 for z3. WI-FI does not work.
i installed this mode, But it doesn't work perfectly. It only works on AIREPLAN MODE.
Click to expand...
Click to collapse
Salam Dadash
My attached mode completly works on lineage 16. Ichecked it. it does not necessary to airplane mode.
after instalatiation of linage ROM 16, by ADB and fastboot you can flash it.
fastboot flash boot wifi5GbootLOS16.img
https://drive.google.com/file/d/1XWkcrpTkSz5udGA70pSm607E0mCmbHlD/view?usp=sharing
any chance for android 10 update ?
or anyone know the new location for bcmdhd.cal on Android 10 ?
Where's the download link?
Cara doenloadnya gimana
Hi,
question to all: I'd like to use Snoop Snitch, but it requires the Qualcomm Diganostic Kernel drivers (CHAR_DIAG) enabled. I haven't found a custom Pie ROM /Kernel yet that supports it.
Dies anyone here habe a hint for me for a LOS based ROM or a Kernel for LOS based ROMS on the 3T that support it? Tried it with Franco Kernel under NLOS but no success...
Thanks and cheers
Zap
Zaphod_B_1 said:
Hi,
question to all: I'd like to use Snoop Snitch, but it requires the Qualcomm Diganostic Kernel drivers (CHAR_DIAG) enabled. I haven't found a custom Pie ROM /Kernel yet that supports it.
Dies anyone here habe a hint for me for a LOS based ROM or a Kernel for LOS based ROMS on the 3T that support it? Tried it with Franco Kernel under NLOS but no success...
Thanks and cheers
Zap
Click to expand...
Click to collapse
I've just checked with nlos: build with "CONFIG_DIAG_CHAR=y", checked on the device and set the device to permissive mode
Code:
[email protected] /usr/local/src/los16/frameworks/base $ adb shell su -c "zcat /proc/config.gz"|grep CONFIG_DIAG_CHAR
CONFIG_DIAG_CHAR=y
[email protected] /usr/local/src/los16/frameworks/base $ adb shell su -c "getenforce"
Permissive
[email protected] /usr/local/src/los16/frameworks/base $
After that I've still got the "could not initialize DIAG interface" message.
Conclusion: enabling CONFIG_DIAG_CHAR doesn't make a difference on nlos.
No good news, but thank you for the quick try! Would have been great to see it working on NLOS.
It looks like there is no further ROM or kernel that supports it on the 3T, even OOS based Pie ROMs do not work... Checked it yesterday. It seems that Oneplus removed the driver somewhere after 7.1.1...
Cheers
Zap
I was looking for the same
Zaphod_B_1 said:
It looks like there is no further ROM or kernel that supports it on the 3T.
Click to expand...
Click to collapse
https://forum.xda-developers.com/on...evelopment/glassrom-8-1-t3876869/post80420021
Just found:
On NLOS (and I belive on los, too) CONFIG_DIAG_CHAR is auto selected:
Code:
[email protected] /usr/local/src/los16/kernel/oneplus/msm8996 $ grep -r DIAG_CHAR arch/arm64/configs/lineageos_oneplus3_defconfig
[email protected] /usr/local/src/los16/kernel/oneplus/msm8996 $ grep -r DIAG_CHAR ../../../out/target/product/oneplus3/obj/KERNEL_OBJ/.config
CONFIG_DIAG_CHAR=y
[email protected] /usr/local/src/los16/kernel/oneplus/msm8996 $
If Snoop Snitch can't initialize the diag interface, it's NOT! due to the abscence of CONFIG_DIAG_CHAR, but it must be something else. What does the Snoop Snitch support says, that Snoop Snitch is bailing out, though the diag interface is compiled in?
Zaphod_B_1 said:
question to all: I'd like to use Snoop Snitch, but it requires the Qualcomm Diganostic Kernel drivers (CHAR_DIAG) enabled. I haven't found a custom Pie ROM /Kernel yet that supports it.
Dies anyone here habe a hint for me for a LOS based ROM or a Kernel for LOS based ROMS on the 3T that support it? Tried it with Franco Kernel under NLOS but no success...
Click to expand...
Click to collapse
It's verified that LineageOS-16.0 and NLOS-16.0 have CONFIG_DIAG_CHAR enabled.
For LOS-16.0:
https://forum.xda-developers.com/showpost.php?p=80437877&postcount=3317
FOR NLOS-16.0:
Code:
[email protected] /usr/local/src/oxygenos $ adb shell su -c "cat /sys/module/diagchar/version"
1.0
[email protected] /usr/local/src/oxygenos $
Considering the faq on 64-bit socs https://opensource.srlabs.de/projects/snoopsnitch/wiki/FAQ#Are-64bit-Qualcomm-chipsets-supported or the term "CyanogenMod", either the documentation or the package is not really made for our msm8996...
Without exact and current documentation on what is really needed in order to run snoopsnitch, no kernel/rom dev can fix this. The error message and the included link to the documentation and the faq arn't helpful, in case of CONFIG_DIAG_CHAR even misleading.
nvertigo67 said:
Without exact and current documentation on what is really needed in order to run snoopsnitch, no kernel/rom dev can fix this. The error message and the included link to the documentation and the faq arn't helpful, in case of CONFIG_DIAG_CHAR even misleading.
Click to expand...
Click to collapse
Does this help? @Zaphod_B_1 @lhe87
https://forum.xda-developers.com/on...h-oneplus-compatibility-t4154491/post83373695
Yes, it helped. Snoop Snitch is again running on my 3T (I'm currently using Havoc 3.8 ROM) and I'm happy it does.
There are two things to mention:
- the patch level checks do not work, that maybe depends in the ROM I'm using - I'll have to check this.
- I cannot say if the detection of silent SMS and IMSI Catchers really is working since I've havent't had such events till now. Silent SMSes should appear from time to time IMO while IMSI catcher events are extremely rare. I used Snoop Snitch for one year two or three years ago and got two of those events in this year: one in Germany, one in Canada.
Does its existence for devices like the Z3C make it more or less likely for us to see on suzuran? Would love to see a LineageOS 17 ROM for this device. Makes me wish I was a dev. Thanks to all those who continue to grind hours into porting and developing ROMs for the platform.
beflythis said:
Would love to see a LineageOS 17 ROM for this device.
Click to expand...
Click to collapse
Oh! I have successfully built a LineageOS 17.0 rom for z5c! :good:
But.... As my 16.0 try this rom is not booting...
Don't know why
Berni-0815 said:
Oh! I have successfully built a LineageOS 17.0 rom for z5c! :good:
But.... As my 16.0 try this rom is not booting...
Don't know why
Click to expand...
Click to collapse
Are you making any kernel changes? If not, that's probably why. You can't use the LineageOS 15.1 kernel on the PIE. Correct me if I'm wrong but Pie requires linux kernel 4.4x and greater while, Android 10 requires 4.9 and greater.
Apart from fixing compile-errors, no.
But I don't think that the kernel version is important. This project uses kernel 3.x too, if I'm not wrong...
Sure, there have to be changes, but I can't do so...
I've tried another kernel (this one) and I changed/added some files to avoid compile errors. But the result is the same:
The splash screen apears, then a blank screen....
The splash screen apears, then a blank screen....
The splash screen apears, then a blank screen....
The splash screen apears, then a blank screen....
...and so on until end of battery...
Have you tried looking at any sort of logs, kernel logs? (I'm not sure if there would be one in the first place) It would be better to try by increments (PIE first with https://github.com/joel16/android_kernel_sony_msm8994). I might give it a try this weekend just for the sake of it.
Joel16 said:
Have you tried looking at any sort of logs, kernel logs? (I'm not sure if there would be one in the first place)
Click to expand...
Click to collapse
Where should these logs be?
I have no access to the device at this early stage...
An when I reflash a working rom /system will be overwritten.
It would be better to try by increments (PIE first with https://github.com/joel16/android_kernel_sony_msm8994). I might give it a try this weekend just for the sake of it.
Click to expand...
Click to collapse
I've tried to build pie with this kernel. Nearly the same result.
Berni-0815 said:
Where should these logs be?
I have no access to the device at this early stage...
An when I reflash a working rom /system will be overwritten.
I've tried to build pie with this kernel. Nearly the same result.
Click to expand...
Click to collapse
Weird, I ran into some issues building pie yesterday, but didn't have any time to fix it. I'll try again tonight and see how it goes. If I still have issues, I'll have to wait till the weekend.
Joel16 said:
Weird, I ran into some issues building pie yesterday
Click to expand...
Click to collapse
I'm sorry; I should have tell you about that... :angel:
I changed a lot of things to compile it successfully. Here are my changes (I hope this list is complete):
.bashrc:
Code:
export CPU_SSE42=false
to avoid crashes in hiddenapi and profman
device/sony/kitakami-common/SonyOtgSwitch/Android.mk:
Code:
LOCAL_SDK_VERSION := current
kernel/sony/msm8994/include/uapi/linux/rmnet_data.h; insert lines 226 to 236 (line 226 changed [a comma at the end of line]):
Code:
RMNET_NETLINK_DEL_VND_TC_FLOW,
/*
* RMNET_NETLINK_NEW_VND_WITH_NAME - Creates a new virtual network
* device node with the specified
* device name
* Args: int32_t node number
* char[] vnd_name - Use as name
* Returns: status code
*/
RMNET_NETLINK_NEW_VND_WITH_NAME
bionic/libc/include/bits/fortify/fcntl.h; insert lines 33 to 36:
Code:
#ifndef __O_TMPFILE
#define __O_TMPFILE 020000000
#endif
#define O_TMPFILE (__O_TMPFILE | O_DIRECTORY)
hardware/qcom/audio-caf/msm8994/hal/audio_hw.c; line 2457:
Code:
ALOGE("%s: error [B]%ld[/B] - %s", __func__, ret, pcm_get_error(out->pcm));
hardware/qcom/audio-caf/msm8994/hal/audio_extn/audio_extn.c; lines 523 and 524:
Code:
void audio_extn_set_parameters(struct audio_device *adev [B]__unused[/B],
struct str_parms *parms [B]__unused[/B])
and line 67:
Code:
static struct audio_extn_module aextnmod [B]__unused[/B] = {
hardware/qcom/display-caf/msm8994/libqdutils/idle_invalidator.cpp; line 127:
Code:
ALOGD_IF(II_DEBUG, "IdleInvalidator::%s Idle Timeout fired len [B]%ld[/B]",
hardware/qcom/display-caf/msm8994/libhdmi/hdmi.cpp: line 196:
Code:
ALOGD("%s: Scan Info string: %s length = [B]%ld[/B]",
and line 320:
Code:
ALOGD_IF(DEBUG, "%s: EDID string: %s length = [B]%ld[/B]",
device/sony/kitakami-common/SonyOtgSwitch/Android.mk: line 5:
Code:
LOCAL_PRIVATE_PLATFORM_APIS := true
Changes in bold
Berni-0815 said:
I'm sorry; I should have tell you about that... :angel:
I changed a lot of things to compile it successfully. Here are my changes (I hope this list is complete):
.bashrc:
Code:
export CPU_SSE42=false
to avoid crashes in hiddenapi and profman
device/sony/kitakami-common/SonyOtgSwitch/Android.mk:
Code:
LOCAL_SDK_VERSION := current
kernel/sony/msm8994/include/uapi/linux/rmnet_data.h; insert lines 226 to 236 (line 226 changed [a comma at the end of line]):
Code:
RMNET_NETLINK_DEL_VND_TC_FLOW,
/*
* RMNET_NETLINK_NEW_VND_WITH_NAME - Creates a new virtual network
* device node with the specified
* device name
* Args: int32_t node number
* char[] vnd_name - Use as name
* Returns: status code
*/
RMNET_NETLINK_NEW_VND_WITH_NAME
bionic/libc/include/bits/fortify/fcntl.h; insert lines 33 to 36:
Code:
#ifndef __O_TMPFILE
#define __O_TMPFILE 020000000
#endif
#define O_TMPFILE (__O_TMPFILE | O_DIRECTORY)
hardware/qcom/audio-caf/msm8994/hal/audio_hw.c; line 2457:
Code:
ALOGE("%s: error [B]%ld[/B] - %s", __func__, ret, pcm_get_error(out->pcm));
hardware/qcom/audio-caf/msm8994/hal/audio_extn/audio_extn.c; lines 523 and 524:
Code:
void audio_extn_set_parameters(struct audio_device *adev [B]__unused[/B],
struct str_parms *parms [B]__unused[/B])
and line 67:
Code:
static struct audio_extn_module aextnmod [B]__unused[/B] = {
hardware/qcom/display-caf/msm8994/libqdutils/idle_invalidator.cpp; line 127:
Code:
ALOGD_IF(II_DEBUG, "IdleInvalidator::%s Idle Timeout fired len [B]%ld[/B]",
hardware/qcom/display-caf/msm8994/libhdmi/hdmi.cpp: line 196:
Code:
ALOGD("%s: Scan Info string: %s length = [B]%ld[/B]",
and line 320:
Code:
ALOGD_IF(DEBUG, "%s: EDID string: %s length = [B]%ld[/B]",
device/sony/kitakami-common/SonyOtgSwitch/Android.mk: line 5:
Code:
LOCAL_PRIVATE_PLATFORM_APIS := true
Changes in bold
Click to expand...
Click to collapse
Yup I made those changes except for
Code:
export CPU_SSE42=false
I did not get any issues building but the device does bootloop. I'm gonna see if we can try and pull any sort of logs to see what's causing the issue.
Joel16 said:
Yup I made those changes except for
Code:
export CPU_SSE42=false
I did not get any issues building
Click to expand...
Click to collapse
That seems to be a problem with my cpu. The mentioned line is a cpu instruction. While trying to build this rom on my pc I ran into errors.
but the device does bootloop. I'm gonna see if we can try and pull any sort of logs to see what's causing the issue.
Click to expand...
Click to collapse
Maybe it's possible to backup the system onto a sd-card with an actual twrp and analyse these files?
Berni-0815 said:
That seems to be a problem with my cpu. The mentioned line is a cpu instruction. While trying to build this rom on my pc I ran into errors.
Maybe it's possible to backup the system onto a sd-card with an actual twrp and analyse these files?
Click to expand...
Click to collapse
I'm not entirely sure how it works, but I have heard people talking about pulling logs form bootloops. I mean there has to be a way to debug a bootloop, I highly doubt people just blindly fix them. Perhaps we can access last kernel message or logcat, someway. I'm going to try this weekend and see what I can come up with.
You can do It!!!
Joel16 said:
I'm not entirely sure how it works, but I have heard people talking about pulling logs form bootloops. I mean there has to be a way to debug a bootloop, I highly doubt people just blindly fix them. Perhaps we can access last kernel message or logcat, someway. I'm going to try this weekend and see what I can come up with.
Click to expand...
Click to collapse
Berni-0815 said:
That seems to be a problem with my cpu. The mentioned line is a cpu instruction. While trying to build this rom on my pc I ran into errors.
Maybe it's possible to backup the system onto a sd-card with an actual twrp and analyse these files?
Click to expand...
Click to collapse
What is about adbd, see here:
https://forum.xda-developers.com/showpost.php?p=67386761&postcount=13
The z5c is based on Qualcomm Snapdragon 810 MSM8994, like:
SONY XPERIA Z5 PREMIUM | MOTOROLA DROID TURBO | MICROSOFT LUMIA 950 XL | NUBIA Z9 MAX
Is there any source of a pie build availible where we can get some hints how get a pie build to run?
Here are some kernel sources from the Nubia Z9 Max (nx510j):
https://github.com/nubia-development/android_kernel_nubia_msm8994
I_did_it_just_tmrrow said:
What is about adbd, see here:
https://forum.xda-developers.com/showpost.php?p=67386761&postcount=13
Click to expand...
Click to collapse
I'll have a look at this. :good:
Joel16 said:
Have you tried looking at any sort of logs, kernel logs? (I'm not sure if there would be one in the first place) It would be better to try by increments (PIE first with https://github.com/joel16/android_kernel_sony_msm8994). I might give it a try this weekend just for the sake of it.
Click to expand...
Click to collapse
For my self I try slowly become deeper into that topic: building a rom.
So I did a little bit of research in github and gitlab and I found some interesting repos from this user:
https://github.com/Cyborg2017?tab=repositories
I ask him if he could help us a little bit and the first result is this.
@Joel16 & @Berni-0815 Perhaps this is useful:
https://github.com/Cyborg2017/android_kernel_sony_msm8994/tree/sony_msm8994_p-upstream
I hope it help us to come closer to an LineageOS 17 for suzuran.
I_did_it_just_tmrrow said:
I ask him if he could help us a little bit and the first result is this.
Click to expand...
Click to collapse
Error 404
A little time later: I think, you're talking about this kernel?
---------- Post added at 16:22 ---------- Previous post was at 16:03 ----------
I_did_it_just_tmrrow said:
What is about adbd, see here:
https://forum.xda-developers.com/showpost.php?p=67386761&postcount=13
Click to expand...
Click to collapse
Tried the mentioned tip in the 2nd post of this that thread without any success. I'm so sorry.
How can I include adbd into my build? I'll give it a try...
Berni-0815 said:
Error 404
A little time later: I think, you're talking about this kernel?
---------- Post added at 16:22 ---------- Previous post was at 16:03 ----------
Tried the mentioned tip in the 2nd post of this that thread without any success. I'm so sorry.
How can I include adbd into my build? I'll give it a try...
Click to expand...
Click to collapse
Yep, just try his source. He told that it could be useful to test this kernel with building twrp first.
To the logging problem. I understand that right that you have nothing in:
Code:
/proc/last_kmsg
Nor in:
Code:
/sys/fs/pstore/console-ramoops
and you check this with the twrp terminal?
You should take a look at this:
https://android.stackexchange.com/questions/213336/how-can-i-enable-last-kmsg
I_did_it_just_tmrrow said:
Yep, just try his source.
Click to expand...
Click to collapse
I'm actually building a rom with that kernel. I'll see later if it's working.
To the logging problem. I understand that right that you have nothing in:
Code:
/proc/last_kmsg
Nor in:
Code:
/sys/fs/pstore/console-ramoops
and you check this with the twrp terminal?
Click to expand...
Click to collapse
Right
You should take a look at this:
https://android.stackexchange.com/questions/213336/how-can-i-enable-last-kmsg
Click to expand...
Click to collapse
Ah! Nice. I'll try it later. Thank you very much! :good:
Berni-0815 said:
I'm actually building a rom with that kernel. I'll see later if it's working.
Right
Ah! Nice. I'll try it later. Thank you very much! :good:
Click to expand...
Click to collapse
Let me know how it goes, I'm more than certain kernel is what's preventing us from getting Pie/Q to boot up.
So I'm trying to get halium working for tab 2 (we can get ubuntu touch and maybe even plasma mobile with help of it) and I get this error
Code:
arch/arm/boot/compressed/atags_to_fdt.o: In function `merge_fdt_bootargs':
atags_to_fdt.c:(.text+0x20c): undefined reference to `__stack_chk_fail'
atags_to_fdt.c:(.text+0x210): undefined reference to `__stack_chk_guard'
It seems to be a toolchain error any help?
"It would appear that the -mstack-protector-guard option is only for backwards compatibility with how the stack protector worked in the past. In the past the canary was in a global variable. Later it was switched to TLS. It would appear that the operating system / libc you use either removed or never had support for the global variable canary, so only TLS works.
Don't touch the -mstack-protector-guard option and everything should work. The default should be fine when you use -fstack-protector-all."
"Provide __stack_chk_guard with a random value in c file, avoid using regular values like all zero's or FF's because the stack can easily get these values during any memory operation. Wiki on providing magic number implementation. This __stack_chk_guard will be placed at the top and bottom of the stack, which will be checked during every stack access. Any change in the value implies a corrupted stack and returns with error providing the stack protection.
unsigned long __stack_chk_guard;
void __stack_chk_guard_setup(void)
{
__stack_chk_guard = 0xBAAAAAAD;//provide some magic numbers
}
void __stack_chk_fail(void)
{
/* Error message */
}// will be called when guard variable is corrupted "
"There are two ways to remove this error: 1. From the compiler option disable(comment out) the "stack guard".
Define __stack_chk_guard in you c file.
When you define __stack_chk_guard make sure you provide random value to it. For providing random value you need to pass as an argument to the random function.
For any further detail you can refer to the compiler manual."
"For those that get this error in bare metal software development with a custom linker script, make sure to pass the option -nostdlib option:
gcc -nostdlib
since Ubuntu 16.04 for example enables the stack protection by default on the compiler. man gcc says:
NOTE: In Ubuntu 14.10 and later versions, -fstack-protector-strong is enabled by default for C, C++, ObjC, ObjC++, if none of -fno-stack-protector, -nostdlib, nor -ffreestanding are found.
-fno-stack-protector also solved it for me, but you should likely tell your poor compiler that you are doing baremetal stuff to prevent other such problems.
I'm guessing this is because the feature relies on symbols which are normally defined if a linker script is not given? But TODO I found no mention of those symbols by dumping the default linker script with:
aarch64-linux-gnu-gcc -Wl,-verbose main.c
so I'm not sure.
I grepped GCC 6.4.0 source code and it suggests that the symbol comes from libgcc2.c at gcc/doc/tm.texi:
The default version of this hook creates a variable called @samp{__stack_chk_guard}, which is normally defined in @file{libgcc2.c}."
Click to expand...
Click to collapse
source: https://stackoverflow.com/questions/27290086/gcc-canaries-undefined-reference-to-stack-chk-guard
i cant wait to use this and your other project (sailfishos)!
wizzer48 said:
i cant wait to use this and your other project (sailfishos)!
Click to expand...
Click to collapse
Yes even I can't wait for both as there is no latest development for our tab !!!
Arc android said:
Yes even I can't wait for both as there is no latest development for our tab !!!
Click to expand...
Click to collapse
Halium doesnt seem to work i tried but to no avail
Mithil17 said:
Halium doesnt seem to work i tried but to no avail
Click to expand...
Click to collapse
Its OK at least you tried to build it !!
Hey I have a great idea Mithil17, can you try to build MIUI 7 for galaxy tab 2? There was an attempt to build it earlier but it wasn't successful.
Arc android said:
Hey I have a great idea Mithil17, can you try to build MIUI 7 for galaxy tab 2? There was an attempt to build it earlier but it wasn't successful.
Click to expand...
Click to collapse
MIUI ??? Why do you wanna china bloadware sooo badly?? what's wrong with LOS or any other bloadware free ROMs?
Plus it's gonna be laggy as h3ll... done and forgotten.
drnightshadow said:
MIUI ??? Why do you wanna china bloadware sooo badly?? what's wrong with LOS or any other bloadware free ROMs?
Plus it's gonna be laggy as h3ll... done and forgotten.
Click to expand...
Click to collapse
Yeah I know it's Chinese but it looks beautiful. You'll know it if you have tried mini 5 for tab 2.
Arc android said:
Yeah I know it's Chinese but it looks beautiful. You'll know it if you have tried mini 5 for tab 2.haha
Click to expand...
Click to collapse
Haha, no thank you! I'm happy with LOS and RR ROMS. I own redmi note 5 pro but never used MIUI [email protected], I unlocked bootloader and installed LOS asap. I like to have privacy in my hand and I hate when OS wanna rape my privacy. My privacy isn't on sale.
drnightshadow said:
Haha, no thank you! I'm happy with LOS and RR ROMS. I own redmi note 5 pro but never used MIUI [email protected], I unlocked bootloader and installed LOS asap. I like to have privacy in my hand and I hate when OS wanna rape my privacy. My privacy isn't on sale.
Click to expand...
Click to collapse
If you actually want this much privacy, here's something for you : https://androidfilehost.com/?fid=17248734326145705104
An unofficial /e/os build for your device. Just trying to help you in case you didn't know this. That's all !
Arc android said:
If you actually want this much privacy, here's something for you : https://androidfilehost.com/?fid=17248734326145705104
An unofficial /e/os build for your device. Just trying to help you in case you didn't know this. That's all !
Click to expand...
Click to collapse
whyred = Redmi Note 5. Not SGT2
Are you sure? It can brick device
levider said:
whyred = Redmi Note 5. Not SGT2Are you sure? It can brick device
Click to expand...
Click to collapse
Note 5/pro = whyred that's what Google says.
Also in the above link, it is made for redmi note 5 pro
Official /e/ forum link : https://www.google.com/url?sa=t&sou...FjACegQIBBAC&usg=AOvVaw1iyAyl2Ur__Xid-tw1cRCz
I hope I am not doing anything wrong
Arc android said:
Note 5/pro = whyred that's what Google says.
Also in the above link, it is made for redmi note 5 pro
Click to expand...
Click to collapse
Dude, this is not Redmi Note 5 thread.
Update: It boots now, Sources are in https://github.com/Halium/projectmanagement/issues/238 no ui still
Mithil17 said:
Update: It boots now, Sources are in https://github.com/Halium/projectmanagement/issues/238 no ui still
Click to expand...
Click to collapse
So we can install it now ???? !!!!!
Arc android said:
So we can install it now ???? !!!!!
Click to expand...
Click to collapse
Well you can just install it, it just boots, no ui/display
Mithil17 said:
Well you can just install it, it just boots, no ui/display
Click to expand...
Click to collapse
So it means even if I install it, it can't be operated. Why some things are way too difficult for tab 2 ?? I mean miui7, sfos, treble, Oreo and now haloum are ported to other devices too that are mostly similar to ours but running them on tab 2 is a bit more difficult.