yashsingh1/xdaforums huggingface dataset:
[Moto G Original Android Development] pinsicchio:
yesterday (attacked kernel)! that's why I'm saying it is impossible that the kernel is out of date
[Moto G Original Android Development] aouerfelli:
^^ This. Flash TWRP (any version), then flash CWM after.
[Moto G Original Android Development] i_rnb:
Try deleting /data/system/theme folder from recovery.
[Moto G Original Android Development] xpirt:
nvm
[Moto G Original Android Development] Droidriven:
What has he come up with so far? See what he thinks about where I was going with my tests and my conclusions and ideas in my post.
[Moto G Original Android Development] panan.t:
E:unknown volume for path [@/cache/recovery/block.map]

E:unknown volume for path [@/cache/recovery/block.map]

Would be really appreciated if anyone could advise how to fix the error when I try to update the CM nightly.

E:unknown volume for path [@/cache/recovery/block.map]

E:Can't mount @/cache/recovery/block.map

Installation aborted.

/tmp/recovery.log copied to /sdcard/clockworkmod/philz_recovery.log

I'm using PhilZ Touch 6.58.7 with XT1033
[Moto G Original Android Development] remo0073:
Try Philz 6.55.0

For me it works good

Sent from my Moto G
[Moto G Original Android Development] panan.t:
Thanks for your message. But no, still the same error with Philz 6.55.0
[Moto G Original Android Development] andromobilogy:
I have a problem with the showing mode in the phone contacts.

When i go to phone>>contacts menu my contacts are shown as surname, name mode even why on settings are set to be shown as first name first.
[Moto G Original Android Development] mondechristo1:
I really can't understand why is it so difficult for developers to fix the problem with GPS. It's a known problem which exists from CM11. I know that I can flash the stock ROM first but....after so many months...the same problem!:confused:

I really like CM ROMS but I have to be stuck to stock! :rolleyes:
[Moto G Original Android Development] phizi0n:
I had that problem pop up a couple weeks ago but it only affected OTA updates. You should be able to go into recovery and manually flash the zip that you already have downloaded to /sdcard/cmupdater or just start using CyanDelta to save some bandwidth/time.
[Moto G Original Android Development] dovw:
Boost's only Moto G is the 1st Gen CDMA-only xt1031 - those who have gotten an MFN invite are getting it for that device

---------- Post added at 05:40 PM ---------- Previous post was at 05:13 PM ----------

1) Is there no way to catch in the logs where the startup is setting the SIM dependency? If there is should it not then be possible to correlate it to the point in the code that needs changing?

2) Talking of senior devs, [MENTION=513620]Quarx[/MENTION] used to work on some CDMA variants - if anyone could get his ear that may be a gamechanger
[Moto G Original Android Development] moralesnery:
I have no Ambient Display or the option to enable it on 02/09 build. Does someone have this problem too or knows how to solve it?

Thanks in advance
[Moto G Original Android Development] i_rnb:
Is there anyway to grab direct links of incremental update zips from CyanDelta to download the zip from PC?
[Moto G Original Android Development] mightysween:
Sounds about right. I believe the change we need would be in the "Setup Wizard". That is where the initial radio bringup seems to take place and we would have the opportunity to fork to a non-SIM installation.

---------- Post added at 02:09 PM ---------- Previous post was at 02:07 PM ----------

Oh, cool... I didnt realize it was a device specific invite. I assumed it was a general Boost Lollipop invite.

---------- Post added at 02:13 PM ---------- Previous post was at 02:09 PM ----------

Just remember when explaining it that this is not a CDMA problem...the radio works. The solution we are after is a workaround for AOSP base incompatibility with non-SIM devices.

---------- Post added at 02:33 PM ---------- Previous post was at 02:13 PM ----------

For those with coding familiarity, this is one of several places we can see the issue at hand.

http://review.cyanogenmod.org/#/c/8...nmod/setupwizard/setup/CMSetupWizardData.java

CM has only two possible states when bringing up the telephony system... either 1.) there is a SIM inserted, or 2.)the SIM is absent from the slot.

Obviously, a 3rd possible state should be included. If the SIM detection fails, the next step should be to check if there is actually a slot to begin with. And if the answer is no, it needs to assume that the device is CDMA and NV-Only

Of course, there may be earlier points in the install to have this happen.
[Moto G Original Android Development] Droidriven:
http://review.cyanogenmod.org/#/c/8...nmod/setupwizard/setup/CMSetupWizardData.java

I showed the setup wizard stuff you linked to Motorhead (he suggested our problem may be java related then i passed him your link) the Co admin at Android Area51 while we were troubleshooting the ROM we are trying to put together for my device with SIM dependency removed, he said what you linked had two commits but neither were SIM related but he did say there may some kind of overlay.

I'm not sure if our problem is really in setup wizard, part of it may be but that still isn't everything because when I did a clean flash of CM12 and inserted SIM then booted up my device had mobile service and data, then after first boot I removed the SIM while device was running and the device retained service and data until rebooted, then when it booted it had no service and no data, so setup wizard isn't necessarily our issue either, its each time the device is booted, setup wizard is only the first time the device is booted into whatever ROM it has on it, after that there is no more setup wizard, our issue is in the boot sequence. Granted there may be something to redirect in setup wizard but this only covers the first boot and not each subsequent boot. If I could make sense of the coding I would tear into the ROM and start with the first line in boot sequence and go through line by line of boot sequence until I see the first sign of the SIM then patch that spot with what our perspective devices need then go to the next step that involves SIM and patch it then continue line by line all the way through boot sequence until its conclusion then maybe the system will initialize as normal, I just hope there aren't things laced into the stock apps for our ROMs (the apps that come with the ROM, not google apps, as they are flashed separately and have nothing to do with ROM or connection). Trying to think about this as we would normally before Lollipop came along and what could affect connectivity isn't going to work because before ROMs were based on different principles (namely 3G CDMA present in ROM's by default), this is not going to be beaten by conventional thinking or modding, this is something that hasn't been so prevalently present in ROMs before lollipop, it could very well be hiding in a place that we would never think about, a place that normally wouldn't have anything to do with connection, a place easily overlooked by taking for granted that it isn't there because what we know from BEFORE lollipop tells us it isn't when it very well could be, the focus needs to be put into thinking like the ROM Itself instead of trying to think like your devices, the ROMs are made for 4G devices so they want our devices to have the 4G hardware and system setup as a 4G device does, instead of trying to turn the ROM into 3G ROM we need to trick the ROM into thinking our device is a 4G device, this would only require the redirection we are looking for instead of rewriting the whole ROM.
[Moto G Original Android Development] mightysween:
bingo on the 4g thing. If you look, the phone is registering as LTE despite no capability. A simple test would be to try to make it register CDMA instead.

---------- Post added at 06:52 PM ---------- Previous post was at 06:49 PM ----------

I say "simple"... hahaha :)
[Moto G Original Android Development] Droidriven:
Well, in the process of trying to create a 3g based ROM we got the radios on, it registers on the right network, getprop shows the correct values and baseband is recognized, we have it registering as CDMA as my device is supposed to so there's a little more to it than just getting radios on and getting device reistered on network. What else is missing I don't know, I can definitely say that obviously the meat and potatoes of it is in build.prop, RIL and libraries, but we need to find the appetizer before it hits the grill(so to speak) because it never even gets to see the main course, any changes made to any part after the end of boot sequence could turn into a mess because with the block at startup we'll never know if what we change after that point is helping us or hurting us. Finding that locked door is primary goal, only THERE will a breakthrough be made, then we can see if any changes we have come up with are having an effect or not. Until then we are p*$$**g in the wind, we may make more of a mess than anything and not discover the mess we've made until we find the block.
[Moto G Original Android Development] :
In case it'll help, I remember on one build I had a java error pop up when an app tried accessing data. I don't remember what build or what app, but I could try to get it to happen again and jot down what it says and take some logs if you think it's might point you in the right direction.
[Moto G Original Android Development] Droidriven:
Anything is worth a shot but I'm thinking anything we pull from the device after the startup boot sequence and SIM reference isn't going to tell us much other than connection isn't happening, we need to catch a sequence of startup events before the device gets fully booted into system to catch what we are looking for.

---------- Post added at 09:55 PM ---------- Previous post was at 08:56 PM ----------

I'm thinking that we need to find the first reference to SIM and direct it to our system folders that our devices normally use for connection information OR make a new folder that contains the information that would be on a SIM and place this folder in system and direct startup to that folder.
[Moto G Original Android Development] mightysween:
So, you are able to see CDMA and not LTE in CellInfo? (*#*#4636#*#*) This is something I have been unable to accomplish...it always registers LTE unlike CM11 or stock 4.4.x
[Moto G Original Android Development] Droidriven:
I never did the secret menu through the dialer, I don't have internet at home so when I'm home I do everything through my phones hotspot, Motorhead, my tester and I work together on this, my tester flashed the ROM that we put together and we troubleshot from there, the last logcat that was ran from the device on our ROM had the device registering on the network but still had no service or data, I already have a copy of the ROM and I'm downloading 5.0 Gapps now, I'll flash it and let you know what I come up with, I'll test with the SIM inserted and with it removed.

To get where we are now with the ROM we inserted my devices stock RILblobs and libs with CM11 build.prop then adb chased the files that needed patching, we ran command to find errors for missing files then patched the file and ran command for the next error and file patch and so on until all was in place, I can't remember everything that was done with build.prop. You may be interested in reading in the "Straight Talk S3 sch-968c info" thread here at XDA to see what has been chased from Nov to now. We had a dev that has worked with Invisblek, he and Invisblek started digging around in the RILs back before CM12 was dropped because the SIM had worked its way into the last builds of CM11 on the S3's (this came about when they unified all the S3 devices under one ROM), if you read the "how to root Straight talk S3 sch-s968c" thread you'll see that I discovered that the SIM was required back in Oct, the CM team was notified at that time of the issue, this was the factor that brought about the devs going back to UN-unified builds for all the S3 variants. I've been hunting this down daily trying to find the answer, I don't have the dev experience that it takes for this, out of all the devices out there, there a LOT of people (users and devs) trying to find this workaround and they have been for months now, that is a lot of people and seems like we would be further along than we are now, this is what tells me that this is not going to be easy by any means. Some very good devs are even having problems with this, the master devs I know are baffled by this issue, they don't understand it and have no idea where they should be looking, that's why I say our problem is in a place that by all rights should not have anything to do with network connectivity.
[Moto G Original Android Development] fraz0815:
f2fs support broken since a few nightlies?

Did anyone try f2fs for data and cache partition lately? Tried to upgrade from 02/02 (with f2fs cache and data partition) to 02/09 nightly but got stuck in boot animation - could flash 02/02 back again and it worked.

Tried again with 02/11 nightly, same result even with clean flash. Formatted cache and data back to ext4 and it worked again.
[Moto G Original Android Development] netizenn:
This must be a silly question/observation but Yesterday I had to make a clean install with the nightly 9 and realized that the reboot options is gone. Today I already updated to the nightly 11 and reboot remains without option (revovery, restart or turn off).

Any tip? thanks
[Moto G Original Android Development] abhifx:
camera not working in the latest nightly (XT1033). time of log.

edit: clean install seems to be working for now... hmmm
[Moto G Original Android Development] Swift2603:
Re-activate the developer options and enable "Advanced Reboot Menu" there.
[Moto G Original Android Development] diogobuique:
it doesn't work
[Moto G Original Android Development] Udtabhediya:
Bug list as of latest nightly 2015-02-11

1)GPS BUG "Device only" mode doesn't locates on google maps as well as here maps or any other location service but works for only high accuracy mode but no location lock in open skies when location is selected for "device only"

2)VIDEO BUG If i play a video it hangs at first then it must be stopped and resumed for a couple of times to resume smooth playback, same bug for MX player to for a few video formats but works completely fine if played in S/W mode.

3)I have tried a few super user clients and none works. i will try some other zip.

4)AOSP keyboard gesture typing doesn't work. i have installed google keyboard which works fine.

out of all these the, GPS bug is quite annoying., i noticed it while traveling and it didn't work as i am using it as daily driver.

Great rom. everything else works like a charm and kudos to developers and thank you for such a beautiful rom.:good:

---------- Post added at 07:01 PM ---------- Previous post was at 06:32 PM ----------

P.S.

i am using xt_1033
[Moto G Original Android Development] dysoct:
How about the minfree issue?
[Moto G Original Android Development] mightysween:
I agree. Since early December, my position has been that the issue is a base AOSP issue, not CM specific. The update we need will likely have to come from Motorola.

With Boost sending out soak invites specifically for XT1031, perhaps that update is closer. But there is a lingering suspicion that awareness of this issue does not go very high up the chain, and that the first Boost OTA will basically just be a branded version of Moto stock complete with SIM dependency.
[Moto G Original Android Development] russ722:
That code doesn't work on boost mobile
[Moto G Original Android Development] mightysween:
strange, thought it was a motorola thing. You can also download apps to open the phone testing screen
[Moto G Original Android Development] crouse:
That code works on my xt1031 which is on us cellular, I can't see how it would make a difference
[Moto G Original Android Development] :
It doesn't work on my Boost Mobile either.
[Moto G Original Android Development] dovw:
1) Interesting, I am sure that *#*#4636#*#* worked for me on both CM11 and CM12 (yes, I have an xt1031 flashed to xt1028 on vzw (pp)) - BUT in optimized flashable zip stock ROM WITH FOTA_Disabler.zip, which I am on now - it does not work - but I suspect this may not be about the network, nor the device, nor even the ROM but the FOTA_Disabler.zip

2) What makes me suspect the FOTA_Disabler.zip is that installing a hidden menu app does not help - other options work but the "Testing..." does not - and when it fails I get a result I believe I previously saw on a System Update check- an exclamation point notification of "checkin" error
[Moto G Original Android Development] Droidriven:
Pull the settings.apk and settingsprovider.apk from system/app folder from previous version then push them to the system/app folder on your new version, just rename the existing apk's by adding a .bak extension before you push the new apk's to system, that way if there a problem in doing this you can delete the new apk's and remove the .bak extension and be straight again. Try apk's from different versions of the same ROM till you find one with your options that works with no problem, use a file manager with a root explorer so you can set write permissions.
[Moto G Original Android Development] crouse:
On another note I was messing around after setting up a system to build ROMs and after editing a file in telephony where it is supposed to enable a dummy sim to allow emergency calls , I could call out... Or at least I could call my own number and get my voicemail prompt. No data still and still had the no sim icon which came up as invalid after editing build props. Xt1031 on us cellular. I'll look for the specific spot where I edited in a little bit

Fact of the matter is I didn't get the call not sent error ..
[Moto G Original Android Development] Droidriven:
I'm not sure about the AOSP vs. Cm thing you mention, as I said the CM team was made aware of the issue back in late Oct/Nov when I first discovered the SIM dependency in the last builds of CM11 before CM12 was introduced on my device, this issue is a CM thing because at that time the CM team informed we that were working on this that what we were dealing with was the result of changes that had been made in CM itself in the 10 months before I discovered it. Its a CM issue but the CM team doesn't care about whether their ROM works on what they consider to be lesser devices, they have no interest in supporting or devices, that's why we are having to do this ourself and why Non-CM devs are having to build our ROMs, they ARE aware of this upstream, they just don't consider it to be their problem because our devices were never their targets anyway.
[Moto G Original Android Development] crouse:
/home/dev/android/system1/packages/services/Telephony/src/com/android/servic

es/telephony/TelecomAccountRegistry.java

*** // If we did not list ANY accounts, we need to provide a "default" SIM

account

******* // for emergency numbers since no actual SIM is needed for dialing

emergency

******* // numbers but a phone account is.

******* if (mAccounts.isEmpty()) {

*********** mAccounts.add(new AccountEntry(PhoneFactory.getDefaultPhone(),

false /* emergency */,

******************* false /* isDummy */));

******* }

******* // Add a fake account entry.

******* if (DBG && phones.length > 0 &&

"TRUE".equals(System.getProperty("cdma_sim"))) {

*********** mAccounts.add(new AccountEntry(phones[0], false /* emergency */,

false /* isDummy */));

******* }

Pretty much the trues got changed to false
[Moto G Original Android Development] mightysween:
Like this idea. Should be a similar place for data network bringup...where it is looking for SIM to establish the socket
[Moto G Original Android Development] dau999:
This Code/Number String is a HTC Thing, let you enter a hidden Battery mode.
[Moto G Original Android Development] mightysween:
*#*#4636#*#* has been the motorola (and others) testing mode for a long time

just confirmed it IS disabled in stock based ROMs. You can get apps on Play Store to open it if you so desire.
[Moto G Original Android Development] crouse:
Any idea where? I don't have much time these days so anything would be good
[Moto G Original Android Development] mightysween:
Man, I hear ya... no time here either. Wish I could sit down and sift through code but just cant

My best guess is that we need to look directly in telephony...there arent TOO many places. Got to be something SIM related there
[Moto G Original Android Development] padhu1989:
I'm not able to send or recieve any messages. Im in latest nightly,,Anyone one facing the problem? Any fixes?
[Moto G Original Android Development] ULELLA:
I tried to install the last nightly on my XT032 (originally stock, but converted to stock GPE 5.0.2) but it keeps giving me the error

E: Error executing updater binary in zip "name of the cm nightly.zip"

E: Unable to mount /system

I trried with stock and GPE TWRP (2.8.4.0 and 2.8.2.0), and I tried to flash a CM11 rom first, but nothing, keeps giving me this error. Anything I can do?
[Moto G Original Android Development] indrasatrya:
Try to wipe all except internal memory

---------- Post added at 01:35 PM ---------- Previous post was at 01:35 PM ----------

Are you XT1033 converted GPE?
[Moto G Original Android Development] ULELLA:
[MENTION=4645888]indrasatrya[/MENTION]: Already did: Dalvik, Data, Cache, System. Just Internal Storage left unchecked
[Moto G Original Android Development] fraz0815:
GPE changes partition layout, You need to flash correct gpt.bin wich is a risk.

See http://xdaforums.com/moto-g/general...-available-t2994695/post58477768#post58477768 or here http://xdaforums.com/moto-g/general/41-18-bootloader-restoring-4-4-2-gpt-t3015779.

I flashed that file from here http://xdaforums.com/showpost.php?p=57444986&postcount=1 for my xt1032
[Moto G Original Android Development] ULELLA:
So I should just flash the file in your third link?
[Moto G Original Android Development] remo0073:
I had a similar problem.

I flashed over GPE new stock Motorola firmware (Lollipop 5.0.2 BR XT1032) using Fastboot

http://www.filefactory.com/file/5i311qq8mguf/BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml.zip

Then I flashed official TWRP 2.8.1.0

http://techerrata.com/browse/twrp2/xt1032

Wiped everything except SDCard and then CM Zip flash was ok
[Moto G Original Android Development] ULELLA:
I think I will do the same thing. Feels less risky. What are the commands to flash the rom via Fastboot?

EDIT: But that is the Brazilian version? Is it ok for me to use that even if I have UK Moto G?
[Moto G Original Android Development] easysid:
Since Feb-11 Nightly, battery backup has been quite poor. Anyone else noticing this issue?

Any tips for prolonging battery?
[Moto G Original Android Development] fraz0815:
Quite the same but more than needed, (gpt. bin is part of moto firmware package)

I did so and it worked, although I did not check where the file did come from, eg from which rom/which model., so I won't recommend it generally.

It seems you can also take the file out of remo0073 's archive linked above. I would say you are safe as long as the file comes from 4.4.4 or above original xt1032 moto firmware. d33dvb used even a 4.4.2 file.

I am not even sure if they differ between xt1032 and lets say 1034. or if the file changed between 4.4.4 and 5.0.x.

So i feel a bid like Jon Snow 'knowin nothin" ;)
[Moto G Original Android Development] Sparticuz:
I noticed this also, at the same time they fixed the LMK, I guess that's the drawback when the device isn't killing apps left and right...
[Moto G Original Android Development] stannek:
I can't connect other devices with bluetooth. My bluetooth closes after a few seconds. A connection is impossible.
[Moto G Original Android Development] padhu1989:
Yes.. I got a fix and sms is working fine now