Hi guys, first of all, thanks for you hard work.
I'd like to use you ROM, I'm on LG G2 and LG G3 (it's available for both the devices luckily), but I use the CellMapper application a lot (https://play.google.com/store/apps/details?id=cellmapper.net.cellmapper&hl=it), and it requires the getAllCellInfo method in TelephonyManager to work. On stock ROMs and until Cyanogenmod 13 this method was perfectly implemented and working, now looks like the number of argument is wrong, or something like that.
Here's a debug log from CellMapper: as you can see, the getAllCellInfo method returns a null parameter: https://drive.google.com/open?id=0Bya36Q0flNdBc1RETVdUbnNnSUFFWUVSNC1zLWxqX3F2T2xv
Here's a debug log from the D855 with Cyanogen 13: https://drive.google.com/file/d/0Bya36Q0flNdBTVZIWjVVTm85eDQ/view
Could you please fix this? All CellMapper users who were forced to stay on CM13 or stock would be so glad!!
Thanks
Unfortunately, I share the same experience with my G900F. Cellmapper reads next to nothing.
Would be great if that could be fixed! Is there anything planned regarding this issue?
Nothing new?
@mrk2006 Have you found a solution now?
FTTX said:
Nothing new?
@mrk2006 Have you found a solution now?
Click to expand...
Click to collapse
Hmm I've installed lineageOS 14.1 on my moto g 4G (XT1039), tried on 4G (with root reading on CellMapper) and works!! 3G dbm are still wrong unfortunately, but we must blame the RIL then.. I'll have ti look further at that method on the logcat
Inviato dal mio ONEPLUS A3003 utilizzando Tapatalk
I
That must be new, I tried it again two months ago on my G900F and it didn't work. I will try to test if it works now soon.
Tested it, unfortunately nothing changed.
LineageOS 14.1 for Samsung Galaxy S5 G900F started working again with CellMapper a few weeks ago, including correct band/frequency reading.
Related
You may be wondering why these devices haven't received Lollipop yet. The issue is, yet again, the MT8389 processor, which is based off of the MT6589.
I.nfraR.ed posted yesterday on the main CyanogenMod on MTK devices thread:
I.nfraR.ed said:
Do you see anyone working on CM for 6589? Most of the people moved to other chipsets.
Maybe chrmhoffmann and DerTeufel are still working on this, but I don't know anyone else who has not moved to newer device.
I have moved to Redmi Note 2.
For lollipop there's no mt6589 source and although it might be possible, it would be enormous amount of work. I don't have so much free time and have a full-time job after all.
I can't leave my regular job just to work on side projects.
So, no...unless someone else is on to development for Lenovo A820/A830, then don't expect fully working CM or ROMs based on Android 5+.
If for some reason I leave my regular job and have some "free" months, then I will be able to work on this project, because I still have my A820 with me. Not likely to happen.
My KK kernel is public, so anyone can continue from where I left.
Click to expand...
Click to collapse
Development support for the MT6589 has been (mostly) lost, and consequently, so has support for the MT8389. This means that, until a compatible kernel for 5.x.x appears, the likelihood of both of the devices being upgraded to CM12 or 5.x.x is very low.
That doesn't mean it's not possible, however; simply unlikely.
According to the specs the A3000 has a MT8125. Is support for this also gone?
jayvl said:
According to the specs the A3000 has a MT8125. Is support for this also gone?
Click to expand...
Click to collapse
Yes, I'm afraid this is the Wi-Fi only version of the MT8389.
I was on it..but moved to another..not at all able to boot it up..now there is a hope because of 3.4.67 kernel..again working on it???
CM12+ for A3000-H
Looking forward to CM12+ on our beloved A3000-H:highfive:
Hi guys, I have just finished doing my A3300 with Cyan's 5.1.1, all is working except for camera
Am I just missing it, or is there no root or recovery ability for the 915A?
Marshmallow 6.0.1 ****ed mine up when it got pushed down, and Samsung's backup software (all 3 of them) failed to capture my apps and settings properly. Really wish I could've had a better backup ability.
Does or has anyone checked to see if the update to MM 6.0.1 has unlocked the bootloader on the SM-N915A like the Verizon variant?
How does one check?
Att have not released any M updates.
Mine updated to 6.0.1 the same day I bought it . Several small updates happened first. 5.0.1 to 5.1.1 then a small one, and finally 6.0.1. Since I had just bought it, resetting was a simple thought. But so far, no problems, I bought a PowerBear to make it last longer. :fingers-crossed:
Mine had a lot of issues after being updated. MMS didn't work at all. SMS worked sporadically, but would sometimes delete whole threads. Couldn't get a signal in many spots. Google Play Services wouldn't run and couldn't be fixed. Tried a cache-wipe and every other non-destructive method, but nothing worked. Ended up having to factory-reset, and since then the phone works as it should, but none of the backup methods captured key settings. Basically all it did was save contacts and APK's. Lost my 2-factor keys and everything.
I am with you! Since the update to MM, phone has been very laggy/unresponsive. Lock screen lights up for no reason sporadically and I have LOTS of dropped calls/deadspots. VERY irritating! I wish this release would have been tested a bit more before it was OTA pushed out
Hey all! Good news! A 9-year-old bug called the "Dirty Cow" exploit still exists in the Linux/Android kernel can easily grant root on any Android phone!!! See the video below.
http://www.xda-developers.com/9-yea...-dirty-cow-can-root-every-version-of-android/
So there's another bug to exploit for root and even possibly unlocking the bootloader! The bug has been fixed recently in Linux but hasn't been rolled into Android yet.
Could someone make this Windows compatible? http://androiding.how/dirty-cow-root-android/
JEANRIVERA said:
Hey all! Good news! A 9-year-old bug called the "Dirty Cow" exploit still exists in the Linux/Android kernel can easily grant root on any Android phone!!! See the video below.
http://www.xda-developers.com/9-yea...-dirty-cow-can-root-every-version-of-android/
So there's another bug to exploit for root and even possibly unlocking the bootloader! The bug has been fixed recently in Linux but hasn't been rolled into Android yet.
Click to expand...
Click to collapse
Have you tried or someone. I'm already installing Linux into my computer.
juanfe1a said:
Have you tried or someone. I'm already installing Linux into my computer.
Click to expand...
Click to collapse
did you end up doing it?
Who else could get the root on sm-n915a ??? I also have problems with the transition from 5.1.1 to 4.4.4. (Kitkat). If anyone can help write please how to do this ??
I would also like to know if I am from russia and I need a Russian language that is not available on samsung galaxy note edge n915a. Is it possible to add it like that ?? Sorry for my bad english (googl translate)). Thank you. I am hope for your help
pleasseee i need debrick image for at&t not egde (SM-N915A)
winstonakime said:
pleasseee i need debrick image for at&t not egde (SM-N915A)
Click to expand...
Click to collapse
https://forum.xda-developers.com/note-edge/general/stock-att-note-edge-5-1-1-t3241314
You may need to know your build number tho
Just to keep this alive it is now November 2017 any news?
Dr.Lost said:
Just to keep this alive it is now November 2017 any news?
Click to expand...
Click to collapse
I wish...
Anything new?
Trainwr3ck was trying to build RR Nougat for HTC One m9, everything was perfect but there is no signal (as in you don't receive data and calls). Something is very broken with the interface library that's available and it's beyond trainwr3ck and my knowledge of android.
Can someone more familiar with android help us out?
(Only trainwr3ck has logs (I think) so you'll have to wait for him)
Thanks :good:
NDR_man said:
Trainwr3ck was trying to build RR Nougat for HTC One m9, everything was perfect but there is no signal (as in you don't receive data and calls). Something is very broken with the interface library that's available and it's beyond trainwr3ck and my knowledge of android.
Can someone more familiar with android help us out?
(Only trainwr3ck has logs (I think) so you'll have to wait for him)
Thanks :good:
Click to expand...
Click to collapse
:fingers-crossed:
Hope someone will jump in and help u guys...
I am not an Android expert as well, but can you provide me with a build.prop? I just want to check something, I had that Problem with an unofficial CM13 and the reason were some missing build.prop values. Maybe it's that easy as well
Adromir said:
I am not an Android expert as well, but can you provide me with a build.prop? I just want to check something, I had that Problem with an unofficial CM13 and the reason were some missing build.prop values. Maybe it's that easy as well
Click to expand...
Click to collapse
Thanks for your input, unfortunately only trainwr3ck has that stuff, I haven't tested the ROM on my phone so you'll have to wait for him to come online, I'll get it to you as soon as possible.
Hopefully it is that easy, maybe android 7.1 is just a couple of hours away...
Thanks
NDR_man said:
Thanks for your input, unfortunately only trainwr3ck has that stuff, I haven't tested the ROM on my phone so you'll have to wait for him to come online, I'll get it to you as soon as possible.
Hopefully it is that easy, maybe android 7.1 is just a couple of hours away...
Thanks
Click to expand...
Click to collapse
That would be great,if u guys need anything feel free to contact me for any kind of testing... Still :fingers-crossed:
Sorry I'm not an expert but if you
Add the Kernel Mono revisited?
It fix in many devices in RR 5.7.4 with the signal
Sent from my HTC One M9 using XDA-Developers mobile app
I contacted a recognised slim ROM dev and he hasn't figured it out yet either, I told them to try out what you guys said though
Well for my unofficial build I found out that these values weren't added: https://github.com/CyanogenMod/android_device_htc_himaul/blob/cm-12.1/system.prop although they exist in the device tree. After I added them myself, my build was able to receive signal
Adromir said:
Well for my unofficial build I found out that these values weren't added: https://github.com/CyanogenMod/android_device_htc_himaul/blob/cm-12.1/system.prop although they exist in the device tree. After I added them myself, my build was able to receive signal
Click to expand...
Click to collapse
Can we except your test build? Or even pm me
Wysłane z mojego HTC One M9 przy użyciu Tapatalka
Oh sorry for being not clear. It was for an older cm13 built, where i had something similiar happening. Not switched my build tree to cm 14.1 yet..
Adromir said:
Well for my unofficial build I found out that these values weren't added: https://github.com/CyanogenMod/android_device_htc_himaul/blob/cm-12.1/system.prop although they exist in the device tree. After I added them myself, my build was able to receive signal
Click to expand...
Click to collapse
I forwarded this to Trainwr3ck.
I so hope this works, if nothing works then we might need to wait for an official ROM from HTC to come out for the M9 (that isn't too far away so it's not all bad)
Thanks :good:
Not Beamed in by telepathy
Update: it's not just the M9 that had this problem, the m8 team had the same problem and I've asked them how they did it
even i could help u guys but only if i get logs to work with and see whats wrong
Tanuj97 said:
even i could help u guys but only if i get logs to work with and see whats wrong
Click to expand...
Click to collapse
I tried getting the logs but the link to the RIM isn't working any more so I can't download it, it'd be nice if someone could upload it again
This is a pointless thread without work on Cyanogenmod's device tree for the M9, hope we see that soon but until that happens there is no need to talk about nougat for the M9.
Trainwr3ck said:
This is a pointless thread without work on Cyanogenmod's device tree for the M9, hope we see that soon but until that happens there is no need to talk about nougat for the M9.
Click to expand...
Click to collapse
Maybe we can make it work, when HTC is rolling out the official Nougat update an grab a precompiled version of the ril libraries, that might work
Sorry double post
Adromir said:
Maybe we can make it work, when HTC is rolling out the official Nougat update an grab a precompiled version of the ril libraries, that might work
Click to expand...
Click to collapse
It would be a much better starting point than the non working MM ril, we can only hope that it comes out soon.
HTC just announced Nougat rolling out in the USA for the unlocked M9 in the very near future.. Lets see if we can get this working..
Adromir said:
HTC just announced Nougat rolling out in the USA for the unlocked M9 in the very near future.. Lets see if we can get this working..
Click to expand...
Click to collapse
I don't think they said America, they only said tonight for international
Hi Lineage,
Do you all know when will this be coming out for Samsung Galaxy Note 3 SM-N9005?
Is there any tentative date?
Thank you
Brick1235
Brick1235 said:
Hi Lineage,
Do you all know when will this be coming out for Samsung Galaxy Note 3 SM-N9005?
Is there any tentative date?
Thank you
Brick1235
Click to expand...
Click to collapse
Use twrp hlte and install a lineageos hlte zip
Sent from my SM-N9005 using Tapatalk
albertfuller said:
Use twrp hlte and install a lineageos hlte zip
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
First of all THANK YOU VERY MUCH for replying my thread.
Where do you download this build in the official Lineage OS website? The only one i saw for Samsung Galaxy Note 3 is the Builds for ha3g in the official Lineage OS website.
Other then official sites i found only unofficial downloads links below ( I am using this one now and there is several big bugs ) :
http://www.cyanogenmods.org/forums/topic/galaxy-note-3-lineage-14-1-nougat-7-1-rom/
Brick1235 said:
First of all THANK YOU VERY MUCH for replying my thread.
Where do you download this build in the official Lineage OS website? The only one i saw for Samsung Galaxy Note 3 is the Builds for ha3g in the official Lineage OS website.
Other then official sites i found only unofficial downloads links below ( I am using this one now and there is several big bugs ) :
http://www.cyanogenmods.org/forums/topic/galaxy-note-3-lineage-14-1-nougat-7-1-rom/
Click to expand...
Click to collapse
There is no official LineageOS hlte build yet. An unofficial hlte forum is https://forum.xda-developers.com/showthread.php?t=3459973
I use this website to get the zip file:https://androidfilehost.com/?w=files&flid=110928&sort_by=date&sort_dir=DESC
Good Luck
Sent from my SM-N9005 using Tapatalk
any news for the official release yet ?
Mr Galaxy said:
any news for the official release yet ?
Click to expand...
Click to collapse
NOTE 3 LTE version is out already!
https://wiki.lineageos.org/devices/hlte
I have sm-n9005 on linage 14.1-20170713-unoffical-hlte.
Since I installed this I have no mobile phone data, but do have mobile calls and wifi data.
Any idea what to do?
Im just about to buy a 2nd hand Note3 (UK).
Using the link above to the official LineageOS builds I can see there are tonnes of 'nightlies'.
But before I buy this thing can someone tell me, although I can see nightlies, nightlies aren't always stable or reliable.
So are there any like, MILESTONE, or FINAL solid releases of LineageOS for Note3? (like you used to get with CyanogenMod?) (milestones). I used those on my S3 and they were always more reliable.
thanks.
Very happy with my Note 3 and LineageOS 14.1
Hi,
I am using the nightlies since August 2017. I turned away from the obviously ended support of the stock rom.
My expieriences are:
- With the latest stock ROM (Android 5.0.1) it lagged very much performance and was not much fun to use anymore. A factory reset did not change anything with this.
- With lineagos 14.1 the device feels like brand new and fast in response like never before. The device is my main device in everyday use. I was very much pleased with my decision to use lineage0s 14.1 until present so far.
- The ROM is without any major issues, as far as I can tell.
- On day zero, when I flashed the ROM, ONE issue was there that I could fix. But I forgot how, sorry. It was somewhat my own fault I think, because googling around got me a solution for that. Description of the problem: Any sound (music, notification etc.) would come from the ear speaker and not the main speaker. As far as I remember, I had to deal with something like "Baseband/Modem/Bootloader" flashing. I assume, that I had flashed the wrong thing (?). I found some guides that seemed to adress wrong Baseband/Modem/Bootloader versions. I do not understand the technical details about those pieces of software, but after dealing with those things, and flashing again, everything went fine!
Finally I can recommend the nightly builds, there are no official builds yet, but they do work without major (nearly any) bugs. There is one minor exception/bug, that I am trying to find a solution to, but I can live with it, it really is not crucial to the function of the device. It is decribed here
Note 3 rocks!
kiwibird1 said:
I have sm-n9005 on linage 14.1-20170713-unoffical-hlte.
Since I installed this I have no mobile phone data, but do have mobile calls and wifi data.
Any idea what to do?
Click to expand...
Click to collapse
I had the same issuecwith my wifes Note 3, no mobile data... I simply flashed again and it worked. You also should have the right baseband/modem for this to work.
Hi All,
I have a LG G710EMW, and I want to get android 10 on it. I live in UK so I flashed EU open rom onto this phone. Now everything appears to work fine, dual sim is working OK, I can call etc, but I get this error every time on startup.
I have read other threads - but they say they get no network, however my phone seems fine. Can I leave this rom or should I wait until brazil/hong hong/aus get android 10 and then flash? Also any idea when that will happen or it's already happened? Can you share the KDZ?
rash.m2k said:
Hi All,
I have a LG G710EMW, and I want to get android 10 on it. I live in UK so I flashed EU open rom onto this phone. Now everything appears to work fine, dual sim is working OK, I can call etc, but I get this error every time on startup.
I have read other threads - but they say they get no network, however my phone seems fine. Can I leave this rom or should I wait until brazil/hong hong/aus get android 10 and then flash? Also any idea when that will happen or it's already happened? Can you share the KDZ?
Click to expand...
Click to collapse
Same here... I've flashed ITA android 10 kdz and at the startup i've got the same popup
I've flash back android 9 and I no longer have this problem.
hoping that someone knows a little more...
(my phone isn't dual sim)
gius0161 said:
Same here... I've flashed ITA android 10 kdz and at the startup i've got the same popup
I've flash back android 9 and I no longer have this problem.
hoping that someone knows a little more...
(my phone isn't dual sim)
Click to expand...
Click to collapse
Most of us who cross flash get that error. Volte also does not work. Rest all works perfectly even after that error, so i just ignore it.
lefttobleed said:
Most of us who cross flash get that error. Volte also does not work. Rest all works perfectly even after that error, so i just ignore it.
Click to expand...
Click to collapse
is there any method to remove the warning even with root?
gius0161 said:
is there any method to remove the warning even with root?
Click to expand...
Click to collapse
If you google and see there are some methods for other phones. I did not bother to try, so don't know if it will work with our phones.
lefttobleed said:
Most of us who cross flash get that error. Volte also does not work. Rest all works perfectly even after that error, so i just ignore it.
Click to expand...
Click to collapse
Why does VOLTE not work? Any way to fix it?
gius0161 said:
is there any method to remove the warning even with root?
Click to expand...
Click to collapse
Yes possible to fix: https://forum.xda-developers.com/lg-g5/how-to/cust-error-solution-t3507311
rash.m2k said:
Why does VOLTE not work? Any way to fix it?
Yes possible to fix: https://forum.xda-developers.com/lg-g5/how-to/cust-error-solution-t3507311
Click to expand...
Click to collapse
I tried the volte solution in guides section and also voenabler magisk module. They did not work for me. I have EMW.
I have shifted to lineages, so am not looking at the development in those threads anymore. Voenabler in lineage os only changed my LTE to LTE+.
Voenabler did work for someone in that thread maybe you can go to that thread and discuss or try on your phone.
lefttobleed said:
I tried the volte solution in guides section and also voenabler magisk module. They did not work for me. I have EMW.
I have shifted to lineages, so am not looking at the development in those threads anymore. Voenabler in lineage os only changed my LTE to LTE+.
Voenabler did work for someone in that thread maybe you can go to that thread and discuss or try on your phone.
Click to expand...
Click to collapse
How is lineage os? Is it stable as a everyday OS? Any issues? Rather have stock android
rash.m2k said:
How is lineage os? Is it stable as a everyday OS? Any issues? Rather have stock android
Click to expand...
Click to collapse
I use the one by Josh.
For me it is stable. I don't use bluetooth, wireless charging, etc. so cannot comment on that.
I find this to be the best ROM out there for now. It has good battery and performance.
Basically you should be ready to experiment and see if you like it. If you want a fully stable phone, and no TIME to experiment, then I would advice you to stick to stock.
rash.m2k said:
Why does VOLTE not work? Any way to fix it?
Yes possible to fix: https://forum.xda-developers.com/lg-g5/how-to/cust-error-solution-t3507311
Click to expand...
Click to collapse
I had already read this guide, but I gave up as the code did not open any menus. Doing some research I found that the code varies by model (ends with 710#). However, unfortunately it does not work. I cannot modify the NT Code and with the 20b base firmware it returns NTCODE WRITE ERROR after edit it.