Hi to everybody,
I'm new to defy world, and I don't understand this strange issue...
Is it fixed ?
Is it related with the radio (so with latest official motorola ROM flashed)?
Thanks
sent from my NS
You are not very specific with your request/question but the Defy is well known for connection drops net only and telephony as well, which can only be recovered by a reboot. It is not fixed and probably never will be, because the problem is most likely located in the closed source RIL.
A few people reported they never had the bug with cm7_euroskank_v121203, walters rom and whiterabbit. But I cannot personally confirm that. I tried the euroskank version and it seemed to behave, but that was only a short test.
Other than that there is a workaround which works by autorebooting the system when you get a socalled bp panic (forgot what that means). It is integrated in most CM7 roms and CM10/10.1 but those require sim pin so the reboot is not as practical as in the CM7 builds.
Good luck.
thank you
sorry for bad english
whether this is the OTA official update but as usual update is like custom update or rom and worst update till today.
it have too much bugs which i and one of my collegue faced are-:
1-App themer crashing as click it crashes i did factory reset but not success found problem on two yureka mobile with 5.1.1.
2-Battery drain like hell worst situtation then previous rom need to charge 5-6 time in 8 hours cant use for watching movie withoutcharging. old solution uses but not works
3-none app locking software working even with enabling with usase aceess
4-mobile hangs on setting if you click two times any setting by mistakes then self reboot
5-camera gives much redness while clicks with flash.
still using i think ROM is not stable will report more bugs
please suggest
i have a samsung galaxy grand 2 SM-G7102. I had been peacefully running the official rom that came along with the phone until i decided to root the phone. Tweaked a lot of settings here and there without knowing what was happening. unfortunately one day rebooted my phone and many of the system apps were lost - keyboard phone everything. so i flashed a custom rom and fixed it.
CURRENT SPECS- cyanogenmod version - 12.1-20151026-UNOFFICIAL-ms013g
android version - 5.1.1
kernel version -
[email protected]
[email protected]#1
Thu Sep 24 23:04:02 ICT 2015
now everything works except calling. I call someone but i cant hear anything and neither can the guy i called. same when someone calls.
I didnt exactly know what info to give so i put it all.. will provide anything else needed.
looking through the apps i discovered an app named "In-call interface". its 0.00B in size. could this be the problem?
In-call interface
com.android.incallui
Version 5.1.1-90cd289875
hoping to fix this soon... stock rom was complete trash compared to CM
So I found that there is a nougat alpha build of cm 14 here.
https://androidfilehost.com/?fid=24591000424966343
I claim no responsibility for the rom I just found it and wanted people to know that there is a build available.
Currently there are no known working and not working details of the rom so comment with details if you end up flashing it.
Android4thewin said:
So I found that there is a nougat alpha build of cm 14 here.
https://androidfilehost.com/?fid=24591000424966343
I claim no responsibility for the rom I just found it and wanted people to know that there is a build available.
Currently there are no known working and not working details of the rom so comment with details if you end up flashing it.
Click to expand...
Click to collapse
Wouldn't bother trying it yet; leave it to devs, but if you want the updated one is here https://androidfilehost.com/?fid=24727369092696651 thanks to codeworkx and genesixx
Android4thewin said:
So I found that there is a nougat alpha build of cm 14 here.
https://androidfilehost.com/?fid=24591000424966343
I claim no responsibility for the rom I just found it and wanted people to know that there is a build available.
Currently there are no known working and not working details of the rom so comment with details if you end up flashing it.
Click to expand...
Click to collapse
I gave a slightly older version (9/14 build) a go last night.
Working: WiFi, cellular data, texting, GPS, NFC (as far as I could tell)
Not working: Camera, audio/video playback of any sort, phone (I could make and receive calls but hearing anything was a no go and the dialer app would randomly force close)
I also experienced the issue where if I flashed the ROM and Gapps in one go via TWRP I'd end up in a loop once the ROM booted where it'd never let me sign into my Gmail account. It'd just boot me back to the WiFi setup. Flashing the ROM itself and booting into it then flashing Gapps after worked fine. Was able to sign in to my Gmail account with no issues at all.
I could live without audio/video playback since I have a backup phone I could use for both but being unable to listen or speak when using the dialer app to make and receive calls is currently a "pass" for me since I'm waiting on some important calls. So if you absolutely need to use your phone as an actual phone wait til the issues there are fixed.
bangishotyou said:
I gave a slightly older version (9/14 build) a go last night.
Working: WiFi, cellular data, texting, GPS, NFC (as far as I could tell)
Not working: Camera, audio/video playback of any sort, phone (I could make and receive calls but hearing anything was a no go and the dialer app would randomly force close)
I also experienced the issue where if I flashed the ROM and Gapps in one go via TWRP I'd end up in a loop once the ROM booted where it'd never let me sign into my Gmail account. It'd just boot me back to the WiFi setup. Flashing the ROM itself and booting into it then flashing Gapps after worked fine. Was able to sign in to my Gmail account with no issues at all.
I could live without audio/video playback since I have a backup phone I could use for both but being unable to listen or speak when using the dialer app to make and receive calls is currently a "pass" for me since I'm waiting on some important calls. So if you absolutely need to use your phone as an actual phone wait til the issues there are fixed.
Click to expand...
Click to collapse
Yeah earlier builds didn't have the audio policies fixed; now they do. Obviously the camera is being worked on
CraigHardy said:
Yeah earlier builds didn't have the audio policies fixed; now they do. Obviously the camera is being worked on
Click to expand...
Click to collapse
i tried the most recent build (v....29) and the phone was still giving no phone or audio. is the newer build giving the same symptoms for you or only the ....21 build has functioning audio?
There is already a thread on CM14 for the H811 here:
http://forum.xda-developers.com/tmobile-g4/general/cm14-t3464339
ashtreylil said:
i tried the most recent build (v....29) and the phone was still giving no phone or audio. is the newer build giving the same symptoms for you or only the ....21 build has functioning audio?
Click to expand...
Click to collapse
Make sure you have updated your H811 to 20o. 20i isn't working very well with CM14 at this point.
AngryManMLS said:
There is already a thread on CM14 for the H811 here:
http://forum.xda-developers.com/tmobile-g4/general/cm14-t3464339
Make sure you have updated your H811 to 20o. 20i isn't working very well with CM14 at this point.
Click to expand...
Click to collapse
i thought i was forgetting something, thanks:highfive:
[ROMs] Source for LG H811 (T-Mobile) CM-14 Nougat
I have begun building CM-14 (Android AOSP 7.0.1, Nougat) for H811 and will post ~weekly builds here. The builds are from the CyanogenMod and Muppets (vendor proprietary) sources on github. This I will do until a developer at CM takes on the task of creating official "nightly" builds for LG H811 CM-14.
Please report problems here and I will forward them on to official CyanogenMod devs.
2016-10-04: Don't expect great things right away. On first builds the phone app crashes continuously and it will soak the battery dry in a few hours.
2016-10-07: The build today is working relatively nicely. Earlier problems may have been partly my error. I've been running today's build all day without major problems. Battery drain is higher than CM-13.0 version but not terrible. I'm planning on running this ROM over the weekend to see what bugs pop up. Only two so far – the external sd access as reported earlier; and flakey navigation button editing. Give it a try!
Since the development thread is closed by OP request( sad but true ), and personally building a "port" of the ROM, i'm glad to help everybody as i can, with this thread.
It doesn't mean to be a development thread since i only build and implement some changes, but just to share comments, issues( like xposed one ) or just ideas to people who own this device ( CN or ROW ).
As a reminder you can find my builds here: LINK or just use OTA function in ROM.
And a big thanks to @frantisheq and @Electry for the works on CM13, and for the next, CM14.
reserved
Are someone try to flash Vibe Z2 (NON PRO) with this ROM?
don't do it, you will probably brick the phone.
K920/Z2 PRO only
Uploaded new build!
Should have Dec 5 patches, have a nice day
Try to install the latest build together with xposed. There is a boot loop with CM logo...... It seems to me there was such kind of problem......
That should be fixed by cm ? . Will apply the xposed fix in next build.
Thanks to inform me about this!
Tapatalk
updated build, with xposed patch, hoping now works fine
The latest build works fine for me. I installed it with xposed.
Hey @malaga82
I have a strange feeling that the new ROM is worse in performance compared to the previous build. It has way more stutters and sometimes the system UI resets and changes my wallpaper to the stock one. Anyone else facing such issues?
Saamyo said:
Hey @malaga82
I have a strange feeling that the new ROM is worse in performance compared to the previous build. It has way more stutters and sometimes the system UI resets and changes my wallpaper to the stock one. Anyone else facing such issues?
Click to expand...
Click to collapse
Could you please provide more details about this behavior and I try to reproduce it? Now I have not such kind of problem. But I can say that the UI sometimes has strange behavior. For example, the horizontal size of quick settings can be more widely than the size of the screen.
maybe it's something related to CM repo's and they will fix "soon".
give some days to see if they fix anything, i'll provide a new build.
In additional to my previous report I would like to add that the latest build cannot hold loading. At the previous build from 16 Nov I can run at the same time a navigation application and a video registration application. Now I cannot do the same because the device is rebooting due to overheating. I tried to figure out what is going on and found that the high limit of CPU0 temperature is set up to 85 C (it seems to me it is low....) and I cannot change it – try several tuning tools. And it is not only one reboot – there are several reboots….. After its a Bluetooth pairing was lost….. And I can repair a normal work only wipe cache & dalvik through TWRP and pair a Bluetooth once again…..
i'd like to have more feedback if possible.
i'm thinking to try to build with the "old" kernel that have cpu voltage control and other features i included times ago.
atm we are a bit stuck with development.
malaga82 said:
i'd like to have more feedback if possible.
i'm thinking to try to build with the "old" kernel that have cpu voltage control and other features i included times ago.
atm we are a bit stuck with development.
Click to expand...
Click to collapse
What information could I provide to you to help?
i just want to know if someone else have that overheating issue
Could you please prepare a build with "old" kernel? Who does not face the overheating problem can stay on the previous one
Solved games issue.
Hello!
Sorry for my English, I from Russia.
On roms later CM 13 2016.03.07 in file: build.prop, increase the value: dalvik.vm.heapsize= from 512m to 768m. This led to the errors in game Real racing 3 (insufficient free memory, missing textures, game crashes). With value 512m games work fine.
If install Adreno drivers from ROM CM 13 2016.03.07, game Gear.club also work fine. The difference can be noticed immediately after starting the game.
I also sent this message to frantisheq.
Happy new year!
Solved games issue.
Additional information to the previous post.
I was looking the file: default.prop, and the parameter ( dalvik.vm.dex2oat-xmx ) is set to =512m. System parameter ( dalvik.vm.heapsize=768m) overlap kernel parameter. Possible, if rebuild kernel with the value 768m, all be fine? I don't test this.