fm / NextRadio on Lollipop? - Sprint Samsung Galaxy Note 3

fm / NextRadio works well on stock Sprint Kitkat Rom, but I haven't seen it working on any Lollipop Rom yet on our SM-N900p simply because those Roms are not based on stock Sprint Lolipop (will there be one anytime soon?). Right now, once running NextRadio on Lollipop, the program just thinks there is no fm hw on this phone, which we all know is not true. It must be software issue instead of hardware issue. And it must not be the modem because I'm using the same modem as in Kitkat.
I think the reason that fm is not working yet on non-stock Roms could be due to following reason(s):
1. fm hw is not switched on, and/or
2. there is dependencies missing
3. Rumors has it that Lollipop removed fm supporting module.
I'm collecting info on this topic (info only, no working solution yet).
1. Switch on the fm hw by modifying /proc/config.gz under the key CONFIG_RADIO_ADAPTERS or similar
from https://android.stackexchange.com/questions/62243/fm-radio-on-htc-one-google-play-edition:
You might be able to glean in on the kernel config script if present to determine the chipset employed by the FM Radio... hint: /proc/config.gz under the key CONFIG_RADIO_ADAPTERS or similar
More than likely, the kernel has that config.gz switched off hence cannot be found in /proc directory
2. I did a search of "fmradio" in all xml files in stock NH7 ROM and find these:
In \system\csc\feature.xml and \system\csc\SPR\system\csc\feature.xml
http://forum.xda-developers.com/showthread.php?p=34028174#post34028174
Code:
<!-- MMApp -->
<CscFeature_FMRadioRTPlus>true</CscFeature_FMRadioRTPlus>
<CscFeature_FMRadioSEASetting>false</CscFeature_FMRadioSEASetting>
In \system\etc\feature_default.xml
Code:
<!-- SEC FMRadio -->
<CscFeature_FMRadio_FrequencySpaceAs>100</CscFeature_FMRadio_FrequencySpaceAs>
<CscFeature_FMRadio_DefaultChannelAs>87.5</CscFeature_FMRadio_DefaultChannelAs>
<CscFeature_FMRadio_DisableRTPlusInfo>false</CscFeature_FMRadio_DisableRTPlusInfo>
<CscFeature_FMRadio_DeconstantAs>50</CscFeature_FMRadio_DeconstantAs>
<CscFeature_FMRadio_BandWidthAs>87500_108000</CscFeature_FMRadio_BandWidthAs>
Some mentioned that these line in /system/csc/others.xml (http://forum.xda-developers.com/showpost.php?p=46678611&postcount=29):
Code:
<CscFeature_FMRadio_FrequencySpaceAs>100</CscFeature_FMRadio_FrequencySpaceAs>
<CscFeature_FMRadio_DefaultChannelAs>87.5</CscFeature_FMRadio_DefaultChannelAs>
<CscFeature_FMRadio_DisableRTPlusInfo>TRUE</CscFeature_FMRadio_DisableRTPlusInfo>
<CscFeature_FMRadio_DeconstantAs>50</CscFeature_FMRadio_DeconstantAs>
<CscFeature_FMRadio_BandWidthAs>87500_108000</CscFeature_FMRadio_BandWidthAs>
<CscFeature_FMRadio_DisableMenuAf>TRUE</CscFeature_FMRadio_DisableMenuAf>
<CscFeature_FMRadio_DisableMenuRds>TRUE</CscFeature_FMRadio_DisableMenuRds>
3. In \system\etc\mixer_paths.xml, the keyword "fm" mentioned several times.
4. denpendencies
/system/lib/libfmradio_jni.so is the one for Samsung's stock fm apk. Not found in NH7 Rom though.
5. There is this "Spirit1, Spirit2 Real FM Radio General Thread" going on and looks promising to make fm work again on Lollipop:
http://forum.xda-developers.com/showthread.php?t=1059296

I've found there is no radio section in CM and other custom roms in the mixer_paths.xml.

Related

How to install MIUI FM Radio application in a Sense ROM?

Hello,
I love the MIUI ROM, but I can not renounce the 3D capabilities. The implementation of "FM Radio" in MIUI allows for a countdown to shutdown the application, ideal for listening the radio when you go to sleep
I downloaded the ROM to get the application "FM.apk" but installing from the file explorer has not worked.
Any suggestions?
Greetings.
That apk maybe miui framework dependant and would need to modified to work with sense. Try asking DH over in his miui thread. If it's anyone who knows it'd him.
#Root_Hack-Mod*Always\
Hello,
I found an alternative solution. I installed the application "Sleep Timer", and I can launch the FM Radio from within, setting the time that will stop the application, with different methods to do so.
Greetings.

UMI C1 - GPS not working in ported ROM

Hi everyone,
few days ago i've started reading about porting ROMs to different devices because i have free time and i'm interested in such stuff. I've successfully ported a CM12 based ROM (resurrection remix, lollipop 5.1.1.) to my MT6582 UMI C1. But the problem that i'm facing is that the GPS isn't functional. It works fine if i use WIFI assisted GPS (battery saving or high accuracy option) but when i use the device's GPS (device only option) it just won't get a fix. I've used GPS test app to check what's happening, and all 'i see' is 9-13 satellites but none is actually being locked onto. Also CM12 doesn't have com.mediatek.lbs.em (location based services) or YGPS.apk. I've tried 4-5 custom ROMs and none of them had those apps. Kitkat did have those and i was able to check the SNR of the GPS reception per satellite.
In previous ROM (kitkat 4.4.2) GPS worked very good, especially when i've installed modified gps.conf into /system/etc
I was able to get a lock within seconds.
SO...
I've ported zImage (a.k.a. kernel?) from stock boot.img to port boot.img, compiled it and done few other file replacements in port ROM to make my ROM working.
I am not a programmer or a coder. All I do is read/copy/paste/ and enjoy what I've done. I don't sell the stuff I do. It's all just for me. But I can (and know how to) use notepad++ to replace lines in ROM's files so if you know a solution please share it with me :fingers-crossed:
So far all stock ROMs for my phone (UMI C1) are missing all files in /system/lib/modules and i've read that i should replace mtk_stp_gps.ko from PORT with one that is located in STOCK. So there has to be another fix, my phone worked fine without it.
Thanks in advance and i hope we'll find a solution.
Got the same problem porting MIUI 7 / 8 to mtk 6582. Have you found a solution?

[MOD][Xposed] Make Infrared Blaster working with all 3rd party apps (on EUI)

Update: Dec 6th, 2016: published version 1.1, works now with more LeEco phones. Btw, module was renamed to "LeEco Infrared Fix".
Hi!
I've created the Xposed module "LeEco Infrared Fix" for the LePro 3 (but seems to work on other LeEco phones too) which tries to make the IR blaster (the infrared hardware) usable via the standard Android API. This means that all 3rd-party infrared apps which use the standard API should work!
The module is open-source, you can find the code here on GitHub.
For background infos and details look into this thread: [REF] How Infrared is (not) working on LePro3 - some infos for IR devs.
Restrictions:
Problably only working with EUI (will not work on plain cyanogenmod. Update: seems to work also on Cyanogenmod as long as the proprietary sysrem app "UEI Android Services SDK(LeTV)" from the device's original ROM is also installed (as system app?) in Cyanogenmod). Developed on my LePro 3 --> Please give feedback if it also works on other phones or EUI versions
The app UEI Android Services SDK(LeTV) (QuickSet SDK Service) must not be removed or disabled (this service is responsible for talking to the IR chip). Its internal package name is: com.uei.quicksetsdk.letv.
It supports only sending Infrared (no receiving, learning-mode) simply because the standard Android API has no support yet for receiving infrared. But the original LeEco remote control app should still be able to use the learning-mode.
This module overrides the standard Android Infrared API, so this means the standard Infrared API must already be present in the ROM! This the case for EUI 5.8.018S on the LePro 3 but might not be the case on other ROMs. :-/ Update: no longer necessary since version 1.1
But you can disable or remove the original Le Eco remote control app. Or you can keep it. Just as you like. It should be able to co-exist with 3rd party apps.
Reported to work with following devices / ROMs:
LeEco Le Pro 3 (LEX720) running EUI 5.8.018S (tested by myself)
LeEco Le 2 MTK Chipset running EUI 5.9.020s (according to this posting from @bearady)
LeEco Le 2 X526 running EUI 5.9.020S (according to this posting from @jhakjhuk1853 and this posting from @kedaranmol)
LeEco Le Max 2 X820 running Madsurfer's 21s EUI 5.9 Rom according to this posting from @serc
LeEco LePro 3 running CM13 (as long as the proprietary system app "UEI Android Services SDK(LeTV)" from the original EUI ROM of the same device is also installed (as system app?) in Cyanogenmod)
Please report in comments if it's also working for other versions or devices, so I can complete this list.
Changelog and older releases:
see Changelog on Github
all releases can be downloaded from release page on Github
Also:
Here be dragons.. (aka bugs)
8 days ago I had no idea how infrared works, had never used the infrared API or even used any infrared app. I just started poking around and then things escalated quickly (you can follow my story in this other thread if you have some hours to read...). Keep in mind that working with the infrared API is new for me, so there might be bugs..
If it's working or not, please give feedback.
Btw, I'm currently testing with the app RCoid free which works perfectly for me (and which I really like). I also tested with these randomly chosen apps: ZaZa Remote-Universal Remote, ASmart Remote IR and IR Universal Remote and all of them worked.
Download:
via Download section in Xposed Installer app (click on the link from your phone and the Xposed installer app should open)
releases page on Github
or download attachment of this posting
Awesome, I do not use the IR blaster but thanks for the time and work!
i have tested with lemax2 and eui 5.9.21s
is not working
but i will look at later versions, for me this is very important
thanks for your work
can we do this way principicaly for the camera too
edit edit new version 1.1 beta is running like charme
thank you androcheck
Tried on eUI 5.8.19s with Le 1s Eco. ended up with boot loop.
im testing again to ensure the bootloop not bcos of this module... unfortunately couldn't get a logcat
@androcheck can you post this in xposed modules repo that would be useful.
reversegear said:
Tried on eUI 5.8.19s with Le 1s Eco. ended up with boot loop.
im testing again to ensure the bootloop not bcos of this module... unfortunately couldn't get a logcat
@androcheck can you post this in xposed modules repo that would be useful.
Click to expand...
Click to collapse
Hi, thanks for the feedback. Good idea, I will it submit to the Xposed repo. :good:
Yes, it's very likely that this might not work well on other devices (or even other EUI versions) as the tricks needed to get this working are very specific targeted. But in the other side (under the assumption that the used IR Blaster and QuickSet SDK is the same than on LePro 3) it might only require some small changes to get it working.
The logfiles from Xposed and maybe a Logcat (from the start of boot) would be extremly useful to see what's going wrong:
Boot into TWRP recovery and copy the Xposed logs to your computer:
Code:
adb pull /data/data/de.robv.android.xposed.installer/log/error.log
adb pull /data/data/de.robv.android.xposed.installer/log/error.log.old
Then boot normally start logcat from the beginning of boot (start it even before you see the bootanimation):
Code:
adb logcat -v time '*:V' > logcat_lepro3_boottime.txt
[edit]
If you experience a bootloop (caused by my module), simply boot into TWRP and delete my app from there: Just navigate to the directory "/data/app", there you should find a subdirectotry named "at.zweng.xposed.debug.infrared-1" (maybe the digit at the end is different) and just delete this whole directory.
[/edit]
Done. Published it into Xposed repo. Just search for "LePro 3 Infrared Fix".
Also I would like to get feedback from LePro3 users if it's working on the newer EUI versions for the american version. (And please include logs if it's not working.)
And when we finally have a working cyanogenmod device tree (so that we can build it ourselves) I will happily support developers to get this working for cyanogenmod, too so that infrared will work there out-of-the-box without the need for an Xposed module. (After searching the forums here on XDA I guess this would make the LePro3 being the first device with a UniversalElectronics IR chip where infrared will work on cyanogenmod with all 3rd party apps. )
serc said:
i have tested with lemax2 and eui 5.9.21s
is not working
but i will look at later versions, for me this is very important
thanks for your work
can we do this way principicaly for the camera too
Click to expand...
Click to collapse
One thought: could you test with an app like z-device test if the phone advertises having infrared capabilities to apps?
Because this is the case with the LePro 3. It has the Infrared API included (so all infrared apps install and work fine), but just didn't do anything.
My module only works if the Infrared API is already present in first place.
I did not understand what you meant about the camera.
androcheck said:
One thought: could you test with an app like z-device test if the phone advertises having infrared capabilities to apps?
Because this is the case with the LePro 3. It has the Infrared API included (so all infrared apps install and work fine), but just didn't do anything.
My module only works if the Infrared API is already present in first place.
I did not understand what you meant about the camera.
Click to expand...
Click to collapse
May be he meant to say about working camera 2 API
Z-device test says no IR capabilities
androcheck said:
One thought: could you test with an app like z-device test if the phone advertises having infrared capabilities to apps?
Because this is the case with the LePro 3. It has the Infrared API included (so all infrared apps install and work fine), but just didn't do anything.
My module only works if the Infrared API is already present in first place.
I did not understand what you meant about the camera.
Click to expand...
Click to collapse
Z-device test says no IR capabilities in Le 2 (X526) Indian Version. So i guess we cant use your xposed module? Is there any way to add the Infrared API with rooted phone? I could test it, if you have any theories...
OMG...you're a life saver and a genius.I can confirm it worked on Leeco Le 2 X620 eui 5.9.020s mtk chipset. I've tested with Anymote,Rcoid(also suggested by you),Peel Smart and Zaza Remote. Thank you very much...respect for your work
Which eui version?
One of the user said worked on mtk 20s we can also try on Chinese 20s
kedaranmol said:
Z-device test says no IR capabilities in Le 2 (X526) Indian Version. So i guess we cant use your xposed module? Is there any way to add the Infrared API with rooted phone? I could test it, if you have any theories...
Click to expand...
Click to collapse
---------- Post added at 10:42 AM ---------- Previous post was at 10:41 AM ----------
@androcheck can you help in making it for le2 Indian x526
I can help for files etc
jhakjhuk1853 said:
One of the user said worked on mtk 20s we can also try on Chinese 20s
---------- Post added at 10:42 AM ---------- Previous post was at 10:41 AM ----------
@androcheck can you help in making it for le2 Indian x526
I can help for files etc
Click to expand...
Click to collapse
But the 20s rom is for mtk chipset? Or are you referring to 20s ported from Chinese 5.9.20s?
Ported
Ported 20s
kedaranmol said:
But the 20s rom is for mtk chipset? Or are you referring to 20s ported from Chinese 5.9.20s?
Click to expand...
Click to collapse
androcheck said:
I did not understand what you meant about the camera.
Click to expand...
Click to collapse
reversegear said:
May be he meant to say about working camera 2 API
Click to expand...
Click to collapse
Hi Androcheck, Reversegear with Camera I mean this ROM
http://forum.xda-developers.com/le-max-2/development/unofficial-cyanogenmod-14-1-t3498764
here is Camera not running, i thinked your way can Help here perhaps
kedaranmol said:
Z-device test says no IR capabilities in Le 2 (X526) Indian Version. So i guess we cant use your xposed module? Is there any way to add the Infrared API with rooted phone? I could test it, if you have any theories...
Click to expand...
Click to collapse
jhakjhuk1853 said:
@androcheck can you help in making it for le2 Indian x526
I can help for files etc
Click to expand...
Click to collapse
I am currently playing around and testing.. I am trying to hook also all the relevant PackageManager methods, so that for an app everything looks like if there is a standard infrared HAL implementation available. Not sure, if this would work for the X526.
If the IR blaster hardware or the QuickSet SDK is only a little bit different, then it might not work. So this is just a try.. Don't get your hopes too high..
serc said:
Hi Androcheck, Reversegear with Camera I mean this ROM
http://forum.xda-developers.com/le-max-2/development/unofficial-cyanogenmod-14-1-t3498764
here is Camera not running, i thinked your way can Help here perhaps
Click to expand...
Click to collapse
Hi! I think there is a misunderstanding what Xposed is and what it's used for. Xposed is a (not so easy) way to "hook" (in other words: modify) existing code during runtime.
It's complicated to work with Xposed and it should only be the last resort if you have no other ways to do it. If you have the orginal source code of some peace of software it's MUCH easier to just work with the plain source code and fix the bugs directly there before you build it (and not take the unnecessarily complicated road with Xposed).
In Cyanogenmod you have all the source code (besides low-level drivers, and there Xposed also cannot be used), so devs should try to fix the errors in the source code, not with Xposed. Also, I have never worked with Camera API (and I can only assume that it's way more complicated than Infrared), so I'm afraid I cannot really help here.
Hi, @serc, @reversegear, @kedaranmol, @jhakjhuk1853!
I've extended the module so that it now also fakes the availability of standard Android Infrared API. So now all Infrared apps should think infrared is available. I attached it to this posting below. Update: removed attachement, use final version 1.1 instead from first post (or from Xposed installer app)
Maybe you can try it this beta version on your devices. No guarantee that it will work (as I don't have the devices for testing). If it seems to work please verify with a digital camera or another's phone camera that the infrared LED actually is really emitting light (cameras can see infrared light, which humans cannot see).
--> also please report your exact phone model plus the version of the ROM you're running!
If it's not working I would need a logcat output (started directly at boot) as well as the Xposed logfile (found in the Xposed installer app).
Code:
adb logcat -v time '*:V' >> logcat_debug_infrared.txt
Have fun!
[EDIT]
Removed BETA attachement as final version 1.1 is now released in Xposed installer app (and in first post)
[/EDIT]
update : le2 x526 EUI 20s version
after installing module phone booted succesfuly
installing peel smart and report back when home will check on TV
will check and report in 10min
thank you
androcheck said:
Hi, @serc, @reversegear, @kedaranmol, @jhakjhuk1853!
I've extended the module so that it now also fakes the availability of standard Android Infrared API. So now all Infrared apps should think infrared is available. I attached it to this posting below.
Maybe you can try it this beta version on your devices. No guarantee that it will work (as I don't have the devices for testing). If it seems to work please verify with a digital camera or another's phone camera that the infrared LED actually is really emitting light (cameras can see infrared light, which humans cannot see).
--> also please report your exact phone model plus the version of the ROM you're running!
If it's not working I would need a logcat output (started directly at boot) as well as the Xposed logfile (found in the Xposed installer app).
Code:
adb logcat -v time '*:V' >> logcat_debug_infrared.txt
Have fun!
Click to expand...
Click to collapse
---------- Post added at 03:23 PM ---------- Previous post was at 02:47 PM ----------
Guys this really worked I am using peel smart on my le2
nothing can be better than this thanks
androcheck said:
Hi, @serc, @reversegear, @kedaranmol, @jhakjhuk1853!
I've extended the module so that it now also fakes the availability of standard Android Infrared API. So now all Infrared apps should think infrared is available. I attached it to this posting below.
Maybe you can try it this beta version on your devices. No guarantee that it will work (as I don't have the devices for testing). If it seems to work please verify with a digital camera or another's phone camera that the infrared LED actually is really emitting light (cameras can see infrared light, which humans cannot see).
--> also please report your exact phone model plus the version of the ROM you're running!
If it's not working I would need a logcat output (started directly at boot) as well as the Xposed logfile (found in the Xposed installer app).
Have fun!
Click to expand...
Click to collapse
I have tested it and I can confirm that this xposed module now works on Le 2 X526 (Indian version with Snapdragon 652). I can see IR signals from another phone's camera using the Anymote Universal Remote and Rcoid. But strangely SURE Universal Remote for TV didn't work for me. I will test with other apps later when I get home. I am yet to test if this works with my TV and other devices. Will update when I do this.
Hi Androcheck compliment you are a Genius !!!
ver. 1.1 beta
my Phone LeEco LeMax2 x820 with Madsurfer's 21s EUI 5.9 Rom, from lemax2 forum xda
rCoid remote is running wonderfull, for me one of the important things at this phone.
Thank You very much , i am now very very happy
Hi, @jhakjhuk1853, @kedaranmol and @serc!
Thanks for reporting back! I will clean up the code (remove a little bit of the debug logging I've included for the case if it wouldn't work), and will make a new clean 1.1 release (and also release the source again).
I'm glad you like it! At the beginning I only wanted to solve this problem just for me personally, but I am happy that my solution now even is working for several devices.
(And if you like it really much and feel like buying me a coffee, there is also a donation link at my profile page.. )
P.S.: The app SURE Universal Remote for TV also doesn't work for me. It seems that they are not only using the standard API to query for infrared capabilities. Hmm.. it looks like they include several other proprietary IR implementations to make it work on as much devices as possible. It seems there is also a version of QuickSet SDK included but it's a different one than the one we see in our phones (I guess it's for LG phones). I'm not sure what exactly is causing the problem.

[ROM][UNOFFICIAL][9.0.0] LineageOS 16.0 [BETA][2.01.2020]

Code:
/*
* Your (probably expired) 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.
*/
IMPORTANT INFORMATION
Hi all,
This is an unofficial Pie build for the Galaxy Note 2 (t0lte) based on LineageOS 16.0.
Most of the ROM features are working, but the overall state might be not fully stable or not suitable for a daily use.
This work is heavily based on works of PoisonNinja, Option58 (thanks for device tree, kernel and device patches for LOS 14.1).
A full credit for Pie bringup goes to rINanDO (thanks for device tree, kernel and device patches for LOS 16.0).
What is working:
Boots
Audio (playback && recording)
Bluetooth
Graphics
Camera
Sensors
RIL (SMS, mobile data, calls)
Wifi
USB
Video playback (HW/SW)
What is not working:
GPS
Compass / Magnetic Sensor
SIM might be not detected / Data might be not available upon boot (reboot to fix).
LTE is not currently supported
Gapps installation can cause boot issues (?) - not tested
Supported variants:
fully tested on t0lteatt (SGH-I317, AT&T variant)
SGH-I317M
SGH-T889
Should also work for the following variants (not tested as of now):
GT-N7105/N7105T
SGH-T889V
SHV-E250S/E250K/E250L
SC-02E (SGH-N025)
Reporting bugs
When reporting reboots, please produce log below as follows
(using adb or terminal)
Code:
su
cat /proc/last_kmsg > /sdcard/last_kmsg.txt
and attach in this thread.
If reporting another issues
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
A rough timestamp of when the issue occurred is also useful.
Click to expand...
Click to collapse
Download:
ROM
TWRP
Root
Installation:
Make sure you are using the latest TWRP version.
Download the latest build and copy it to the phone
Factory reset in TWRP (Very important! Do not skip)
Flash LineageOS 16.0
Optional: Flash root package
Reboot
Be patient. The first boot will take between 5 - 15 minutes.
Set up everything and reboot again to get radio working
Credits:
rINanDO
forkbomb444
Option58
PoisonNinja
AdrianDC
A$teroid
Lord Boeffla
LineageOS team
Nameless ROM
I really do hope I didn't miss here anyone who deserves credits for their amazing works
If you like my work and want to thank me, feel free to buy a coffee
Source code: LOS 16.0
XDA:DevDB Information
LineageOS 16.0, ROM for the Samsung Galaxy Note II
Contributors
ChronoMonochrome, rINanDO, Option58, PoisonNinja, LineageOS team
Source Code: https://github.com/CustomROMs/android_local_manifests_i9300/tree/lineage-16.0
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.0.x
ROM Firmware Required: TWRP 3.2.x or newer
Version Information
Status: Testing
Created 2020-01-02
Last Updated 2020-01-02
Reserved
Reserved
Congrats on getting this working! :victory:
This build work for me cool thé ril work il so happy to see pie on this device thank
Hi,
thanks for your hardwork on this. Unfortunately doesnt work on SHV E250:
This package is for device: tolte, t0ltexx, gt-7105, t0lteatt, SGH-I317M...... this device is .
updater process ended with Error:7
Working on N7105 blazing fast. haven't tried with gapps.
sosodef_3000 said:
Hi,
thanks for your hardwork on this. Unfortunately doesnt work on SHV E250:
This package is for device: tolte, t0ltexx, gt-7105, t0lteatt, SGH-I317M...... this device is .
updater process ended with Error:7
Click to expand...
Click to collapse
I had a similar error with my t0lte. I was able to fix my error by installing the latest TWRP
qspitzer said:
I had a similar error with my t0lte. I was able to fix my error by installing the latest TWRP
Click to expand...
Click to collapse
what version of note 2 do you have?
sosodef_3000 said:
what version of note 2 do you have?
Click to expand...
Click to collapse
I have the AT&T (i317/t0lteatt) version
i test this rom on my Samsung Note 2 SHV-e250k and it was good but sometimes buggy
You can activate the LTE option on *#*#4636#*#* but sometimes the "No Internet" appears
Pico is the best to install gapps because when you use other it was not working because of "System is full" message
sometimes the facebook, messenger and youtube crash and i encounter the Couldn't sign in on Google
again it's a good rom and need some several fix tho, it was good already just fix the Google Account issue, the partition of Sys on the memory and some app crashes.
Thanks for your work on this ROM ChronoMonochrome!
I tested out your ROM on my Verizon Galaxy Note II (t0ltevzw), another Note II LTE variant. I had to modify the updater-script to get this ROM to flash successfully on my device. Everything seems to be working (sound, wifi, BT), except for RIL. I seem to be seeing a dialog on launch saying that the SIM is voice only.
I'm guessing this is due to some specific differences with t0ltevzw compared to other t0lte devices.
Let me know if there's anything I can do to help with testing.
Sent from my GM1917 using Tapatalk
CKTurbo128 said:
Thanks for your work on this ROM ChronoMonochrome!
I tested out your ROM on my Verizon Galaxy Note II (t0ltevzw), another Note II LTE variant. I had to modify the updater-script to get this ROM to flash successfully on my device. Everything seems to be working (sound, wifi, BT), except for RIL. I seem to be seeing a dialog on launch saying that the SIM is voice only.
I'm guessing this is due to some specific differences with t0ltevzw compared to other t0lte devices.
Let me know if there's anything I can do to help with testing.
Sent from my GM1917 using Tapatalk
Click to expand...
Click to collapse
Hi,
this variant of N7105 seems to be unsupported even by the official LineageOS sources.
You can try extract file libsec-ril.so from the stock and try use it (put the file in /system/lib).
If that works, it should be easy to add support for this phone variant as well.
ChronoMonochrome said:
Hi,
this variant of N7105 seems to be unsupported even by the official LineageOS sources.
You can try extract file libsec-ril.so from the stock and try use it (put the file in /system/lib).
If that works, it should be easy to add support for this phone variant as well.
Click to expand...
Click to collapse
Thanks @ChronoMonochrome. I've added the libsec-ril.so from the latest t0ltevzw KK stock ROM.
After doing so, the SIM card dialog warnings have gone away and the phone number is now detected on the Verizon SIM card.
Still no radio signal (at least for Verizon), but probably related to another issue.
t0ltevzw 4.4.2 KitKat Stock libsec-ril.so:
https://gitlab.e.foundation/e/devic...0ltecdma/proprietary/system/lib/libsec-ril.so
Sent from my GM1917 using Tapatalk
View attachment 4923377
CKTurbo128 said:
Thanks @ChronoMonochrome. I've added the libsec-ril.so from the latest t0ltevzw KK stock ROM.
After doing so, the SIM card dialog warnings have gone away and the phone number is now detected on the Verizon SIM card.
Still no radio signal (at least for Verizon), but probably related to another issue.
t0ltevzw 4.4.2 KitKat Stock libsec-ril.so:
https://gitlab.e.foundation/e/devic...0ltecdma/proprietary/system/lib/libsec-ril.so
Sent from my GM1917 using Tapatalk
View attachment 4923377
Click to expand...
Click to collapse
I didn't know it's a CDMA device. CDMA is not supported by the ROM, however the following can make it work.
Edit /system/build.prop as following:
Code:
rild.libpath=/system/lib/libsec-ril.so
(change rild.libpath=/system/lib/libsecril-shim.so to rild.libpath=/system/lib/libsec-ril.so)
This is very promising ROM even though the basic issue I can say it is constant need to restarting to use data and even the music app starting at any time to is also a problem. Apart from that, this is a dream come true
ChronoMonochrome said:
I didn't know it's a CDMA device. CDMA is not supported by the ROM, however the following can make it work.
Edit /system/build.prop as following:
Code:
rild.libpath=/system/lib/libsec-ril.so
(change rild.libpath=/system/lib/libsecril-shim.so to rild.libpath=/system/lib/libsec-ril.so)
Click to expand...
Click to collapse
Thanks for the suggestion! Yep, the Verizon Galaxy Note II is CDMA. I tried making the build.prop settings and then added the Verizon APN, but still no signal found.
Not a big deal, since I'm just using it on Wi-Fi at the moment.
As for Gapps issues, I have the Gapps pico package installed. However, I noticed that if you install a certain Google app (not sure, could be Google, Google Assistant, Gmail, etc), it causes bootloops to occur. I've had to factory reset a few times. Trying to figure which Google app causes this to occur.
Sent from my GM1917 using Tapatalk
shv e250k
KirikoSen said:
i test this rom on my Samsung Note 2 SHV-e250k and it was good but sometimes buggy
You can activate the LTE option on *#*#4636#*#* but sometimes the "No Internet" appears
Pico is the best to install gapps because when you use other it was not working because of "System is full" message
sometimes the facebook, messenger and youtube crash and i encounter the Couldn't sign in on Google
again it's a good rom and need some several fix tho, it was good already just fix the Google Account issue, the partition of Sys on the memory and some app crashes.
Click to expand...
Click to collapse
Hi thanks for this.
Did you change the updater script to get it to work? Because mine it justs stops trying to install and says this is for phones....etc
Also what bands (wcmda/LTe) did you select for the *#*#4636#*#* ? I tried this on my oreo 8.1 but this didnt find the IMEI or the sim
(Also it seems you tested this in the past...what new rom did you move on to?)
I've been investigating further into why this ROM starts bootlooping or experiences the display to blackout, particularly with t0ltevzw. One suspicious error seems to be with com.google.android.carriersetup:
2020-01-12 09:38:46.929 18771-18771/system_process E/PackageManager: updateAllSharedLibrariesLPw failed: Package com.google.android.carriersetup requires unavailable shared library com.verizon.provider; failing!
2020-01-12 09:38:49.606 18771-18879/system_process E/StorageManagerService: Failed to read field SystemLocale
android.os.ServiceSpecificException: Failed to read field SystemLocale (code 2)
at android.os.Parcel.createException(Parcel.java:1964)
at android.os.Parcel.readException(Parcel.java:1918)
at android.os.Parcel.readException(Parcel.java:1868)
at android.os.IVold$Stub$Proxy.fdeGetField(IVold.java:1112)
at com.android.server.StorageManagerService.getField(StorageManagerService.java:2427)
at com.android.server.StorageManagerService.copyLocaleFromMountService(StorageManagerService.java:984)
at com.android.server.StorageManagerService.handleDaemonConnected(StorageManagerService.java:977)
at com.android.server.StorageManagerService.access$900(StorageManagerService.java:173)
at com.android.server.StorageManagerService$StorageManagerServiceHandler.handleMessage(StorageManagerService.java:574)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loop(Looper.java:193)
at android.os.HandlerThread.run(HandlerThread.java:65)
Click to expand...
Click to collapse
logcat: View attachment 4925079
These symptoms seems to start occurring if you install any of these `com.google.*` apps:
* Google Wellbeing
* Google Calendar
* Gmail
* Google Docs
* Google Slides
Finally got this to load on SHV-E250K but unfortunately internet doesnt work.
If Chronomonochrome can kindly fix that would be great.
Tried to reflash the old modem from 4.4.2 but that didnt help.
tried murata fix and flashed together still didnt work
Have gone back to:
lineage-14.1-20171208-nightly-t0ltekor-signed with wifi and internet working.
Maybe someone can take the wifi files from there and plug into lineage 16.0 that would be great

Joyuse FM-Radio - no sound?

Hi there!
I have a Xiaomi Note 9 Pro = Joyuse device, with unlocked bootloader.
I've tried those two ROMs:
* Arrow-v12.1-miatoll-OFFICIAL-20220505-GAPPS (=Android 12)
* lineage-18.1-20220506-nightly-miatoll-signed (=Android 11)
Both include an FM-Radio app, with both I can scan and find channels, and get those RDS texts displayed for the stations that send them, but I can't hear any audio. I've also tried the recording feature: The resulting audio files contain only silence.
I also have a Xiaomi Note 9S = Curtana device, on this the FM-Radio works without a problem with all ROMs I've tried that included an app for it.
Does anybody else have a Joyuse device for which the FM Radio is working? Does it work with MIUI / Stock ROM?
Thank you!
Yes,
using same ROM (lineage-18.1-20220506-nightly-miatoll-signed) with base MIUI ROM miui_JOYEUSEEEAGlobal_V12.5.8.0.RJZEUXM_0d0abb3576_11.0.
FM Radio is working as expected. Can't say for the MIUI ROm since i haven't used it.
oh, so maybe the issue is that the last original xiaomi MIUI ROM that was installed on my Joyuse was too old. I didn't know that was required for this device..?
So I've tried flashing fw_joyeuse_miui_JOYEUSEEEAGlobal_V12.5.8.0.RJZEUXM_0d0abb3576_11.0.zip from https://xiaomifirmwareupdater.com/firmware/joyeuse/
That didn't change the FM-Radio, still no sound, still scanning + RDS Texts working.
@MiATOr Can you confirm the path you went to get the FM Radio working on your Joyeuse device?
You said you used "base MIUI ROM" miui_JOYEUSEEEAGlobal_V12.5.8.0.RJZEUXM_0d0abb3576_11.0.
Did you flash the fastboot or recovery version of this?
https://xiaomifirmwareupdater.com/miui/joyeuse/stable/V12.5.8.0.RJZEUXM/
Not sure if this makes any difference.

Categories

Resources