[Q] CM7 RC1 video playback issue - Defy General

I used CM7 RC0 and video playback of all my recorded videos worked.
Now I have installed CM7 RC1 and some of my videos have issues during playback. The videos do play, however on certain times it freezes, (is skipping back and forward between frames) and then continues until the next freeze. Someone also mentioned something like this in the developers forum.
It seems that all videos recorded with CM7 RC0 and stored as .m4v file also work good in CM7 RC1.
All videos recorded with the original motorola software and stored as .3gp have the described issue since installing CM7 RC1.
Does anybody know a workaround for this issue?

It is a known issue and probably will be fixed in upcoming nightly..

arpith.fbi said:
It is a known issue and probably will be fixed in upcoming nightly..
Click to expand...
Click to collapse
Thanks for the quick response.
Are the current nightly stable enough for normal users, or should I wait for a next RC?

they r completely stable...sometimes there will be one or two bugs..but for normal use it is more than enough..as u can see this RC1 had more bugs than usual nightlys..
i find nightlies stable enough...and even if there r few bugs,they will be fixed in next nightly..

I think the developers of CM7 for Defy don't use the normal software release life cycle... so I wouldn't call the "last stables" or RC unless they wouldn't plan to add 720p recording.
A RC should be feature complete... so i would call it a gamma or delta version ;-)
I wonder why the RCs have so many bugs left... eventually released to fast... known problem for great companys like Microsoft :-D
Nevertheless this ROM is much better than the Stock versions from a Company with 19,000 employees... so thumbs up to the Developpers.

According to the first reactions in the developers forum the latest nightly (cm7-110627-1722-NIGHTLY-Jordan) should indeed solve my issue.
But now I wanted to install the latest nightly following the procedure described in the CM7 FAQ (number 3: How to update from previous versions?) and I encounter the following.
The FAQ says: Enter Recovery -> Custom Recovery
However I only see the following options:
-Latest recovery
-Stable recovery
-Stock recovery.
Is this changed? which option should I use?

-Latest recovery is the last test version of clockwork recovery which could have some issues.
-Stable recovery is the recomendet version which has no bugs but also none of the new features of the last test version.
-Stock recovery is the recovery from Motorola which shippes with the device.
So take the stable version and everything should work fine ;-)

The latest nightly 110627-1722, does indeed seem to solve all my video playback issues.

Related

All CM7 & CM9 Discussion

Since everyone is going crazy about not talking about it, I decided to create this thread to keep all discussion non-development related here for both Cyanogenmod 7 and Cyanogenmod 9. Keep in mind this is for discussion and should not be used to post this and that isn't working. Thanks!
rESERVED?HEHE
How Fix wifi problem on CM7 ??
reserved
reserved
Waiting..
Yeah, I have already downloaded the CM7.1.2 build from whitexp, some said it boot properly. but I want to hear more feedbacks and waiting for more patches to fix other know bugs... thinking twice if am gonna flash it or not.. but it's a great start... :good:
hope nano & white give a stable build soon
Flasing method as on NanoSurfers thread
Wipe data
Wipe cache
install
Wipe cache
Reboot
Report:
The colour swap is gone
All other problem from older builds are still present.
Data connection appears but no app can be connected
calling and messaging working fine with some Forceclose of messaging app
Sent from my Galaxy Y - A phone with Small Screen and Big Buttons
Atleast they have fixed the color swap bug, and soon other bug will be fixed.. let's hope for the best. What kernel did whitexp put on his latest release? Haven't tried it yet. :victory:
it is his kernel you can take a look at dev section
heres the link
http://forum.xda-developers.com/showthread.php?t=1762692
Sent from my GT-S5360 using Tapatalk
I got madteam's CM7 working on my phone. Indeed, wifi and bluetooth are not working. Also the interface feels a bit sluggish as the rendering is done in software mode. Color's fixed as per WhiteXP. I'd like to post some screenshots but I don't even know where CM7 saved them
wow new CM 7 release lots of improvement hope we got the full working soon
change
WiFi turn on but cant find any network & turn off auto after some time
Camera show white but take picture good
music not working even after installing other music apps
u can make call but can't receive any call but messaging work fine
other bugs are same as in older builds
data connection is working for me..... just on the tethering...
cm7
i flashed savie's kernel
wiped data
flashed nano build 0.63 (telephony completely works)
replaced some libs with whitexp's build ( colour swappiness fixed)
Great!!!
any one tried theme Chooser or getting force close
my cm7 bug:
3G data connection not working
i want to sent SMS but not sent
EDIT:
can SMS now
yash989 said:
any one tried theme Chooser or getting force close
Click to expand...
Click to collapse
i installed many themes if it force close just apply the theme u want nd reboot
Playing with my LiTTle "Y"
Originally Posted by yash989
any one tried theme Chooser or getting force close
Click to expand...
Click to collapse
it work fine for me
I cant make calls it stuck at dialing screen :crying:
edit
now works fine
amal das said:
I cant make calls it stuck at dialing screen :crying:
Click to expand...
Click to collapse
white is releasing new build after somedays with telephony fixed
till then use master-key build nd replace some files with whitexp build to fix graphics
i am trying to fix some bugs and i needed calling facility so i mixedup them...

[Q] SPH-D710 on CM11.0 - problems with camera, slow menu navigation

Unfortunately I don't have rights to ask on http://forum.xda-developers.com/showthread.php?t=2540250 ([ROM] CyanogenMod 11.0 - VILLUMINATI - December 7, 2013) so I'm creating new thread here.
Yes, I did my best to search the question, but cannot find anything related.
I used CM10, CM10.1, CM10.2 so I know what I'm talking about. I did NOT have the issues in these ROMs.
Current CM11.0 ROM dated by Dec. 7, 2013
Yesterday I've tried CM11.0 and found some issue which I cannot find mentioned anywhere.
1. Camera:
When I try to record video with [HD 720p|HD 1080p] resolution the picture is freezing after start of the recording and camera hangs.
I have to reboot my smartphone to get the camera (photo or video) working again.
I CAN successfully record video only with SD 480p resolution.
2. Slow Settings menu navigation (if compare with CM10, CM10.1, CM10.2).
Scroll is a bit slower, it's not critical.
Entering to a menu (for example About phone) is a bit slower - not critical but I don't like it.
Exiting from a menu (for example About phone) is MUCH slower - it's critical and very annoying.
Any idea ?
Did anyone have these issues ?
Currently I've downgraded back to CM10.2 (Andriod 4.3.1) where everything is fine.

[ROM] [24/12/15] [Unofficial] CM 10 for HTC Desire 300 [Public Beta]

Unofficial CM 10 for HTC Desire 300 (g3u)
device_htc_g3u v0.8b (24/12/15)
Traded stagefright bug for a new kernel
(no more stagefright and a freshly compiled kernel)
device_htc_g3u v0.77b3 (04/10/14)
Battery comsumption (hot)fix
(rls should no longer drain your device)
device_htc_g3u v0.77b2 (01/10/14)
Wifi is working
(wifi0 is forced into compliance)
device_htc_g3u v0.77b (25/9/14)
jellybean
(nom nom nom)
Full Disclosure
This is my first android project, so go easy on me.
Project Status
It's usable as a phone
So any willing beta testers are welcome to join the 'fun' and report further bugs.
Project !Status
mobiledata works but will drain your battery
(if you need to use it, reboot after switching it off)
libaudio is not fully functional
(stock has no mic unless in a call and custom has no speaker)
USB only works in mtp mode
(mass_storage mode appears to be incompatible with rmt_storage)
FM Radio not available
(required apps are currently not compiling)
Camera (front) appears unstable
(didn't bother to check what might be the cause)
TODO
[high priority]
fix libaudio (recording in stock or speaker in custom)
[medium priority]
fix libril -> mobile data drains the battery
[low priority]
enable apps2sd -> 2GB internal should suffice for the time being
check if cm supports proximity & light sensors -> they do work fine
fix mass_storage -> mtp is working
fix video recording -> it's a phone not a camcorder
fix video playback -> at least they are running
fix camera -> it's a phone dammit
find a better fix for wifi -> it works for now
fix graphical glitches
Disclaimer
Use at you own risk. This is a public beta and not meant for daily use. Please keep that in mind.
I can not be held accountable for any damage you might cause to your device if you decide to flash this file.
Requirements
HTC Desire 300 with unlocked Bootloader and custom recovery
(S-ON or S-OFF does not matter)
Download
Click me if you want the initial wifi free version (9d0a8fcca957d09dbaf306a1986d14dd)
Click me if you want to drain your battery (688c2779b4864ed9b568260477708049)
Click me if you like the stock kernel (1ba8a225bc7772f34f1e56bff51bfe27)
Click me if you dare (78bbcf5bf0eb26520efff6d49adac106)
Warning!!! If you are not a certified beta tester the zip file might explode upon extraction!!! You have been warned!
Installation
Enter recovery and begin by backing up your current system.
Next choose Wipe Data / Factory Reset from the main menu and Wipe Dalvic from the advanced submenu.
Last but not least use the mount submenu to format system.
Now use sideload or zip install to start beta testing this tasty jellybean.
Special Thanks
go out to anyone who has ever contributed something to a msm8225, ath6kl or htc related android project
device_htc_g3u
kernel_htc_g3u
Branch: Android 4.1.2
Version: 3.4.0-g12f638f
Config: g3u_defconfig
Toolchain: arm-eabi-4.6
Click to expand...
Click to collapse
compiled by 4m8
(My mind is a swirling miasma of scintillating thoughts and turgid ideas.)​
What are the requirements ? I guess I should use the only recovery available for the device ? and also, since we don't have s-off working for this device I think we have to flash the boot.img right ?
I'd recommend using the recovery from this build for the job. It won't crash unlike the philz version.
And no, you don't need to flash boot seperately. The only requirement is an unlocked bootloader.
S-ON only protects hboot and radio from flashing so you can safely install this release from the recovery.
Don't forget to backup your current system.
I'm downloading the files now, will test and report ASAP
Can i promote this in 2 german Forums? ist German translation available?
when do you think you will fix wifi?
HUGE THANKS IN FORWARD FOR COMPILING CM!
After the experiment:
the Rom stable and fast, but Wi-Fi does not work and do not contain FM radio
Front camera not working
I wish you success in your work and I hope you update the version of Android to be higher than 4.1.2
Thank you very much ..
4m8 said:
I'd recommend using the recovery from this build for the job. It won't crash unlike the philz version.
And no, you don't need to flash boot seperately. The only requirement is an unlocked bootloader.
S-ON only protects hboot and radio from flashing so you can safely install this release from the recovery.
Don't forget to backup your current system.
Click to expand...
Click to collapse
In which way will PhilZ CWM crash? will it still install the rom or not? will it brick my phone?
bassam_tayyan said:
After the experiment:
the Rom stable and fast, but Wi-Fi does not work and do not contain FM radio
Front camera not working
I wish you success in your work and I hope you update the version of Android to be higher than 4.1.2
Thank you very much ..
Click to expand...
Click to collapse
Ah yes FM. It's included in the custom libaudio that can't connect to the speaker.
Which I currently simply replace with the stock lib to make it work as a phone so it can be used to test battery consuption etc.
Sadly the cm apps used for fm won't compile for me. So even if I get libaudio working FM would still be untestable without non cm apps.
I'll add it to the todo once the libaudio trouble is resolved.
The wifi is an annoying issue. I manged to get it to load the drivers so the p2p0 socket gets created.
But it tries to restart it as STA which if my google fu is correct it shouldn't do, since this firmware does not need restarting.
The front camera is a curious bug. It works absoluetly fine for me until I point it towards my face.
So it's either a problem with the proximity sensor or the nasty htc camera tries some facial recognition crap and dies.
If I ever decide to logcat the camera I can tell you more.
Now for a higher version, don't get your hopes up. At least not from my side.
First I'll try my best to fix this up. Then I'll wait for htc to release the kernel so I can get a closer look at the configuration
for this device and maybe adjust it to make this rom even better. Then again the last kernel I compiled was 10 years ago for a gentoo install.
LukeHorizon said:
In which way will PhilZ CWM crash? will it still install the rom or not? will it brick my phone?
Click to expand...
Click to collapse
If you are quick it will install fine. So if you prefer to live dangereously, don't let me stop you
I don't know if it is only an error that is presented on my device. Or maybe it was updated since then.
But for me philz recovery by SPSPawn does boot into a dead state. If you reboot it will crash until a panic reset is triggered.
Actually it is allready crashed while you are in recovery. Therefore you are on a timer until the device resets or you decide to
take out the battery.
I had the same problem on my build and it was caused by cwm always ignoring the ueventd.rc I had prepared because I didn't know
I had to copy it to root and not to recovery.
I've never bothered to figure out which missing element of this script was responsible because I had to substitute it in any case.
But honestly, tell me. Why do you prefer philz? I'm allready (so far unsuccessfully) trying to port twrp. If you have a few good arguments
I might be willing to try compiling a fixed version of philz aswell.
Well i didnt want to use a pc right now ... A TWRP port would be amazing
Is mobile data working?
Can you make your recovery flashable via cwm?
LukeHorizon said:
Well i didnt want to use a pc right now ... A TWRP port would be amazing
Is mobile data working?
Can you make your recovery flashable via cwm?
Click to expand...
Click to collapse
It always tried to download the google language pack for my region until I aborted it. So, yes mobile data should be available.
You mean put the recovery into an update zip thingy, right. Well I could, but you will have used a pc before I'll find the time to upload it.
I'll keep it in consideration for the next update.
Well, atleast internet
When do you think you'll fix wifi?
Regarding to wifi, it will be fixed once it's fixed. Or if you prefer the usual response: When it's done.
This will happen either after or before libaudio is fixed. And that's about as specific as I can get.
Well, it was worth a try still thanks for your effort!
Okay, here goes.
First I tried installing the ROM with the PhilZ recovery because I already had it on my phone, didn't work. Gave me some kind of error (not sure about the error code anymore). Flashed your recovery, worked flawlessly. Now for the ROM.
It's pretty stable, I've had only one strange crash and that was in the first 2 minutes of using it so I don't even know if it counts. The additional CM settings panel works fine, quick toggles are ok, I haven't tried overclocking yet - I'll leave that to someone else. But I have found some bugs:
-proximity sensor not working (screen doesn't go black when you place it up to your ear)
-ambient light sensor not working (auto brightness doesn't work)
-video recording doesn't work
-the camera app glitched up the first time I tried to zoom (was fine afterwards)
-sometimes when going from portrait to landscape I got 1 second of weird graphical glitches
-signal indicator seems to be stuck at 2 out of 4 bars and doesn't move
Overall very nice, keep up the good work!
luxb said:
Okay, here goes.
First I tried installing the ROM with the PhilZ recovery because I already had it on my phone, didn't work. Gave me some kind of error (not sure about the error code anymore). Flashed your recovery, worked flawlessly. Now for the ROM.
It's pretty stable, I've had only one strange crash and that was in the first 2 minutes of using it so I don't even know if it counts. The additional CM settings panel works fine, quick toggles are ok, I haven't tried overclocking yet - I'll leave that to someone else. But I have found some bugs:
-proximity sensor not working (screen doesn't go black when you place it up to your ear)
-ambient light sensor not working (auto brightness doesn't work)
-video recording doesn't work
-the camera app glitched up the first time I tried to zoom (was fine afterwards)
-sometimes when going from portrait to landscape I got 1 second of weird graphical glitches
Overall very nice, keep up the good work!
Click to expand...
Click to collapse
I guess wifi isnt working for you right?
It's not working, but I didn't put it on the list since he already knows it's bugged.
Well, i'll try today
Lets see what happens
Anyway, forgot to unpack the file ... GApps come with it?
SOOO, booting went fine, working like a charm... quicksettings page not available, quicksettings bar is working properly
Mobile Data works flawless, and i guess the rest is just fine
German language worked instantly
it feels way faster then Sense, a HUGE Thanks for you, makes me actually like that phone again ...
I'd like to promote it in German forums if i WiFi is fixed in near future
regards!
LukeHorizon said:
[...]
GApps come with it?
[...]
German language worked instantly
it feels way faster then Sense, a HUGE Thanks for you, makes me actually like that phone again ...
[...]
Click to expand...
Click to collapse
No, you have to get gapps on your own. Since there are multiple options you can choose for yourself. But if you did not format system,
as I've mentioned in the install instructions, chances are high that google apps did get picked up by the install script.
I am not sure if it can take them from the stock rom but it can and will take them from a cm rom and keep them on reinstall.
(I am really not very pleased by this behavior!)
I also should have mentioned that the primary language is decided by the simcard. (Which is annoying since I prefer english in any case)
Randnotiz:
Es freut mich das ich Dir den Spass am Gerät zurückgeben konnte.
Natürlich darfst Du es in deutschen Foren weiterverbreiten sobald die gröbsten Fehler behoben sind.
Einzige Vorraussetzung ist, daß Du es nicht als Deine Arbeit ausgibst.
luxb said:
[...]
-proximity sensor not working (screen doesn't go black when you place it up to your ear)
-ambient light sensor not working (auto brightness doesn't work)
-video recording doesn't work
-the camera app glitched up the first time I tried to zoom (was fine afterwards)
-sometimes when going from portrait to landscape I got 1 second of weird graphical glitches
-signal indicator seems to be stuck at 2 out of 4 bars and doesn't move
[...]
Click to expand...
Click to collapse
Wow. That's much more broken than I expected it to be. Kudos.
Regarding the sensors. I currently am using the stock lib. And logcat let's me assume that they are working as they should.
(i.e they don't crash or drift into madness afaik)
Maybe the stock lib doesn't play well with cm, or you are expecting features from cm that are not implemented.
I will definetly try to compile a working sensor lib in the future, so I guess we'll see....
Camera is also just the stock lib for now. So it's no surprise that somethings might be acting up.
I need a lot of research into that subject before I can specify the requirements for the camera in my boardconfig.
The graphical glitches are rather minor and can be ignored for now. I am aware they exist.
But for now I'd rather focus on the more prominent broken features.
Like wireless for those of us that can't or won't use mobile data. (I belong to the 2nd group)
I noticed the signal indicator aswell. but that should be a problem of the radio compatibility.
We can't flash radio and I'm using the stock libril as the radio interface which should give maximum compatibility in theory.
Of course it doesn't irl... typical -_- (I hate you, Murphy!)
Sidenote:
Why did you remove your avatar? I really wanted to make some "stop trying to kill spoderman" remark...
@all:
Does anyone have any clue how to use the mock locations for gps? They are enabled, but so far I couldn't find any way to set them to a specific location.

Weird CM 11 and CM 11 based ROMS issue with calling

Hi fellow forum members!
I recently found great ROMS at Kevin's web storage. I tried them all and they work amazingly well except for one thing. When I make a call for a first time after a clean boot everything is fine. But when I make another call I can not hear anything nor the person I'm calling. After a reboot I have one shot again. Each time I want to call I need to reboot my phone. It only happens on CM 11 based GPROJ ROMS. Anyone encoutered this issue before? Any suggesting? Solutions?
Thanks, Zunex
nuraH6 said:
Quote:
Originally Posted by ShorelineDroid
Can anyone confirm the new nightly still has the call issue?
Alright, so after chatting with a CM maintainer we've been able to narrow it down to an upstream CM issue along with the phone not going into deep sleep. So, point is, no matter how many of our commits I revert it still won't fix the problem until CM fixes it on their end. I'm told it shouldn't take too long and will keep an eye on CM gerrit to see when an update is pushed into their code to fix these issues. So its not just PAC it's an LGOG gproj that sync'd to CM after 10/4.
Until the issue is resolved you can use the nightly 10/4 as it doesn't have the dialer or deep sleep issues and I will update when I hear more.
Click to expand...
Click to collapse
Same problem here on PAC-man ROM
I am facing the same issue with 10/13 nightly build. Its so frustrating to miss out so many important calls due to this call issue. They pulled back their 10/16 and 10/17 nightly build citing some major issue with the builds. Expecting a build asap with fixed call issue.
I had same problem. I was going back to CM snapshot-M11. This doesn't have call problem.
Is it fixed yet? Any news on this?
Updated today to cm-11-20141025-NIGHTLY-e975 but the calls bug is still there...
So, what should we do to solve this?
Fotonic said:
Updated today to cm-11-20141025-NIGHTLY-e975 but the calls bug is still there...
So, what should we do to solve this?
Click to expand...
Click to collapse
Thanks for the heads up. I don't know. I really don't wanna go back to stock because of dsp manager but this bug forces me to. Hope it gets fixed soon.
Reading This I found the solution to audio-caf problem. The solution is replace in system/lib/hw the library audio.primary.msm8960.so for a working one, I used the library from official M11 and now everything is OK. Attached is the library I used.
I installed the stock rom after this issus. I think the stock rom has a good battery life.
cabe2001 said:
Reading This I found the solution to audio-caf problem. The solution is replace in system/lib/hw the library audio.primary.msm8960.so for a working one, I used the library from official M11 and now everything is OK. Attached is the library I used.
Click to expand...
Click to collapse
Confirmed working!
Thanks cabe2001.
Does anyone have the skills to create a flashable zip that overwrites audio.primary.msm8960.so with a working version?
Is it as simple as deleting everything from a standard CM zip?

List of roms with "Novatek NT36672" touch screen module support so far.

UPDATE: There is a telegram group with latest nightly builds of genom kernel, they are mostly stable, there may be a couple of ussues with some of them (like phantom touches or random battery inefficiency), however you can find kernels that support our touch panel in android pie, and oreo roms, and they run butter smooth compared to stock rom, (thank you rama982 and all contrubutors to Genom kernel). Just download a kernel build you like, and then flash it after the installation of rom. genom_ci
It has been an issue for a long time, since Xiaomi refuses to release kernel sources for this module (or so i been told), anyways, many people encouter the issue with touch screen that doesn't work after flashing custom rom (screen flickering, response lag e.t.c). This issue was brought up in this thread, however there is no answer to a question that excites most of "novatek" owners that are here - "what can i actually install of all roms". I decided to make a list of roms that happened to avoid this issue, i hope this will help users like me, so they don't have to spend literally weeks stalking, testing, looking around at all sorts of places only to find another rom that doesn't work.
1. This is the easiest one, all MIUI roms that are available for our device are working flawlessly, official global roms, custom ones, they all work (i personally prefer Revolution OS MIUI 8.10, since it has an option for the chinese bloatware and spyware to be removed, and i find it the fastest one).
2. Almost all nougat roms ( the ones that are based on android 7.1, (and maybe 7) ). Or at least 95% of them, i had issues with some of them, but it's okay that some roms are less stable than the others, you will have to find what works best for you.
3. As far as i remember, all roms based on android 8, 8.1 DO NOT work with our touch screen, except the ones that were mentioned here.
4. Who wan'ts a piece of a pie? I think everyone, but not all of us can get it, since there is only a couple of pie roms that work with our panels:
Aosp extended 6.0 (only 28/10/2018 release so far, developers told that they will fix it but they didn't so far, this release is pretty stable and snappy though).
Dirty Unicorns 13.0
(I really like the esthetics of this rom, and a philosophy that stands behind it, but release is missing some important features for me personally.)
lineage-16.0-20181115 (As stable as aosp extended, or even more. Perfect rom for a new user that doesn't care about a lot of features, and just wants to do basic stuff without any bugs and crushes) (IMO)
GZOSP from Here, it's even more simple compared to lineage, but a a bit less stable.
Thanks to rama982 we have Nitrogen Os, it works fine, things are strating to change. (Live a like to Rama982).
This list is potentially suitable for EBBG touch panel users, but as i have no device on hands to test it, i can't say anything about it. If you are wondering wich type of touch screen you have, you can dowload AIDA from play store, or any other "sysinfo" type of app.
That's all. I hope this will help you, it's the smallest thing i can do, as i love the community of this place even more than my morning coffee.
P.S. If i missed something, you can comment down below, or send a private message, we all make mistakes.
vince with novatek panel user here. Info here is really helpful. I'm trying out AEX 10-28 now. i tried the latest build and i got a flashing screen on bootup.
Setesh73 said:
vince with novatek panel user here. Info here is really helpful. I'm trying out AEX 10-28 now. i tried the latest build and i got a flashing screen on bootup.
Click to expand...
Click to collapse
Try LOS16, Havoc, or Bootleggers - or try the latest Genom kernels.
I tried out AEX 10-28 for a couple of days. i went back to xiaomi eu beta for full screen navigation. i also opted for genom eas nightly for miui. i think i'll stick with this setup for a while.
Can i use genom kernel nightly on pixel experience rom to support novatek panel?
jharone23 said:
Can i use genom kernel nightly on pixel experience rom to support novatek panel?
Click to expand...
Click to collapse
i got blinking screen same as aex when i tried pixel experience with genom.
Setesh73 said:
i got blinking screen same as aex when i tried pixel experience with genom.
Click to expand...
Click to collapse
I flashed just now the latest build of pixel experience on my device with genom nightly build for pie roms and it worked... No blinking or screen and the touch is working flawlessly, still checking for small bugs
Thanks for the thread and detailed info!
But Camera crashes on DU, any fixes you guys got?
drmjp93 said:
Thanks for the thread and detailed info!
But Camera crashes on DU, any fixes you guys got?
Click to expand...
Click to collapse
Try gcam
DarthJabba9 said:
Try gcam
Click to expand...
Click to collapse
Just gave it a try, it's too crashing.
drmjp93 said:
Just gave it a try, it's too crashing.
Click to expand...
Click to collapse
All gcam builds are crashing?
Have you tried this one: https://f.celsoazevedo.com/file/gcamera/GCam_5.1.018_by_SerJo87_1.6RC2_test4d_fixed.apk
DarthJabba9 said:
All gcam builds are crashing?
Have you tried this one: https://f.celsoazevedo.com/file/gcamera/GCam_5.1.018_by_SerJo87_1.6RC2_test4d_fixed.apk
Click to expand...
Click to collapse
Yes tried many, including this.
It crashes as soon it is launched.
Try Open Camera... Its open source and pretty good! I use it daily.
Sent from my Note 5 / 5 Plus using XDA Labs
In case anyone is interested, nitrogen os is working great on my ebbg display
i've tried pixel experience like @jharone23 said and it's working fine. i also installed genom nightly and it runs smooth. i think they worked out most of the kinks for novatek panel. i haven't tried the 12-31 build of the rom yet. gcam v5 works great. i also installed gcam v6 for better back cam low light and i'm satisfied so far. no problems with gps and lte. no network drops on wifi and data. i have mine rooted and installed kernel aduitor, also installed blex and youtube vanced from magisk repo. google backup works like a charm. played ro mobile for 4 hours straight on wifi. everything is great. note for benchmarkers, you would get lesser score in antutu compared to xiaomi eu rom with genom. i used to get 84k score with that setup but with p.e. and genom i only get 80k with performance setting in kernel aduitor. overall a 4/5 stars for user experience just because i was accustomed to full screen navigation in mi eu rom. A 5/5 stars in stability kudos to p.e. developers and genom. i won't be flashing any other rom for quite sometime as my current setup is stable enough as daily driver. maybe t.s. could include rom in the list. thanks jharone23 for the tip.

Categories

Resources