Related
Is there EAP-SIM support in OnePlus 2?
EAP-SIM is supported by my carrier (France/Free) to connect phone to nearby WiFi Hotspots automatically using mobile account identification.
There are some posts around here talking about this feature (here and there for example).
It is not provided in AOSP, the android issue #9329 is open since 2012 asking for it.
Apple, Samsung, LG, HTC, Sony... phones support it through custom OS or Android overlay.
So the real question is: Do Oxygen OS provide it?
EDIT/ANSWER :
It works fine. I've used it multiple times.
Carrier application (Free) says it supports it
I just received the phone yesterday and installed an application provided by my carrier to configure Visual Voice Mail (Messagerie Free).
The application can also configure EAP-SIM and said that the phone is compatible and I completed its configuration.
However I didn't had the change to test it (EAP-SIM).
I'll post a reply if I'm able to test it.
Connection occurs
I saw the phone connecting to an EAP-SIM WiFi Hotspot (FreeWiFi_Secure), however I couldn't confirm the connection was working (I was driving, so safefty first).
It seems to be working, I just have to confirm it (browse some website when connected to a EAP-SIM WiFi Hotspot).
It works
I can confirm it works.
I've used it multiple times.
So good news.
Hi everyone !
Are you SURE EAP-SIM is working on the Oneplus 2 (the 2, not the one).
I had the oneplus ONE and, yes, it IS working, "Messagerie Vocale Free" can configure Freewifi_secure for the phone.
But I now have the Oneplus TWO and "Messagerie Vocale Free" cannot configure it : It says it cannot configure EAP-SIM on Dual SIM phones, you have to configure it manually. And when trying to configure EAP-SIM manually.. it's not possible...
I'm talking about stock ROM (Oxygen OS 2.1.2)
Yea it works I'm on stock rom and AK kernel.
In Singapore I needed Eap Sim for my provider's free WiFi, so it kind of look like this
network={
ssid="SingTel WIFI"
key_mgmt=WPA-EAP IEEE8021X
eap=SIM
sim_num=1
priority=235
}
network={
ssid="Singtel WIFI"
key_mgmt=WPA-EAP IEEE8021X
eap=SIM
sim_num=1
priority=242
}
The settings were automatically disabled by the phone once added for some reason, I thought it didn't work and left the code there until one day I realize I was connecting to the WiFi through Eap Sim. Nt sure what I did in between that made it work. Perhaps restart or add only when WiFi is off or disable then enable background WiFi scan
Take note that there are two wpa_supplicant file. The correct one should have some WiFi AP already there if u have previously connected to any WiFi AP. The path should be system>data>misc>WiFi
I modified the file using fx file manager with the free root add-on. Which means u need to root ur phone in order to change the settings. ES file explorer didn't work for me
10/8/16:
I've upgraded to Paranoid 6.0.2, there is EAP-SIM option when connecting to Singtel WiFi however it will always result in "Authentication Problem".
I've tried many ways to fix it:
- Removing pmf = 1
- Setting DHCP back to lollipop
- Disable 1.2 and 1.1 TLS for compatibility
- Adding sim_num = 1 (will be removed by driver due to external_sim = 1)
All of them did not work for me.
The only one that did work was to use EAP-AKA instead of EAP-SIM. It even works for [email protected] too.
P"
Thanks all for your advices,
Here is the procedure for French FREE MOBILE + OP2 users
The correct file "wpa_supplicant.conf" is in System(root)/data/misc/wifi as Imk1988 said (so grateful to him btw)
(do not modify the other wpa_supplicant.conf file in System(root)/etc/wifi)
Add this line
network={
ssid="FreeWifi_secure"
key_mgmt=WPA-EAP IEEE8021X
eap=SIM
sim_num=1
priority=5
}
after rebooting, it's working like a charm
Conditions:
SIM FREE MOBILE in slot 1
OP2 rooted
Hi lmk1988,
I tried using your method for Singtel WiFi (using a Oneplus X on CM12.1) and it's not working I'm afraid. I could edit the file successfully, but I get a "WiFi connection failed" when I try to connect.
Will try again later!
(I'm wondering if it's just that CM doesn't support EAP-SIM at all...)
Unfortunately I'm using oneplus two (custom rom: SkyDragon v3.1 OOS2.2 and Boeffla 1.1-beta3) now.
Not really sure if it will work for oneplus X
Anyway do make sure u are modifying the correct file, there are two files with the same name.
And note that not all Singtel WiFi will work. It's funny it can be working on one day then not working the next. Kinda depends on time and place.
---------- Post added at 08:59 AM ---------- Previous post was at 08:27 AM ----------
Okay the issue seems to be from CM12.1 oneplus X
Take a look at bbs.zhiyoo.com/thread-9972195-1-1.html
(T.T I can't post links yet because under 10 post)
It's in Chinese but if you look at what they say for version 8
Code:
8.0更新：
回滚7.0版本的音频驱动设置
回声问题应该解决了
禁用EAP-SIM 设备本身不支持
It basically means
Code:
version 8.0:
Reverted Audio Driver to 7.0
Echo issue have been be fixed
[B]Restricted EAP-SIM setting, it is not supported[/B]
I'm not sure if it means CM12.1 for oneplus X does not support EAP-SIM, or does it mean oneplus X does not support EAP-SIM.
Try changing your ROM back to OOS and see if it works
I see.
Thanks man! I don't really know much about coding, etc., and finding out where everything us. Just kinda winging it by searching through forums and so on.
So really appreciate the help and the info! = )
I'm not sure if I'll try to switch back to the stock OS at the moment, found CM to be preferred at the moment. If I do, though, I'll let you know!
Hello,
since I'm not qualified (yet) to post this in the developer thread for the X compact - here's a LineageOS 14.1 ROM for the device to be flashed with fastboot as stated on Sony's website for the AOSP ROM (fastboot –S 256M flash boot boot.img etc).
filefactory.com/file/5wfgwk1cmzw9/LineageOS-05-03-2017-kugo.zip
Things that don't work so far:
* AudioFX (use PowerAMP or VLC for mp3 replay with bass boost/EQ)
* FM radio (no stations found at all)
Big thanks to the LineageOS team, the SonyLOS guys and Sony itself
Enjoy,
jtk_de
jtk_de said:
Hello,
since I'm not qualified (yet) to post this in the developer thread for the X compact - here's a LineageOS 14.1 ROM for the device to be flashed with fastboot as stated on Sony's website for the AOSP ROM (fastboot –S 256M flash boot boot.img etc).
filefactory.com/file/5wfgwk1cmzw9/LineageOS-05-03-2017-kugo.zip
Things that don't work so far:
* AudioFX (use PowerAMP or VLC for mp3 replay with bass boost/EQ)
* FM radio (no stations found at all)
Big thanks to the LineageOS team, the SonyLOS guys and Sony itself
Enjoy,
jtk_de
Click to expand...
Click to collapse
Hi! Thanks for this rom. I will try it when i am at my home pc. But, a question. It's got a built-in-root? Or we use the add on root package? Or use magisk phh superuser? I'm a little confused about the root process.
Re:
lba810701 said:
Hi! Thanks for this rom. I will try it when i am at my home pc. But, a question. It's got a built-in-root? Or we use the add on root package? Or use magisk phh superuser? I'm a little confused about the root process.
Click to expand...
Click to collapse
To install, as with the Sony AOSP ROM, your bootloader must have been unlocked. After installation via fastboot root access can be enabled in the developer options.
If you want to build the ROM yourself init the LineageOS sources from github (cm14.1 branch) and add the local_manifests folder from SonyLOS (also on github) to the .repo directory to have a device profile and the binary blobs for the X compact aka kugo. Then repo sync, and brunch lineage_kugo-userdebug.
Hi!
I flashed your homemade rom. My first impression, is it's very smooth. But I found some little bugs? First is a LineageOS recovery. I must flash OpenGapps twice, to install it correctly. ( second time i mount the system inside advanced settings... maybe thats the key ) Second one is a fingerprint sensor. I can't make it to work. Neither on first run, neither later in the settings. Phone calling working, but sometimes it's dialer force stop in middle of the voice calling. ( but you could speak, just a notification came up about the FC ). Bluethooth seems ok, about music listening and about calling. Camera with the roms app is working. But, google cam doesn't start. On selfie picture, the picture is upside down. Root is inside developer settings, and it seems working fine. ( except flashfire... ) I'm using kernel toolkit ( v 1.2.1 ), and it's showing me the big cores allways off, and the phone doesn't go to deep sleep. About the battery life time i can't say too much, because the roms is nearly one day on my phone. I think it's a good start the LinageOS 14.1 to our phone. Thanks again.
Re:
lba810701 said:
Hi!
I flashed your homemade rom. My first impression, is it's very smooth. But I found some little bugs? First is a LineageOS recovery. I must flash OpenGapps twice, to install it correctly. ( second time i mount the system inside advanced settings... maybe thats the key ) Second one is a fingerprint sensor. I can't make it to work. Neither on first run, neither later in the settings. Phone calling working, but sometimes it's dialer force stop in middle of the voice calling. ( but you could speak, just a notification came up about the FC ). Bluethooth seems ok, about music listening and about calling. Camera with the roms app is working. But, google cam doesn't start. On selfie picture, the picture is upside down. Root is inside developer settings, and it seems working fine. ( except flashfire... ) I'm using kernel toolkit ( v 1.2.1 ), and it's showing me the big cores allways off, and the phone doesn't go to deep sleep. About the battery life time i can't say too much, because the roms is nearly one day on my phone. I think it's a good start the LinageOS 14.1 to our phone. Thanks again.
Click to expand...
Click to collapse
Thank you for testing. You're right there's some more issues. I was able to unlock the phone with the fingerprint sensor once but I guess this should work a little bit more smoothly. Face camera image is vertically flipped. Normal phone operation seems to be OK, battery runtime also. Didn't examine core load nor install Google apps so I can't say anything about it. All in all it looks quite usable but needs a little bit of fine tuning
Flashed your ROM yesterday (coming from an unofficial cm14.1 build) and till now everything runs smooth. I didn't flash recovery.img since I already had twrp flashed and flashing opengapps was also successful. Fingerprint sensor is working too. The camera quality is bad, but that's what I have with every custom ROM.
Issues I found out so far:
- registering the fingerprint sensor for purchases in the play store doesn't work, play store closes upon trying to set it up
- the volume when calling can't be changed
Maybe there's something else but I'm really satisfied. I hope you keep on updating the rom jtk_de
can you give us a short update on this?
Still Progressing?
Is this still being developed?
The thread seems to have been continued here: https://forum.xda-developers.com/x-compact/help/rom-lineageos-14-1-sonylos-7-1-binaries-t3584504/
jtk_de said:
If you want to build the ROM yourself init the LineageOS sources from github (cm14.1 branch) and add the local_manifests folder from SonyLOS (also on github) to the .repo directory to have a device profile and the binary blobs for the X compact aka kugo. Then repo sync, and brunch lineage_kugo-userdebug.
Click to expand...
Click to collapse
@jtk_de
Is there currently any place where can I find the source code?
The reason I ask this question is that SonyLOS (github.com/SonyLOS) has been removed.
This is stackexchange issue I raised on this issue :
<a href="http://android.stackexchange.com/questions/171241/wifi-hotspot-timeout-setting-gone-in-nougat-7-0-7-1-but-timeout-has-not">
Wifi HotSpot timeout setting gone in Nougat 7.0 , 7.1, but timeout has not</a>; .
(answered only by myself).
I have observed, on receipt of my new AGM A8 QualComm 410 MSM8916 Android 7.0 phone , that the Wifi-HotSpot keeps timing out
after 2-5 mins . I am trying to connect my Linux 4.10 x86_64 host, using its iwlwifi driver, and wpa_supplicant + ISC dhclient, and it
does connect fine, for 2-3 minutes, but then the android phone (default DHCP router) stops responding to ping requests, and the
link is dead , until I bring the device down on the linux host & kill & respawn wpa_supplicant & dhclient . The script I use to do this
is attached. One weird thing is that even though the Android device stops responding to pings, it may still be passing pings through
to the WAN internet , so my script has to trying pinging an actual internet address like www.kernel.org (one of the few public IP
addresses left that respond to ICMP).
This is really nasty of Android Nougat, especially as the previous Android version I used on my old phone (4.2.2)
had a Wifi-HotSpot Timeout Options Settings dialog , which let you specify inactivity timeouts .
So I had to develop this complicated workaround where my 'network' init.d script does
PID_FILE=/run/wlan_ping_monitor.pid daemon /etc/init.d/wlan_ping_monitor.sh
which keeps the link alive.
I really need to root this phone, so I can install my own /etc/hosts file / ISC BIND9, fix this issue in /etc/default.hostapd.conf settings,
and maybe try to fix hostapd , & be able to view logs .
Any advice on how to create a custom recovery for this phone ? latest TWRP & CyanogenModROMs do not support it.
It looks similar to the WileyFox Swift , for which there is a lineageos 14.1 build . Should I try this ?
I am focusing on trying to build android & android_bootable_recovery and android_rooting_tools gitweb gits, & then build AOSP
& TWRP & a recovery ROM - any advice gratefully received.
This is linux kernel bug : https://bugzilla.kernel.org/show_bug.cgi?id=194931
and stackexchange issue: http://android.stackexchange.com/qu...ng-gone-in-nougat-7-0-7-1-but-timeout-has-not
The kernel could be responding better to the empty data frame sent by Nougat hostapd on ap_max_inactivity=300 timeout.
Also wpa_supplicant should be detecting the link has gone dead & re-initializing .
Hi guys,
the trouble began when switching my AP from 2.4 GHz wifi to 5 GHz.
After some time in which everything worked well, it would just suddenly bloody stop working.
It started like this: random disconnect from the wifi, reconnect and then just stopped working (no ssids visible).
Normally I could restart and the problem was gone, but now it is persistent even throughout reboots and I therefore have to use the mobile network (which is really expensive where I live).
I'm using Lineage OS 16, but the problem was also there when I used previous releases iirc which is why I changed the phone for some time.
What I tried:
* flash different firmware versions
* upgrade /system LOS
* restart
* set interface down/up
* delete entry for my SSID and create it again
Right now nothing works.
Maybe someone has knowledge about the internals of the wifi on this SoC.
How is the general design?
E.g. I saw that the kernel loads some files (wcnss.mdt, wcnss.bXX) that are inside the NON-HLOS.bin disk image.
I assume that the trustzone does something with it?
Very weird architecture to get wifi going and debug it.
What are things that I can try?
Does the driver / firmware / android store data that might lead to a different state after reboot and this behavior being persistent?
Who else had this kind of problem?
I also opened an issue at the LineageOS bugtracker where I pasted some excerpts of dmesg / logcat and bit more details https: //gitlab.com/ LineageOS/issues/android/issues/1323 (not allowed to post URLs).
Right now I'm not sure what it is, could be firmware (and therefore not LOS related, which right now I think is more likely) or e.g. kernel or who knows, maybe even hardware?
Thanks!
BEFORE YOU decide to try this rom, please read all of post 1 and 2.
The UNOFFICIAL LineageOS 17.1 T550 ROM
BACKUP YOUR DATA AND OLD ROM BEFORE trying my rom.
Let me be clear, I have the SM-P550, NOT the SM-T550.
So I built a SM-P550 rom which is almost the same as the SM-T550 except the "P" stands for Pen.
I believe my P550 rom with minor modifications will work on the T550, but I have no T550 to test it on. I believe it will work because I have used virsys T550 rom on my P550 and it works, but the X-axis touch is inverted.
So I built SM-P550 with code to fix the X-axis touch inverted problem and it's one of line code. If I leave that one line of code out, then the X-axis will be correct for the T550. I have tested my 17.1 T550 rom on my P550 and it works, but again with the X-axis inverted. Just remember I don't have a T550 to test it on so you may run into bootloops, stuck at boot animation, etc.
If you are NOT an expert in using fastboot, adb, odin, heimdall, twrp, DO NOT attempt this ROM. You must know how to use these tools to revert back to your old rom. I'm not a Windows user so do not expect any help from me. My main OS is Lubuntu 20.04 LTS and all my roms are built on this platform.
If you are new to flashing custom roms, do NOT attempt this.
If you need your tablet for work and something important, do NOT flash this rom. This rom could result in a bricked device or boot loop or non booting device or you not being able to revert back to your old rom.
Again, the T550 rom that I built does boot and function on my P550, but I have no T550 to verify.
BACKUP YOUR DATA AND OLD ROM BEFORE trying my rom.
The rom has the latest monthly 2021 security patches.
What works
1. bluetooth
2. wifi
3. brightness
4. external audio
5. GPS
6. audio through headphone jack
7. camera
8. touchscreen X-axis works properly
9. Google play store - use pico apps
10. flip flap smart cover
11. audio over bluetooth
What doesn't work
1. LineageOS FM Radio app does not work. The P550 and T550 don't have the LTE chipset for it to work.
2. The stock Jelly browser crashes a lot. Use a different browser. There's lots of better options that are more stable and reliable than the built in Jelly browser.
3. Home screen text may look fuzzy.
Text on home screen looks funny/fuzzy. This only seems to affect the home screen and nowhere else. I have seen the same problem on the SM-T350, SM-T560NU, SM-P550 and Nexus 7 2013.
Problem is with stock trebuchet launcher and/or its fonts. I tried rootless pixel launcher from fdroid as a quick and simple test and see no problems with home screen text. Rootless pixel uses a different font though. A future LineageOS update could resolve the problem?
FAQ - I spent hundreds of hours building this rom. The least you can do is spend a few minutes reading everything before posting.
Q1) Why are you releasing a ROM for a tablet that you do not own?
A1) I don't own the SM-T550, but have the SM-P550. I also build roms for the SM-T350 and SM-T560NU. All these platforms use the same msm8916 code base. As such, all my work from the SM-T350, SM-T560NU and SM-P550 could possibly benefit SM-T550 users. For one P550 owner, there are probably twenty T550 owners.
Q2) What if my app, xyz, doesn't work?
A2) I won't answer questions regarding why your app doesn't work. If your app, whatever it is, doesn't work, then go back to your old rom. It's difficult enough building and maintaining these roms. Remember, I'm an unpaid volunteer making a rom for free for your benefit, not mine as I don't even have the T550.
Q3) Your rom is laggy and buggy.
A3) If you find the above, then go back to your old rom. There's only so much software can do on a 2015 budget level tablet. Remember a budget tablet will have the slower SoC/CPU and less DRAM than a top of the line model. Your tablet will also run slower when you use gapps (google apps). You can run a lot of software without using gapps. Research newpipe, microg, youtube vanced, aurora store etc.
Q4) What TWRP should I use?
A4) Use 3.4.0.0. Get it at
Download TWRP for gt510wifi
Download TWRP Open Recovery for gt510wifi
dl.twrp.me
Q5) Why should I use this rom?
A5) You don't. I only offer it because I have built the SM-P550 and it was an easy change to make a SM-T550 rom. If you don't like this rom, then don't use it. Yes, it's that simple.
Q6) Can you build SM-T555 (LTE) or a crDroid version of the SM-T550?
A6) No. All the source code is open source and my changes are in the repo diff file. You can use these two with the roomservice.xml to build your own rom.
Q7) Will you offer monthly updates with security patches?
A7) That all depends on if I continue to have high speed Internet and on the reaction of the posts in this thread. If people are going to complain, then I have NO incentive to make an update. Remember, I don't have the T550 so I get zero benefit from making this rom for myself.
Q8) Can you help me? I'm a newbie. Can you provide step by step instructions?
A8) There are lots of tutorials, videos, etc on how to flash roms. Do your own research.
Q9) Can I report a bug with respect to the rom?
A9) Yes, but you need to supply a) how to recreate it b) a logcat c) a github commit showing how it was fixed. Even then, if I don't have the means to recreate it, I won't be working on it.
Q10) Can I build this rom? Where are the source and kernel source files?
A10) Yes. The kernel source files are at
Samsung MSM8916 Devices
Samsung MSM8916 Devices has 68 repositories available. Follow their code on GitHub.
github.com
aala27 - Repositories
aala27 has 7 repositories available. Follow their code on GitHub.
github.com
Q11) Okay, I understand the consequences and that this is beta rom and willing to take the risks outlined, now where can I find the rom?
A11) Downloads are at
retiredtab - Browse /SM-T550/17.1 at SourceForge.net
sourceforge.net
Hi rretiredtab
I have a T550 with the latest virsys image 16.0 from March 2020.
It is more or less stable, but I think, it will be always slowlier. Empty dalvic and cache does not help.
I'm ready for a new challenge. If I can help you, please let me know.
Best regards
Schaagi
Hi retiredtab,
I ready to try this rom
Schaagi said:
I have a T550 with the latest virsys image 16.0 from March 2020. It is more or less stable, but I think, it will be always slowlier. Empty dalvic and cache does not help.
Click to expand...
Click to collapse
My 16.0 rom for the SM-P550 is based on virsys repos. However, I was only able to make 2 builds using his repos before a LineageOS update in Sept 2020 caused it to get stuck at the boot animation.
Then I tried virsys 17.1 repo and it too gets stuck at the boot animation. I know virsys built crDroid Android 10 rom and uploaded it sometime June 2020, but his Android 10 repos on github are dated March 2020 so whatever patches he did to get crDroid working isn't on github.
I don't know if 17.1 will be faster than 16.0. The 17.1 builds, by default, use an overclocked CPU and GPU in the kernel code. However, I don't know if you will see any real world differences in performance from the overclocking.
In addition, I don't know if virsys March 16.0 March 2020 is overclocked or not. You can always download an utility like CPUinfo at
CPU Info | F-Droid - Free and Open Source Android App Repository
Information about device hardware and software
f-droid.org
to see if the CPU is running at 1.2Ghz or 1.6Ghz (overclocked).
@Schaagi and @Simone101, please let me know if the T550 ROM boots or not after you have installed it. I'm pretty sure it will, but would like to know ASAP.
Then, afterwards, you can let me know how it works over a 24 to 48 hour period. I'm interested to see if it randomly reboots or crashes.
As for speed and performance, just remember it's a 5 year old entry level tablet and unless LineageOS is written in assembler language, it will never match a top of the line model tablet.
Thank you.
I've installed your image as clean-install. It boots !!!
At the beginning of the setup process there is a bluetooth error, that repeats after every new boot.
First installation without opengapps -ok
Second one with opengapps - ok
Restore Data from previous image - ok
As next I will try to install magisk.
Wow, good job. I will check it for the next days and give feedback later.
Best regards
Schaagi
Schaagi said:
At the beginning of the setup process there is a bluetooth error, that repeats after every new boot.
Click to expand...
Click to collapse
Can you provide a screenshot of the error please?
I haven't seen the bluetooth error before on my SM-P550 and I reboot my SM-P550 a lot because I'm always flashing new builds.
I don't use bluetooth at all, but when I turn it on, I can see my neighbor's 65 inch TV. Also, I can pair two tablets together using bluetooth.
Meanwhile I have installed Magisk 21.1 and it works too
I've attached 2 screenshots from Bluetooth error.
Schaagi said:
I've attached 2 screenshots from Bluetooth error.
Click to expand...
Click to collapse
The above is why we need BETA testers.
Okay, I ran into the bluetooth error problem on the SM-T350 and it was due to a missing bluetooth library.
In my SM-T350, I have
Code:
# RT 17.1 copy bluetooth file otherwise bluetooth keeps crashing
PRODUCT_COPY_FILES += \
vendor/samsung/msm8916-common/proprietary/vendor/lib/libbtnv.so:$(TARGET_COPY_OUT_VENDOR)/lib/libbtnv.so
Those 3 lines of code are not in the T550 build. It's easy to add and I can create another BETA build. It's building right now and probably be done in the next 2 hours or so.
If you want to add the libbtnv.so file yourself, here are the instructions
1) Boot into TWRP 3.4.0.0.
2) Click Mount. Choose System.
3) On your computer, goto
proprietary_vendor_samsung/libbtnv.so at lineage-17.1 · Galaxy-MSM8916/proprietary_vendor_samsung
proprietary_vendor_samsung. Contribute to Galaxy-MSM8916/proprietary_vendor_samsung development by creating an account on GitHub.
github.com
4) Click download.
5) Goto the directory where the libbtnv.so is saved.
6) Plug in microusb cable to tablet.
7) Then use adb to push the file using the command
Code:
$ adb push libbtnv.so /system/vendor/lib/libbtnv.so
libbtnv.so: 1 file pushed, 0 skipped. 48.5 MB/s (16128 bytes in 0.000s)
8) Check to make sure file was pushed.
Code:
$ adb shell ls -al /system/vendor/lib/libbtnv.so
-rw-r--r-- 1 root root 16128 Dec 19 21:24 /system/vendor/lib/libbtnv.so
9) Reboot into system and bluetooth error should be gone.
OR
Just wait until my next build is done to get rid of the bluetooth errors. I'm confident the error is due to the missing bluetooth library file.
I will send you and Simone101 a PM when the new build is done.
The new BETA build is finished, but having problems uploading to host server right now. I will try again in a couple of hours to upload. I will PM when I get it uploaded.
I've installed the new image and bluetooth error has gone.But I'didn't test the functionality of bluetooth at the moment.
Will check more in detail and inform you about the results. Thank you.
Regards
Schaagi
@retiredtab
I want to test your ROM , where I can download it.
At the moment I use the cdroid 10 by virsys
My CPU runs at performance mode with 1600 MHz.
bierma32 said:
At the moment I use the cdroid 10 by virsys
Click to expand...
Click to collapse
Over at the T550 thread, it seems that some people who are using crDroid 10 are reporting
1) camera not working
2) brightness not working
3) browser crash (that's you)
#1 and #2 work on my build. As for #3, if you are using the built in Jelly browser, I have noticed that if you open more than 4 windows, it crashes sometimes.
While not perfect, I found that smartcookieweb app works better than Jelly.
Releases · CookieJarApps/SmartCookieWeb
A secure, open source web browser for Android. Contribute to CookieJarApps/SmartCookieWeb development by creating an account on GitHub.
github.com
The Brave browser seems to work the most reliable. You can use Aurora store to download it from play store or try downloading brave apk somewhere.
On a daily basis, I use smartcookieweb as it has built in adblocker and suits my daily browsing needs.
@retiredtab
Both cameras works on Cdroid for me.
Yes, browsers crashes after some times, I use opera mini.
Bluetooth works for, tested sending and recive images.
GPS is not working, will try it again next time.
Magisk 21 works.
WiFi works.
Hi retiredtab,
Nice to see that anybody has try to give us an update for this fossile
Please let me knoe where can I download and test your build.
regards,
L
bierma32 said:
GPS is not working
Click to expand...
Click to collapse
No need to retest GPS. I already know what's wrong. This is the same problem I had with the T350.
The T550 build is missing the commands
Code:
# GPS
PRODUCT_COPY_FILES += \
vendor/samsung/msm8916-common/proprietary/lib/libloc_api_v02.so:$(TARGET_COPY_OUT_VENDOR)/lib/libloc_api_v02.so \
vendor/samsung/msm8916-common/proprietary/lib/libloc_ds_api.so:$(TARGET_COPY_OUT_VENDOR)/lib/libloc_ds_api.so
Now I did test the T550 build on my P550, but it looks like when I made the final image, some of my scripts or commits didn't get copied, like the above, over when I initially changed some P550 naming/parameters to T550.
Some background. I had only 1 hard drive for the P550 and T550 code. I did test bluetooth and gps on my P550 and both work.
After I tested everything, I then later split the P550 onto one hard drive and the T550 to another so I wouldn't get confused when compiling and making changes. I suspect now that I forgot to copy over my T350 script to fix gps and bluetooth onto the new T550 drive.
To fix gps without having to re-download another 440MB file,
1) Boot into TWRP 3.4.0.0.
2) Click Mount. Choose System.
3) On your computer, goto
proprietary_vendor_samsung/libloc_ds_api.so at lineage-17.1 · Galaxy-MSM8916/proprietary_vendor_samsung
proprietary_vendor_samsung. Contribute to Galaxy-MSM8916/proprietary_vendor_samsung development by creating an account on GitHub.
github.com
and
proprietary_vendor_samsung/libloc_api_v02.so at lineage-17.1 · Galaxy-MSM8916/proprietary_vendor_samsung
proprietary_vendor_samsung. Contribute to Galaxy-MSM8916/proprietary_vendor_samsung development by creating an account on GitHub.
github.com
4) Download both files above (libloc_ds_api.so and libloc_api_v02.so).
5) Goto the directory where both are saved.
6) Plug in microusb cable to tablet.
7) Then use adb to push the file using the command
Code:
$adb push libloc_api_v02.so /system/vendor/lib/libloc_api_v02.so
libloc_api_v02.so: 1 file pushed, 0 skipped. 7.6 MB/s (116316 bytes in 0.015s)
$adb push libloc_ds_api.so /system/vendor/lib/libloc_ds_api.so
libloc_ds_api.so: 1 file pushed, 0 skipped. 29.5 MB/s (26132 bytes in 0.001s)
8) Check that both files exist.
$adb shell ls -al /system/vendor/lib/libloc_api_v02.so
-rw-r--r-- 1 root root 116316 Dec 7 2020 /system/vendor/lib/libloc_api_v02.so
$adb shell ls -al /system/vendor/lib/libloc_ds_api.so
-rw-r--r-- 1 root root 26132 Dec 7 2020 /system/vendor/lib/libloc_ds_api.so
9) Reboot into system and GPS should be work now.
I'm making a new BETA image again and before I upload it, I will retest everything again on my P550. It's a bit awkard as everything is mapped backwards on the X-axis.
I'll post here when it's up.
Well it was around 1AM in the morning when I saw the gps not working post and now it's 2:13AM. I'm just waiting for the last 5 minutes of my new build, but the host server is having major problems right now.
So I'm going to sleep and will try uploading the new image tomorrow after I retest everything with the P550 running the T550 image. Everything will be mapped backwards for me on the X-axis while testing.
Dec 21 BETA build up. Androidfilehost is having major problems so I put it up on sourceforge.net. No way I could go to sleep with this hanging over my head. It's 2:30AM. Now I'm going to sleep in tomorrow.
Dec 21 build has gps fix.
Ooh i want really like to test!