yashsingh1/xdaforums huggingface dataset:
[E 2015 Original Android Development] Dunci10:
Yeah, no problem, but you will have to tell me how to do all that since im clueless on how to do logcats or radio logs. But yeah the whole ROM is flawless. I had to airplane mode it once last night because it said LTE and everything, said data was going through, but nothing would come up. But I've had that before with other phones so figured it was just a reset type thing.
[E 2015 Original Android Development] ssingh1:
Hey scritch!! The ROM is working flawlessly....CM actions and everything....

Just wanted to ask, the way you included twist to capture, how about Moto Display?

:D
[E 2015 Original Android Development] starkly_raving:
Bearer should be set to unspecified, I've edited the apnconf for Boost even directly replaced it with the stock 5.1 and had no change, I'm more and more certain its telephony. Its reading the UICC for us (Boost) hence having Sprint but the 00000 is telling me (from everything I've read so far) that its not being provisioned for the CDMA radio. However since 3G does work its just a matter of getting it to call the right carrier etc.
[E 2015 Original Android Development] sirhc:
That's good progress, I've came to the conclusion it's the telephony also. So how do we go about getting that fixed? Decompile the stock telephony and the CM one then fill the gaps? I can't read smali for sh** though lol

---------- Post added at 01:09 AM ---------- Previous post was at 01:08 AM ----------

Just picked up the Verizon variant today, I'm gonna play with that one too before I give it to my brother
[E 2015 Original Android Development] starkly_raving:
Yeah I'm going to pick apart the smali when I get in tonight.
[E 2015 Original Android Development] sirhc:
Awesome keep me posted, I'll help with anything I can, I'll be awake all night lol
[E 2015 Original Android Development] starkly_raving:
Can someone upload the telephony apk from the 44 build? Thanks.
[E 2015 Original Android Development] sirhc:
I will, just give me a minute
[E 2015 Original Android Development] sirhc:
Here you go :good:
[E 2015 Original Android Development] jhona1234:
Hi, where are smartlock on 44 build?
[E 2015 Original Android Development] grofweg:
Still under 'Lock screen' in Settings.
[E 2015 Original Android Development] jpmaster:
[MENTION=3445372]scritch007[/MENTION] I think that squid2 has solved a problem that plagues some of us for a while : low quality Wi-Fi signal and difficulty to connect to a network. See http://xdaforums.com/showpost.php?p=62765025&postcount=319
[E 2015 Original Android Development] starkly_raving:
Compiling a test build of the telephonyprovider now will report back in a bit if there's any success.
[E 2015 Original Android Development] sirhc:
Awesome! I knew you didn't go silent from the thread for nothing lol, keep me posted
[E 2015 Original Android Development] starkly_raving:
1st attempt bootlooped...

2nd attempt booted after editing some corresponding strings and IDs but now the phone is constantly crashing. :-/
[E 2015 Original Android Development] DanHutchins:
Almost seems as though its impossible are the xt1526 phones the only ones that are having issues right now?
[E 2015 Original Android Development] sirhc:
Ughhhh! That's what happened when I used the stock telephony on CM12.1. I knew it wasn't going to work but I said what the hell lol. Did you ADB push Telephony via TWRP?
[E 2015 Original Android Development] starkly_raving:
ADB...going to look at the jar files. :-/

---------- Post added at 10:27 AM ---------- Previous post was at 10:14 AM ----------

Somebody will figure it out. Sadly with other Boost Devices we had dedicated CDMA developers but we're getting closer.
[E 2015 Original Android Development] sirhc:
You can PM Unjustified Dev. He got CM12 working on the Virgin Mobile LG Tribute with LTE and all working. That guy is a miracle worker, you can also ask Phenom from Android Forums. It's something were looking past that needs to be modded.
[E 2015 Original Android Development] starkly_raving:
Yeah I'll reach out to Phenom, I know him pretty well from Android forums actually.

---------- Post added at 10:51 AM ---------- Previous post was at 10:39 AM ----------

Pmd both devs, too bad it wasn't the tribute 2 as the chip sets are identical. Do you have the link to the tribute ROM?
[E 2015 Original Android Development] jhona1234:
Ok, i see the smartlock now after pin setup and smartlock to administrator (sorry me english kkk)
[E 2015 Original Android Development] sirhc:
Here's the link https://www.androidfilehost.com/?fid=24052804347780105 and Phenom did an awesome job with the ZTE Awe, he has a fully functional CM12.1 running on that phone. And it's crazy because when I had the Tribute I was waiting for UD to post a new build for months to fix the issues and update to CM12.1 until I gave up and moved on to another device, now I see he posted a new build. That's bulls*** lol
[E 2015 Original Android Development] scritch007:
Good luck guys. Sorry I can't help you there.

I just was googling about 000000 carriers, and found that moto X and Nexus 6 users reported the same issues. I'll be looking into that.

From what I read in the posts Nexus 6 was fixed on the 3/4.

Regarding Moto X didn't find when/if it was fixed.

I'll be looking into thoses repositories too.

Are you both on the 310120 or 311870 when trying to go on the lte network?
[E 2015 Original Android Development] sirhc:
I think I was on 310120, I feel like its a telephony issue. apn_conf and eri didn't give any progress. ro.ril.force_eri_from_xml fixed the 000000 issue for me, but I'm on Sprint and it didn't work for spark

---------- Post added at 09:39 PM ---------- Previous post was at 09:39 PM ----------
[E 2015 Original Android Development] starkly_raving:
311870 for Boost users.
[E 2015 Original Android Development] sirhc:
I'm Sprint so do I still use the one for boost?
[E 2015 Original Android Development] PriPhaze:
Ik that you guys have problems with telephony and all that but ughh.. I honestly expect to see new updates about the Rom and not that. Would it be better if you open your own thread?
[E 2015 Original Android Development] amkirk94:
Any chance we see that on Official CM, just like the 3G version?
[E 2015 Original Android Development] scritch007:
[MENTION=4678203]sirhc[/MENTION] and [MENTION=4658982]starkly_raving[/MENTION] let's move the CDMA issue to the CDMA thread.
[E 2015 Original Android Development] jadephyre:
I wouldn't count on it... if they are actually going to, i'll believe it'll get released when I see it on the download-page.
[E 2015 Original Android Development] scritch007:
We could already be official, since the SEPolicy is now valid. I just wanted to clean up stuff. The only difference between an official and an unofficial version, is that it's built by CM and you have to get through the gerrit process to push new changes.

It's more convenient for me to work on the unofficial version for now on.
[E 2015 Original Android Development] amkirk94:
Moving it to Official would make our lives way easier. It will be easier for us to update, easier to report bugs and easier to distinguish stable builds from the experimental builds.

CyanogenMod is not made just for developers, it is also made for every-day people. Please don't forget that... Having CyanogenMod on the Official site makes it way more accessible for people to find and install. Plus, some people cannot take the risk of installing nightlies and they prefer Snapshots. Snapshots are generally more stable, and not just from the maintainer perspective, but also from the general CM code.

Please take all these into consideration, because I think it represents a lot of non-developer Moto E users, that do not visit XDA too often. :)

Thanks in advance :o
[E 2015 Original Android Development] adrianocolvero:
Cyandelta really may help a lot! ;)
[E 2015 Original Android Development] rokban:
The latest update r48 ramdisk network for all or CDMA users only? [MENTION=3445372]scritch007[/MENTION]
[E 2015 Original Android Development] sirhc:
It's better to push it to Official once issues are cleaned up. The rom is already functional but not fully stable. Average users expect everything to work out of the box and not every MOTO E user has the GSM variants. There are CDMA Moto E users as well and with LTE not working, you'll see an a**load of people complaining about something they didn't read on XDA, due to them expecting everything to work out of the box. Snapshots are for small changes or features being added as well as security fixes. With LTE being broken, that needs to be fixed before anything is made official. That's what he means by cleaning some stuff up.

---------- Post added at 05:16 AM ---------- Previous post was at 05:00 AM ----------

The build is Ramdisk REWORK not network lol and I'm assuming it's for all considering the Ramdisk is just a partition mounted by the kernel when the device boots

---------- Post added at 05:16 AM ---------- Previous post was at 05:16 AM ----------
[E 2015 Original Android Development] thrasher194com:
I flashed 9/12 I did factory rest twice
[E 2015 Original Android Development] amkirk94:
Thank you for your response. This actually sounds good. Whenever you feel that it is ready to go Official, make the big step ;)
[E 2015 Original Android Development] rokban:
[MENTION=3445372]scritch007[/MENTION]The present build is unusable, some blank screen is coming up every now and then, also it disappears, no idea what's that, reverted to r44 :(
[E 2015 Original Android Development] brenosabino:
anyone with a xt1523 using this rom? everything working?
[E 2015 Original Android Development] lucasolivamorim:
I'm using it. Everything working, including dual sim.
[E 2015 Original Android Development] rokban:
You clean flashed r48? Or dirty flash?
[E 2015 Original Android Development] lucasolivamorim:
I'm using build 44. Dirty flash from v42.
[E 2015 Original Android Development] PriPhaze:
Anyone here using the v48 and being able to even boot?
[E 2015 Original Android Development] rokban:
Ya it booted but some blank page is coming up and closing all the time. :(
[E 2015 Original Android Development] scritch007:
Dirty flashed the rom

and clean flashed the rom.

It works fine for me in both cases.

How do you trigger an issue? Do you an sdcard?

If it doesn't work for you, can you grab some logcats and dmesg
[E 2015 Original Android Development] entony80:
v48 clean install on xt1524 and everything works fine
[E 2015 Original Android Development] rokban:
Well I have SD card and flashed ROM from sdcard only( normally I do that). And most of my apps are on sdcard. Maybe that's the cause of, also I don't know if that's an error at all, it was just some white screen comes up and then it disappears...
[E 2015 Original Android Development] scritch007:
How do you install them to the sdcard? I'd like to try to reproduce the issue.

When you cleaned it all, you wipe cache/dalvik cache (which shouldn't be necessary)/data and system?
[E 2015 Original Android Development] rokban:
Well, 1) I had most of my apps moved to sdcard( there's an option to move apps to sdcard ).2) I wiped cache and dalvik cache only, then flashed the ROM r48.

3) everything went normal ,device booted and then when I clicked settings this thing started , then in every few seconds some blank screen comes up and disappears. This issue I faced first time using android:) strange one but it happened.
[E 2015 Original Android Development] grofweg:
Dirty flashed 48, supersu and squid's kernel r7F. No probs so far (XT1524)
[E 2015 Original Android Development] scritch007:
Actually the goal was to change stuff in the ramdisk, so flashing squid kernel doesn't take into account those changes.

Seems like it's x1524 users don't have any issue with the build. Anyone else facing some issues, or having a fully working version?
[E 2015 Original Android Development] ssingh1:
Hey scritch! What about the moto display?
[E 2015 Original Android Development] scritch007:
Maybe you can start by telling me if 48 works for you or not. And once it works for everyone, I can look for new features.

Even though I don't think I'll add it.
[E 2015 Original Android Development] ssingh1:
Why? Don't you like moto display?
[E 2015 Original Android Development] rokban:
[MENTION=3445372]scritch007[/MENTION] I will reflash r48 later at night, right now am using LTE as hotspot , will do a clean flash and get back to you.
[E 2015 Original Android Development] matteo 06:
HI@scritch,I have xt 1524,installed build 48, any issue ,all works perfectly. Thanks

Edit:Put on the table ,i take it lights
[E 2015 Original Android Development] DanHutchins:
I'm on xt1526 and it is working fine for me although I ran out of service so I can't say data is working but everything else is fine
[E 2015 Original Android Development] scritch007:
Any working dual sim flash for version 48?

It changed the way to start the second sim card, maybe this could be the issue
[E 2015 Original Android Development] squid2:
Newer versions of my kernel (r7b and up) actually rebuild the boot image and use whichever ramdisk was previously installed. That's how one kernel zip is able to work on any ROM.
[E 2015 Original Android Development] JobSup:
Dirty flash from 44 to 48 on my XT1524, no problems. But I must admit that I also flashed 48, TKGapps, squid's kernel r7f and the WLAN firmware you posted. Manly to see if WLAN is improved. No problems so far, I'll leave that for now.

Thanks!
[E 2015 Original Android Development] scritch007:
Thanks, didn't know that.
[E 2015 Original Android Development] sirhc:
Clean Flashed, LTE still not working, but this build does seem a little smoother and faster and boot time has improved. Great work :thumbup:
[E 2015 Original Android Development] jpmaster:
xt1524, flashed 48 over 44, squid kernel r7f and surnia_wlan_nv.

For now, everything works flawlessly.
[E 2015 Original Android Development] rokban:
[MENTION=3445372]scritch007[/MENTION] clean flashed, everything is working fine !
[E 2015 Original Android Development] Roman2K:
[MENTION=3445372]scritch007[/MENTION] Thanks for the hard work. I'm buying the Moto E (XT1524) thanks to you ?. I'd be very interested in the LED functioning on battery as well.
[E 2015 Original Android Development] Jaball:
Hubdroid 404...
[E 2015 Original Android Development] therealprof:
And back. ;)
[E 2015 Original Android Development] yelupic:
Build 48 is working well on XT1524

Round 1:

flashed dirty over 44 (vaporizing squid kernel r7f + 5.1 wcnss...nv.bin) - OK

Round 2:

full wipe/clean install, no gapps, no user apps, no tweaks (pure rom) - OK

(missed the lock screen, too, which appeared after the first reboot)

One bug:

Bluetooth streaming of MP3 files with short drops every 4 seconds

(A2DP stereo bluetooth headset, works fine with stock/same mp3 file/same hardware)

I pulled a logcat trace (please, see attached file) while playing one song with eleven over the speaker (having no drops), then switched on bluetooth via toggle, listened a few seconds (having drops), switched off bluetooth again. - Maybe useful: In line 30.415 the artist/song title "Transpose - Inside The Time" is mentioned.

Edit:

Also viewing a YouTube movie in the browser hearing over bluetooth gives the identical error pattern.

Happy chase and thank you for your work, @scritch007

_
[E 2015 Original Android Development] ssingh1:
[MENTION=3445372]scritch007[/MENTION] I was earlier using the 15-7-2015 version, which worked flawlessly. But when I updated to number 42, the phone became extremely laggy. Any particular reason?

P.S: I did a clean install.
[E 2015 Original Android Development] Fedray:
Why don't you flash the last version?
[E 2015 Original Android Development] ssingh1:
Exams were on.... Will download and flash today.... ☺
[E 2015 Original Android Development] Fedray:
What about build 50 osprey kernel? Changelog?
[E 2015 Original Android Development] grofweg:
The questions is why changing to the Osprey kernel, what are the benefits over Squid's. Has this anything to so with a possible 'official' status of the rom?
[E 2015 Original Android Development] Roman2K:
I'm running 48 and it's extremely laggy as well. I apprehend every action for fear of temporary freeze. But I can't compare to other versions nor stock because I put 48 directly after unboxing. Can I help debug in any way?
[E 2015 Original Android Development] scritch007:
cm-12.1-20150916-UNOFFICIAL-surnia-osprey-kernel-50.zip

Use the same kernel as osprey

I thought the name of the build was pretty obvious, but here is the changelog.

And yes maybe this is for using the same kernel as osprey when going official, but maybe not ;)
[E 2015 Original Android Development] rokban:
I like this r50, somehow it seems more battery friendly and smoother than previous builds.
[E 2015 Original Android Development] ssingh1:
How about including the true caller dialer from the android 5.1 update for the one plus one

And the app themer
[E 2015 Original Android Development] PriPhaze:
It was worse for me .. until i installed squid kernel r8. Now its really smooth
[E 2015 Original Android Development] lucasolivamorim:
Yes, my phone was really slow before the install of squid kernel.
[E 2015 Original Android Development] Roman2K:
Thank you so much! :good: Night and day. Like it was agonising using a single core and now with the squid kernel, exploiting all 4, finally breathing.
[E 2015 Original Android Development] thathtcguy:
Using squid kernel r8 with the version of the Rom that came out yesterday, battery life is terrible it's leggy.
[E 2015 Original Android Development] yelupic:
Build 50 (osprey kernel, pure ROM, XT1524) works well.

Notification light: The notification LED functionality (which worked before) has gone south. Is this because of the osprey kernel? Will it come back?

Bluetooth: No change in error pattern (drops every 4 to 6 seconds here). - Same setup while testing.
[E 2015 Original Android Development] scritch007:
Thanks for testing. People want it to become official, but don't even bother testing what would be the official version.

Yes the led notification is broken because of the kernel. I already made a patch, so that it can be compatible with osprey and surnia:

https://github.com/Motorola-Cyanoge...mmit/79aeee18dc84e0e86d380f0715170d50aab84f15

I'm working on adding the led while charger is plugged. I just have to make the choice when charger is plugged do we want to have the led notification or not.

Regarding your bluetooth issue, I tried with my bluetooth headset and my bluetooth bose speaker and I don't get the problem. I'll add this file https://github.com/MotoG3/android_device_motorola_osprey/blob/cm-12.1/rootdir/etc/init.qcom.bt.sh in next build, just in case this help your particular problem.
[E 2015 Original Android Development] therealprof:
Thanks for your hard work. I'm not quite sure to interpret your statement above; which is the version you'd like people to test? 50 or a previous version?
[E 2015 Original Android Development] scritch007:
Latest version (not the CDMA testers versions) but with my kernel. I mean it's not only a rom, it's both that are important, so when I read, flash squid kernel, it just doesn't help.

Although I do agree that flashing squid kernel in the end can help you and improve your experience, but the goal is to have a steady rom as is, squid2's kernel is too much tweaked to go to CM repos.

If you flash squid kernel directly you'll have the led notification, so you'll miss that issue and maybe others. Same think for the wifi, it's using the same code as the osprey kernel, maybe it's not as good as my previous kernel nor squid's kernel, I didn't update the WLAN blob either yet, but is the dhcp working for every body now?

The point here is to test it as a whole.

If I only cared about my usage, I wouldn't even bother supporting other version then the xt1524 and it would have been finished a long time ago.

Reporting that you think is slow can be useful, I don't see any difference between the older kernel and this new one, the only change is that now the CPU can go at 200Mhz instead of being blocked at 800Mhz before so probably better battery life
[E 2015 Original Android Development] rokban:
Well ,for me I still believe it's battery friendly for my device, am checking with 100% battery and will see how it goes till 5%, and another reason I like this build 50 is call quality, its so clear I never had before ( I don't know if that's coz of osprey kernel or not).

Thanks a lot for your efforts.

[MENTION=3445372]scritch007[/MENTION] to get the CPU to 200 we need to use kernel auditor or it's automatically done?
[E 2015 Original Android Development] scritch007:
The lowest CPU frequency is now 200 instead of 800 (stock) value. This will be done by your governor. It doesn't go that much so low, but I managed to see it a little when running CPU-Z
[E 2015 Original Android Development] yelupic:
So, guys, that's it: respect and honour the dev by

installing only his pure ROM (clean install, no gapps|tweaks|mods) for testing in the first run

then (and only then) go ahead with your personal preferred modifications in round 2

report your findings for both sequences clearly tagged (to separate things)

This is no demand, but a humble request to all testers (and time consuming - as it's for the dev, yes) ...

This will speed up development, quality and results for everyone, right?
[E 2015 Original Android Development] yelupic:
Thank you, this sounds promising. - In builds 48/50 I'm having a bluetooth mac of 00:00:00:00:5a:ad, which is not the one displayed in stock. - I'll test the next release with the file integrated.
[E 2015 Original Android Development] ssingh1:
[MENTION=3445372]scritch007[/MENTION] While browsing through the official wiki of cyanogen, I stumbled upon the official thread of Cyanogen For the Moto E 2015 3G version...

Why don't you make yours official??
[E 2015 Original Android Development] DanHutchins:
Just saying the ones that are complaining about not having official more than likely have no clue what goes into this kind of stuff and just think they can bully people to get what they want

And yes led when plunged would be great and thanks for all your hard work
[E 2015 Original Android Development] yelupic:
Because he is a wise guy wise man?

Edit: sorry for the faulty term. - In other words: He knows what he's doing and it's his decision.
[E 2015 Original Android Development] ssingh1:
Yep. :D
[E 2015 Original Android Development] Shreps:
Stop ask the same thing everyday. He already answered and explain why.

This thread is for devlopment and trying to make the ROM stable.

So guys, stop asking and report for others things which are not related to this thread !

Thx :)
[E 2015 Original Android Development] Fedray:
Sorry if I'm a bit annoying about this scritch, but have you look into the microphone thing in WhatsApp? For some reason when doing a voice record it uses back microphone (the one used for noise cancellation?) and not bottom mic (I remember having the same problem in cm10.2/cm11 in my old lg l7 ii, but it was top microphone instead), hope you can look that!

Enviado desde mi MotoE2(4G-LTE) mediante Tapatalk
[E 2015 Original Android Development] therealprof:
Actually I prefer deep sleep over 200MHz which my system spends 97% of its time in. My only "problem" going to the new version is that your 0523 build already runs so great that I'm really worried about deterioration here. ;)
[E 2015 Original Android Development] PriPhaze:
Ok, it was wrong to just talk about squid kernel . That way the development of the rom will be slow .

I reported a few things almost about 4 builds ago and they now seem to be fixed.

For example i used to have this bizarre sound while playing music, i first though that it could be a governor issue but i was wrong.

The ramdisk rework build fixed that problem and im really thankful for that :D

I haven´t notice any other issue so far and every time you release a new build i make sure to test it at least one day to see the battery life, performance etc.

Thanks for all your work.