Search results

Thanks steadfasterX, this worked well!

I am trying to bulock a verizon LG g4 and everythong goes well until the pre-test stage of flashing, where it seems the partition does not get updated and the process is aborted. Here is the log fragment: 2020-01-06 12:54:01: 0 2020-01-06 12:54:01: F_UPDATE: ended 2020-01-06 12:54:11...

Please , any link for v29A?

Hi all, I understand v29A is rolling out. Anyone got a kdz? Thank you!

Is this sufficient to switch from Verizon to Sprint? Or is there anything else needed for that?

Huh, I tried again and this time it worked. The problem was that previously I used a script to flash and it did not include a fastboot invocation for the last piece of the system image.

I am in thes ame boat, couldnt find a fix. I went back to 5.0.2

Hm, I tried the 5.1 boost ROM from the same site, but I got a bootloop if only flashing system and hang on boot if following the full process....

Hi, did you manage to solve your issue? I am also in the same boat, looking forsprint moto e stock 5.1 firmware or comatible. Didyou have any success?

Same problem here...

I have a Sprint Moto E on 5.0.2 and would like to upgrade it to 5.1, but the only stock firmware I found for the hardware model I have (XT1526) comes from boost (Sprint MNVO). My question is: is that ROM compatible with my phone? Alternatively, does anyone have or can share the Sprint 5.1...

Did you manage to get a 5.1 ROM for sprint moto e 2015? I am looking for the same thing. Maybe the boost 5.1 stock rom would work?

Compatibility question If have the Moto e 2015 Sprint, would the Boost version work on it? Both are XT1526. Thanks!

Sprint Moto E Do any of these ROMs work on Sprint Moto E (XT1526)? I would say that they do not work, but just wanted confirmation.

Looking forward for future updates, especially more stability! great job!

OMG! I don't log in to the forums for a few weeks and I lose THIS! Wow, great work! Does that mean no more black stuff on gmail etc? I am guessing the latest daily is the build to get, right? Thank you solo much, man!

If that is the Nexus wireless charger, it may be ok. If it was the wired charger, then something is wrong, that is very slow.

Exactly! This is why I picked the cable I am using now, but I could not get over 900mA with this combination of cable + charger. The Charger is a T-mobile dual USB 3A charger and in my opinion it is very good.

Could an owner of this charger use the free Elixir 2 app and in the Information menu, check the charging speed (the number of milliamperes is listed there) while the device is charging? Please try to do this when the device is charging and the charge is under 75%, since the charging speed...

Guys, for the wired chargers, we are not talking about the STATED MAXIMUM OUTPUT here, we are talking about the output IN PRACTICE. Most chargers are rated for instantaneous output (it can output 1A or 2A or whatever is listed on the charger, but only for a millisecond, then the rate will fall...

Hello all, I am trying to figure out which is the fastest charger, wired or wireless for the Nexus 5. To do this, I suggest we gather measurements about the charging speed for the phone charging when it has less than 75% charge. My results are the following so far: T-Mobile dual usb wall...

Ha! I started getting the same error, but I thought it is just me... The problem is this the denied permission: Permission Denial: getCurrentUser() from pid=9005, uid=10013 requires android.permission.INTERACT_ACROSS_USERS which brings the whole process down. I have no idea how to work around...

I see. I just tested your kernel with Evervolv rom (latest daily build) and signal drop is there.

"Maybe might possibly help with signal drops" Wait...isn't the signal drop on missed call fixed already?

I can't figure it out... which of the current 4.2 ROMs don't have the signal drop bug on missed call?

What about the speakerphone and mute bugs?

So, in the end..what is the current status? Is signal drop fixed? Is signal drop fixed? What about mic mute? Speaker phone during calls? By the way, Sythetic, Coders and all other active devs... YOU GUYS ROCK.

I already did. However, I think time has come for me to upgrade to JB and I was hoping he would be able to clarify if he belies that we have a change of a ROM without thse bugs that I mentioned...

Elgin, I wanted to figure out if I should jump ship and just buy a new phone. I can't use the 4.2/4.3 roms because of two bugs: -the lost connectivity after missed call bug and -the speaker phone bug. What do you think: is there a chance of ever getting these fixed? PS: I appreciate your...

What about the speakerphone bug, is that absent in this ROM too?

There is no way any one of us can _ask_ for a 4.3 ROM for good old Glacier... Going for 2.2 to 4.2 was a huge feat. Going to 4.3 would be the most incredible feat ever. We should all appreciate the developers we have more, and thank them for their time, even if we will never have a 4.3 ROM...

Unfortunately, I can't live without my phone speakerphone and it does not work in calls on JB ROMs.

Yup, thats right. It looks like this... http://i.imgur.com/9gDq9xn.png.

I would like to have my vanilla Cyanogenmod 7 ROM use the circle mod, preferably the one that has those indentations on it and the percentage. Is there a flashable zip around for that?

Ditto.

After switching a call to speakerphone, can you hear the other party and they can still hear you? (check both)

Thank you for your work, albinoman. One question: is there any hope of having speakerphone working in call?

By "speakerphone works" do you mean in calls? You can put the call on speaker now? That would be great!

Thanks man! I was a fan of your ROM initially but had switched when it did not get updated for a while. Now I am back and love it!

Here is the _real_ fix for the reverted screen problem: increase the minimum frequency. 380MHz makes it happen more rarely and at around 500 I have trouble reproducing it.

I have the same problem even on calls, after I finish the call, then screen comes up upside down, even though rotation is only allowed at 0 and 90 degrees. Locking and Unlocking works as a fix, but this is anooooying. Had this problem on most JB ROMs, but a fix would be really nice.

I can confirm the problem is still there. Considering we can still use the headphones, I think the speakerphone issue is more annoying, because we cant use the speakerphone at all.

Same here.

Is this on the new April 28th build?

Wohoo. If you solve the "switch to speakerphone" issue, we will have the first truly daily driver 4.2.2 rom!

Yup, also, when in a call, if you switch to speakerphone the other person does not hear you anymore, even if you switch back. Do you guys have this problem too?

Same here. Clearing gallery cache does not help.

Today I encountered this problem, on the latest build. Did not happen on the previous build I tried though.

Ah, I got that too. I found that increasing the minimum frequency helps (or just seems to help in my case). It still happens sometimes, but then you can lock and unlock (press the button twice) and it is all good again.

Nope, just 1200... this is why it is weird... Maybe I did not let it settle as much, or is this kernel just sensitive?