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.
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.
I've been trying to figure out what is the best ROM for Note 2 N7100, I have tried a few below but even the stable versions have some issues.
1) Paranoid Android
-4.45 [STABLE] (Screen black out unexpectedly, Exchange Service Issue, System UI failing unexpectedly)
-4.43 [STABLE] (Screen black out unexpectedly)
2) CYANOGENMOD
-11 [SNAPSHOT M11] (Screen black out unexpectedly, Exchange Service Issue, System UI failing unexpectedly)
-Nightly Build (They are nightly so can't complain)
NOTE: CM 11 NIGHTLY (December 3, 2014), that build is very stable as compared to other Nightly builds.
3) SLIMKAT
4.4.4 Build 8.0 [OFFICIAL] (Sync Issue, Apps purchased in Google Play not downloading, Wifi Issue)
4) DN4
I know this is a very new ROM and they haven't released a stable version, but even after flashing the patch, it throws a lot of error.
5) PAC MAN
Nightly Build (August 25, 2014) This ROM I found very amazing, high in performance and awesome battery life. But it has the same issues as CM & PA: Screen black out unexpectedly, Exchange Service Issue, System UI failing unexpectedly.
6) OmniROM
I didn't get a good chance to go through this ROM, but it got stuck at sync as well. So removed it.
One thing very common in all these ROM's is when charging the phone in Power Off mode, the battery Icon is stuck and the phone hangs. Although, the phone is charging, but it won't start through the power button. You'd have to remove the battery and put it in again.
Any suggestions about a very stable ROM for N7100? (No TouchWiz! )
P.S: This is my first post, so please excuse any errors.
Hello,
I've been using Official CM 11 for a while because of the OTA Updates and less bugs, but I have a problem.
(asked on CM Forum and got no answer)
There is a bug in video which is taking place when I'm opening or closing an app. It's like there is no "VSync", the image gets teared.
Tried Agni Kernel, no succes.
Does anyone know why is CM 11 doing that? It happens no matter what I try. Thanks in advance!
Hi Guys!
I already posted this in the specific SM-G935F thread, but maybe my two problems are not device-specific and some user of other phones had this issues or have an idea what cause my problems.
After searching in the internet and many forums I think that I am the only person in this world, who have this problems.
My Phone: Samsung Galaxy S7 Edge (SM-G935F/hero2lte)
Important: These two problems don't occur with the stock rom and everything worked.
I tested this by installing the original samsung rom (Android 6 and 7).
Also with Superman-ROM these problems don't occur.
Only with LineageOS and RessurectionROM (based on Lineage) I have this problems.
What I did (or not):
- ODIN: Installed latest version of TWRP
- TWRP: Installed SuperSU 2.83 and "dm-verity-disabler"
- TWRP: Installed latest LineageOS-Build (Full Wipe) + latest GApps (Pico) + addonsu-arm64
- I did not install any other apps in Lineage
- I did not change any settings
-> I have a clean version of LineageOS on my phone.
Problem 1:
During calls, when I turn on the loudspeakers, I can hear the other person, but I can not be heared by the other person anymore.
Then I turn off the loudspeakers and everthing switches: the other person can hear me now, but I can not hear the other person.
When I'm turning the loudspeakers again it will switch again (I hear the other, I'm not heared).
And so on, and so on ...
Problem 2:
Screen rotation from portrait to landscape mode ONLY works with the gallery and the icons of the camera.
In any other app (Browser, Messages, Settings ...) the screen stays in portrait mode.
And yes, I checked in the settings if screen rotation is active.
I found a solution with the app "Rotation Lock Adaptive", which automatically rotates the screen how it should be.
But that is unsatisfactory, I don't want a additional app to do core-function.
I don't believe the problems occur due hardware issues or what do your think? Beeing on stock rom everything works fine.
Greetz,
Isenberg
Really nobody has an idea what could cause my problems?
Isenberg said:
Really nobody has an idea what could cause my problems?
Click to expand...
Click to collapse
I have not
I experience the exact same problems. Flashed lastest stock-firmware (excluding system & data) and the latest official lineage os.
Sometimes rotation works, but most the time not.