Related
Hello.
This is where you can look at the tutorial and get the files to install if you feel like jumping into it ...
ICS Step by step and files
Note: if you do flash this and it hangs at the boot screen, pull the battery and flash it again and it should work. Some have had to do it 3 times.
I take no credit for this ROM and full props go to the developers of the above post and all those working to make this happen.
First the look and feel of ICS is nothing short of superb. The speed as of now is similar to all the other ROMS I have tried with a little chop here and there but nothing major.
Yes lots of little issues and items that do not work like the camera and GPS but not a huge deal for me so I am willing to stick to it.
Battery so far is decent. 13 hours and 43 min. on the first charge to calibrate and sitting at 24% still. This included allot of playing with the phone and reboots to test jigs
As for the issues that are somewhat bothersome, they include the following.
1. No home or search button. I know same as usual when installing an i9000 ROM but the key mappings from the GB ROMS does not work.
2. BLN (issue all around) will remain lit until you wake the phone to get the notification.
3. They had to do some funky stuff to get 3G to work so it lags to start. Not a huge deal cause it does start and remain working.
I will be continuing to use this ROM and hopefully everything will be working soon (these guys are flying. Also I have been told that the folks over at Glitch are already working on the kernels for the ICS port so that is promising as well.
If there are any other out there running this on our phone chime in with your thoughts or fixes if you have any.
Thanx
Bucky
Thanks for starting this thread. Can't wait to hear about your progress.
Alpha 7
Hey here is the update ...
Installed the Alpha 7 update today and I have to say this rom is fantastic.
1. Camera is fixed and works like a charm.
2. GPS locked in seconds and accurate indoors!! Big improvment over all other roms I have used.
3. HW Acceleration is fixed and working from what I can tell
4. You Tube is fixed and can watch video
Still on the not working list
1. Can not plug the phone in while off as it just restarts. this is a work in progress and known issue
2. Can not record video
3. Will not read a SIM card for contacts and so on (thank god for Google sync)
4. Still no home or search buttons (I think I may need to work on that on myself unless a kernel is released)
SO my review so far ...
No real issues with the general use of the phone. Text, phone, email and web are solid, I have installed apps from the market with no issues and not one FC yet. Battery life is good and nothing is taking over. I have been able to use the phone all day and still have lots left over before going to bed and plugging in. I have not been through a full battery as of yet but that is what I am working on now.
Memory - Last I looked I had 174MB of memory remaining which is the highest I have seen.
ICS is really smooth and fast while moving around. I am going to continue to play with it and report back here for everyone.
I don't use a whole lot of apps so there won't be much regarding those.
Thanx for stopping by and I will post pics when I can.
Bucky
Nevermind
Sent from my SCH-I500 using XDA App
Thanks for the update. From your review, it sounds like an awesome rom. Can't wait to try it but need them to fix the video recording first. Although I might just cave and try it out just to see what the fuss is all about
Can always restore my current setup... lol.
Update ...
been getting the SOD today and not sure why, I mentioned above that the HW acceleration was working, I misunderstood and it is not fully working yet.
I found that the system partition is very small. There was an update which required copying libs and there was not enough space left to do this (2MB). Not too sure if this is due to coming from MIUI or just a ROM issue.
Alpha 8 was released but had quite a few issues so not flashing that one.
Daily use has been great so far (except for the SOD) with no reception or data issues.
I am still working on the home and search buttons but I think that will get fixed with a kernel update. I tried the keymap file but these buttons do not even register in recovery so I get nothing in the ROM either.
More to come ...
Haven't tried this (likely won't as I need the phone for work) but buck have you tried the manual key fix - some directions in our thread on putting on Darkys 10.3.
Sent from T959D running Miui
Yup been there done that no go
Sent from my GT-I9000 using XDA App
Hey buck , was doing some searching in teamhacksung's thread about their ICS port, and someone suggested to change the following and then the key mapping for our phones will work properly. Not sure if the file system is the same for both, but definitely a bit of info if it isn't!
All you have to do is change this part on**arch/arm/mach-s5pv210/mach-aries.c*
*Original**(line 1216~1221)
static const int touch_keypad_code[] = {
#if defined (CONFIG_SAMSUNG_GALAXYS) || defined (CONFIG_SAMSUNG_GALAXYSB)
KEY_MENU,
KEY_BACK,
*0,*
*0*
----------------------------------------------------------------------------*
*Edited*
static const int touch_keypad_code[] = {
#if defined (CONFIG_SAMSUNG_GALAXYS) || defined (CONFIG_SAMSUNG_GALAXYSB)
KEY_MENU,
KEY_BACK,
*KEY_HOME,*
*KEY_SEARCH*
Sent from my GT-I9000 (T959 mod) using XDA App
Thank for the input. After flashing bata 1 all the buttons are working. More to come: )
Sent from my GT-I9000 using XDA App
Hey, have a telus fascinate too. Know how to flash and all that fun stuff. Just don't fully follow where you make the changes for key mapping...if you could just guide me in the right direction, I can figure the rest out...
changes in the kernel zip? the beta zip? after flashing? something completely different?
thanks a lot!
There are no changes to be made with this ROM, they are built in. Just flash and all good.
I will post update tonight after work.
Sent from my GT-I9000 using XDA App
yeah sorry realized that immediately after posting / flashing to the new rom.
have you tried out BT audio? I can connect to different devices but audio won't stream
havoksupertwit said:
yeah sorry realized that immediately after posting / flashing to the new rom.
have you tried out BT audio? I can connect to different devices but audio won't stream
Click to expand...
Click to collapse
There are allot of BT related posts in the QA. I personally do not use any BT but I do have a headset that I will try when I get home.
Seems to be a battery drain issue too as my phone is now dead but I have not calibrated so we will see after I do that.
bucknetbucky said:
Seems to be a battery drain issue too as my phone is now dead but I have not calibrated so we will see after I do that.
Click to expand...
Click to collapse
Calibrated my phone this morning. Heavy use today configuring everything but about 52% now (sooo 5 hours or use?)
Why god! Whhyyy!!
bucknetbucky said:
There are allot of BT related posts in the QA. I personally do not use any BT but I do have a headset that I will try when I get home.
Seems to be a battery drain issue too as my phone is now dead but I have not calibrated so we will see after I do that.
Click to expand...
Click to collapse
AT LEAST YOU GUYS HAVE IT RUNNING!!
I am having a hell of a time trying to get it to work. I have tried so many different ways to get it up and running but no luck.
I've tried installing it from MIUI 3 times but all I get when trying to boot into ICS for the first time is a Black Screen after the FuguMod boot screen.
The funny thing is that the 4 soft buttons at the bottom light up still.
So I then decided to try the JVT way:
-Flashed JVT DARKYROM (ODIN)
-Lagfix OFF
-FULL WIPEs (factory reset, cache, dalvik)
-FLASHED CM7.1 STABLE
-FULL WIPEs (factory reset, cache, dalvik)
-Flash ICS BETA1
-Flash kernel
-FOR THE SECOND TIME:
-Flash ICS BETA1 AGAIN
-Flash kernel AGAIN
Same issue, black screen after the FuguMod boot screen, buttons still light up.
So i tried a couple more times in a few different ways based off what I have already tried, but this time, before booting into ICS for the first time, I installed the 'Superuser-3.0.6-efgh-signed.zip' package.
Same issue. I'm not having any luck here.
iwebsource said:
AT LEAST YOU GUYS HAVE IT RUNNING!!
I am having a hell of a time trying to get it to work. I have tried so many different ways to get it up and running but no luck.
I've tried installing it from MIUI 3 times but all I get when trying to boot into ICS for the first time is a Black Screen after the FuguMod boot screen.
The funny thing is that the 4 soft buttons at the bottom light up still.
So I then decided to try the JVT way:
-Flashed JVT DARKYROM (ODIN)
-Lagfix OFF
-FULL WIPEs (factory reset, cache, dalvik)
-FLASHED CM7.1 STABLE
-FULL WIPEs (factory reset, cache, dalvik)
-Flash ICS BETA1
-Flash kernel
-FOR THE SECOND TIME:
-Flash ICS BETA1 AGAIN
-Flash kernel AGAIN
Same issue, black screen after the FuguMod boot screen, buttons still light up.
So i tried a couple more times in a few different ways based off what I have already tried, but this time, before booting into ICS for the first time, I installed the 'Superuser-3.0.6-efgh-signed.zip' package.
Same issue. I'm not having any luck here.
Click to expand...
Click to collapse
OK so here is what I did ...
Started from MIUI 1.11.18
1. Do a nandroid backup
2. download all the files to the SD card. This includes the ROM, Kernel and super user fix
Links:
Kernel:http://ice-cream-sandwich-sgs.googlecode.com/files/FuguModICS_GT-I9000_update.zip
ROM:http://ice-cream-sandwich-sgs.googlecode.com/files/ICS_4.0.1_r1-Beta1-i9000.zip
Super User:http://ice-cream-sandwich-sgs.googlecode.com/files/Superuser-3.0.6-efgh-signed.zip
3. Boot to recovery and do factory reset, wipe cache and davlik cache
4. Install the Kernel first and reboot now
5. Boot into recovery factory reset and wipe cache and Davlik and Install the ROM then reboot now
6 Boot back to recovery and install the Kernel again with out the wipe
7. If after reboot you do not have root then boot to recovery and flash super user fix
8. reboot and it should be working at least it was for me
It seems to me that you are missing the first flash of the kernel before the ROM. It sets up the file system from what I gather
Note: If needed flash the kernel and rom then kernel again with all the wipes as mentioned above.
I know there are allot of folks having issues getting it to run. Not too sure if it was the way I installed MIUI that might have made the difference.
My battery is charging now so I can calibrate it and see how it goes after that (it drained pretty quick today) lol.
I hope you can get it going cause it truly is awesome
Still not working:
Can not charge with the phone off
Google TTS stops working
Phone will not vibrate for SMS or email when in silent mode
BLN stays on for notifications until the phone is taken out of sleep (can be turned off)
Compass is why off (have not attempted to calibrate yet though)
11 MB left in the system partition (not much but I do not think there will be many changes there)
Video play back is choppy and some will not play
Bucky
regarding the black screen:
- had that too... I let it sit on the black screen for 2-3 minutes and then it went to the boot screen animation (a multi-coloured )...that for a few minutes...then finally booted.
How i got it working:
a) Started on MIUI...booted into clockwork
b) Backup
c) Wipe data / factory reset and cache and dalvik cache
d) Install rom and then kernel
e) Restart
f) Install rom and then kernel
g) Restart and wait very patiently for a little while
h) Once it all works, can reboot into clockwork and install superuser
Good luck! I really think the rom is nearly stable enough for daily use...
-------
Also have the no vibrate on silent... haven't tried the other stuff yet.
Oh and TTS hasn't crashed on this version yet for me...
Astrid glitches a little to a lot.
Changing from google tts to picco tts solves the problem there. As for the other stuff it is all reported as known.
I am using as a daily on my phone and no issues with general use. Still testing battery and that seems to be a bit of an issue with regard to Android OS as usual
Sent from my GT-I9000 using XDA App
So to install this ROM I would just have to install it as per totallydubbed's instructions? I don't want to flash miui if I don't have to to try this out.
Sent from my GT-I9000 (T959 mod) using XDA App
I'm sorry to sound noobish, but every time I flash a ROM on my Nexus 4 (mako) that isn't a Cyanogenmod build (10.2-20130904-NIGHTLY-mako) , my home softkey becomes completely useless and the AOSP or AOKP keyboard constantly crashes. I was told this is a known bug in certain source codes as far as the keyboard is concerned in 4.2.2 builds, but I'm still mystified by the home button issue and as to why I other people can be using the same ROMs that I can't without a problem. Is there a certain version of GAPPS that I can flash to avoid this problem, or is there a known fix? I always wipe data and cache when flashing, so I'm pretty sure this isn't a user error, other than which version of GAPPS I'm flashing (gapps-jb-20130813-signed.zip).
trevorftard said:
I'm sorry to sound noobish, but every time I flash a ROM on my Nexus 4 (mako) that isn't a Cyanogenmod build (10.2-20130904-NIGHTLY-mako) , my home softkey becomes completely useless and the AOSP or AOKP keyboard constantly crashes. I was told this is a known bug in certain source codes as far as the keyboard is concerned in 4.2.2 builds, but I'm still mystified by the home button issue and as to why I other people can be using the same ROMs that I can't without a problem. Is there a certain version of GAPPS that I can flash to avoid this problem, or is there a known fix? I always wipe data and cache when flashing, so I'm pretty sure this isn't a user error, other than which version of GAPPS I'm flashing (gapps-jb-20130813-signed.zip).
Click to expand...
Click to collapse
The known issue you are talking about is the JSS deadlocks? if yes, then it is not the problem with you.. for you it force closes the keyboard.. are you following the procedure of installing rom properly? are you doing dirty flash (flash without wiping data)? you can find out if gapps is responsible by booting into a freshly installed rom without installing gapps and see if the problem persists..
You should also format the /system partition when you flash a new rom.
For some roms the Home button stop working for me and to fix it I had to install gapps, but most CM based roms I use don't have that issue.
As for keyboard, I always delete the default keyboard from the rom and use Google Keyboard.
Andre_Vitto said:
The known issue you are talking about is the JSS deadlocks? if yes, then it is not the problem with you.. for you it force closes the keyboard.. are you following the procedure of installing rom properly? are you doing dirty flash (flash without wiping data)? you can find out if gapps is responsible by booting into a freshly installed rom without installing gapps and see if the problem persists..
Click to expand...
Click to collapse
Please explain what JSS deadlocks are. I don't dirty flash. I always wipe data. As for the keyboard and home buttons not functioning properly,I have this problem with XenonHD, PACman ROM, AOKP and CM variants.
trevorftard said:
Please explain what JSS deadlocks are. I don't dirty flash. I always wipe data. As for the keyboard and home buttons not functioning properly,I have this problem with XenonHD, PACman ROM, AOKP and CM variants.
Click to expand...
Click to collapse
No your problem is not the jss deadlocks.. it happens when you type very fast or something.. it phone vibrates for like 5-10 sec and then restarts. I dont think its your problem. Sorry mate I have no idea why you are having the keyboard and homescreen issue even when you are are doing a factory reset every time you flash.. and why its not happening with CM 10.2..
Andre_Vitto said:
No your problem is not the jss deadlocks.. it happens when you type very fast or something.. it phone vibrates for like 5-10 sec and then restarts. I dont think its your problem. Sorry mate I have no idea why you are having the keyboard and homescreen issue even when you are are doing a factory reset every time you flash.. and why its not happening with CM 10.2..
Click to expand...
Click to collapse
Well, that's unfortunate. I've found that the RevoltHD ROM doesn't have problems, but that's because it's got integrated GAPPS.
Been having the same issue with my Nexus 4, after installing GAPPS the keyboard crashes and the home button stops responding. Did anyone figured it out by any chance? Thanks.
I still don't know what caused it, but I figured out that more recent nightly versions of those ROMs don't have that problem. I'm using AOKP currently and that used to be a problem ROM.
Take off vibration and sound and all the bells and whistles and your keyboard should be fine if the issue isn't Rom specific. Also, it could be kernel related.....try boosting touch input if nothing else
Sent by flying midget
I get the same problem, I factory reset each time I switch ROMs. I was trying with Vanir a couple of days ago and couldn't get the home button to work, tried OmniROM and it worked perfectly, went back to Paranoid it worked perfectly again, went back to Vanir and it didn't work. Was odd.
Hello Everyone,
Nexus 4
Paranoid Android 4.2Beta1
Franco Kernel
I just upgraded to PA 4.2Beta1 from PA 4.1.......
after installing the rom.....when i use my browser or messenger where we require keyboard....the Keyboard doesnt pop up....whats up with this....and also the back button of my navigation bar doesnt work.......this even happened with carbon rom a few days back...when i was experimenting with it.....but then i restored to PA4.1 due to the above given problems....plz offer a solution to this...
The same problem
keyboards not working
please help me my keyboards are not working . i have installed an custom rom.
I'd like to share my experience solving some basic problems with my nexus 4 running cm11, and 10.2
I had problems with the video freezing when shooting video
I wanted to improve the sound quality because I stream google premium and couldn't find a solution until recently
And had a rebooting problem in the end which I solved.
My nexus 4 worked perfectly running cm until I did the 4.3 update in november. After that the video would freeze when I was shooting. wouldn't happen all the time but would happen sometimes. I did everything, factory resets, reinstalling gapps, restoring the camera app, wiping data. Nothing worked. Even updating to cm 11 did nothing to change the situation. After having to go back to stock because of another problem I ran into -- installed Franco kenrnel on cm 11 and they aren't compatible -- I discovered that the video camera was still freezing. So I discovered it had nothing to do with cyanogenmod roms. Someone suggested flashing the separate photosphere gapp package along with the full gapps package and funny enough that solved the problem.
http://forum.xda-developers.com/showthread.php?t=2397942
I don't know if the recent updated photosphere gapp corrected a problem or what. But. Shooting Video now works.
I switched to omni rom because I wanted to use the franco kernel to adjust my sound settings, in my search for sound quality improvement but the omni rom was a real challenge and was plagued with bugs and wasn't for me. But stuck with it because of the franco kernel.
I then discovered that hells-core kernal did the same thing and works with cm11 so switched back to cm11 the stable snapshot version from last week and installed hells-core kernel. My phone started to reboot capriciously every 10 or 15 minutes and tried everything to correct that, eliminated data from apps, fixed permissions -- nothing worked, but finally decided to flash the latest cm nightly to see if the problem wasn't related to the version of the rom I was running .
When I flashed it, I wiped cache partition, delvik cache, and formated data , reflashed full gapp package plus the photosphere gapp. I didn't flash hells-core again. Maybe that was causing the reboots. I don't know. Everything now works perfectly. No more random reboots, the video camera seems to work fine, I discovered that the cm kernerl does have one volume gain adjustment and am now using viper4android effects equalizer that has gain control for both volume, bass and treble and everything is great. and my sound quality is probably as good as it will get on a nexus 4.
I spent an inordinate amount of time trying to resolve these problems so hope this is of some help to others.
So i just woke up, opened my Snapchat, to realize my camera is really dark, and i mean really dark. Unless i point the camera at a light source i can't see anything, just black. The weird this is that it's the same story inside the camera app, and even the front facing camera. Both of the cameras are really dark, i've tried delting the cache, rebooting, wiping my phone, and installing Cyanogenmod again, only to see the same **** over and over again. Any tips on how i can fix this?
Facing the same issue. When in capture mode it's dark and video mode it's completely bright. I am using the 11/18 NitrogenOS with CameraNX4.1 Fix.
Same. On npf10c, started immediately after flashing the pixel navbar fix through FlashFire. Wiping cache didn't do anything.
I have the exact same problem. I'm on 11/18 nitrogen OS as well. It was perfectly fine when I first flashed the ROM but after a day it went dark. If anyone has a fix please let us know
So recording video is broken, it gets super BRIGHT, but for some reason taking a picture with flash on fixes the problem temporarily. Otherwise though this is persistent.
Just got this Nexus and the camera was working fine. I'm on preview with French fk.. last night it just went dark after working fine. Funny it started at the same time
I flashed the NDB91K vendor and it fixed my black camera issue. You get the security message on boot, but the camera is working fine for me
Having the same problem here. Already tried wiping cache, reflashing vendor and dirty flashing Nitrogen. I am on 11.18 Nitrogen release. So far nothing seems to fix it.
Identical problem. I JUST flashed the stock boot.img and it fixed the problem. Going to re-root and flash elementalx and will report back.
yeah flashing the previous vendor fixes the issue. Not sure why that caused the problem
God ****ing dammit I just realized why this may have been happening to me. Franco is not currently supported for 7.1.1. And a user on reddit I spoke to said he was using flash while on 7.1.1.
That's probably what's causing this issue.
Kill me.
Even with fk installed I was able to use the camera just fine.... I ran on it for a couple of weeks even on dp
Running the 11/18 build of Nitrogen OS with banks GApps and having the same issue. Clean flashed. Flashing the latest image fixed it.
ThatInsaneHobo said:
God ****ing dammit I just realized why this may have been happening to me. Franco is not currently supported for 7.1.1. And a user on reddit I spoke to said he was using flash while on 7.1.1.
That's probably what's causing this issue.
Kill me.
Click to expand...
Click to collapse
Using Franco R37 with 7.1.1. No issues here :fingers-crossed:
Same here
Damn it. I just installed the pixel XL ROM and I'm getting dark camera and bright video. This is like way after the original poster too. How come no fix?
The problem still persists , i got the same issue and that too after opening snapchat , i really don't know what to do, any help , how can i get back to old kernel again?
Do you try flash other rom?
Does anyone have a link for the vendor image?
Sent from my Pixel XL using XDA-Developers Legacy app
Solved for me with that boot.img from Silesh.Nair:
http://forum.xda-developers.com/moto-g4-plus/help/camera-records-video-1080p2-t3517934/post70107680
________________________________________________________
XT1642, MM modem, random custom roms
Hello guys, finally I got an error where the snapdragon camera app records video only in slow motion, see Screenshot attached while checking the video on my pc.
That was never before flashing RR 5.8.0 20161208 7.1.1 build,but I don't think it has something to do with it
Temporary workaround:
I figured out it can fixed once I clear dalvik/cache in twrp, boot rom and then record video with snap app.
Open camera crashes(camera hardware is busy cause of usage from others), wasn't before...
But after closing app and waiting some time(seconds minutes) the app only records slow motion. This happens if storage is set to internal or SD card,it's always the same.
What I did already:
-wipe everything, including internal storage, several times
-clean install of cm14.1, 3 different versions including from today. RR 5.8.0 20161126, RR 20161208. Without restoring anything.
-also with @Silesh.Nair additional boot.img for builds before today
Changed sd card from 32 to 64GB
-changed sd card from fat 32 to extfat
Restoring full backup before it happens
-dirty flash several of above roms
-logged the video recording with and without this bug https://drive.google.com/folderview?id=0B4Zy8uoEfFKLbjlYOW5WcW02LXc
But still persists... :crying:
-flashing stock rom is the next step to do
So my questions are:
-anybody seen this before with MM modem?
-any other hints somebody know?
I don't want to upgrade to N soak test for firmware files unless it's the only way! Because downgrade can cause additional problems!
I opened new thread because it's complex problem I though and maybe does nothing have to do with custom roms only...
Thanks in advance!
Till now i haven't recorded anything with my phone, but as your asked, i tried first time to record video on RR-N and my problem is also different than you too, mine is single photo to complete video... Nothing got recorded... Only single photo where from video recording started.... I checked on MOTO CAMERA too.. same on both...
Will see on other ROM...
Edit: I'm also on MM baseband, if anyone on N baseband pls confirm....
__Madddy said:
Till now i haven't recorded anything with my phone, but as your asked, i tried first time to record video on RR-N and my problem is also different than you too, mine is single photo to complete video... Nothing got recorded... Only single photo where from video recording started.... I checked on MOTO CAMERA too.. same on both...
Will see on other ROM...
Edit: I'm also on MM baseband, if anyone on N baseband pls confirm....
Click to expand...
Click to collapse
Thanks for this information! I see this in my system information for baseband:
As I never flashed another baseband/modem file or M soak test I came to the conclusion, that maybe flashing the provided boot.img from @Silesh.Nair (to bring back Hotspot on RR) messed up my baseband and other firmware files like the camera.
@Silesh.Nair could it be or am I wrong?
Thanks!
strongst said:
As I never flashed another baseband/modem file or M soak test I came to the conclusion, that maybe flashing the provided boot.img from @Silesh.Nair (to bring back Hotspot on RR) messed up my baseband and other firmware files like the camera.
@Silesh.Nair could it be or am I wrong?
Thanks!
Click to expand...
Click to collapse
My baseband is same as your's, since we both haven't flashed N soak.. nothing related to messed with baseband.. I'm trying other ROM, will see...
---------- Post added at 05:16 AM ---------- Previous post was at 04:21 AM ----------
Don't know what went wrong with previous setup, now clean flashed again with and without Boot.img also flashed boot.img with CM14.1 worked fine in all cases....
As you said it's slow motion, i have something related to that,
if snap is opened first time after every boot then it's lagging, and video recorded is of lagging images.. for that, close snap and open again.. it will work..!!:good:
Edit:
It worked only for little while after wiping cache..
And then same as before...
__Madddy said:
My baseband is same as your's, since we both haven't flashed N soak.. nothing related to messed with baseband.. I'm trying other ROM, will see...
---------- Post added at 05:16 AM ---------- Previous post was at 04:21 AM ----------
Don't know what went wrong with previous setup, now clean flashed again with and without Boot.img also flashed boot.img with CM14.1 worked fine in all cases....
As you said it's slow motion, i have something related to that,
if snap is opened first time after every boot then it's lagging, and video recorded is of lagging images.. for that, close snap and open again.. it will work..!!:good:
Click to expand...
Click to collapse
I can close snap camera and open it again, but still only 2fps after recording. I need to boot recovery and wipe caches, then after reboot it only works as long as snap camera is open. When I close it once it begins again to record 2fps
Did you have the same baseband as me after flashing other roms? Maybe last thing is flashing stock MM with fastboot?
strongst said:
I can close snap camera and open it again, but still only 2fps after recording. I need to boot recovery and wipe caches, then after reboot it only works as long as snap camera is open. When I close it once it begins again to record 2fps
Did you have the same baseband as me after flashing other roms? Maybe last thing is flashing stock MM with fastboot?
Click to expand...
Click to collapse
Yes, same MarshMallow baseband..
As i mentioned my problem in first reply, it get solved by clean flashing, you should try clean flash again..
Oopsie. I have this problem too. Single image, audio has no issues.
Force closing snap doesn't fix things.
I'm on RR, N baseband, latest build. I think the boot.IMG by @Silesh.Nair is the cause here. Is it incorporated into the ROM?
Here's the log, http://pastebin.com/xg7GFvvC
Just after video was taken with Snap and then played on Google Photos.
zeomal said:
Oopsie. I have this problem too. Single image, audio has no issues.
Force closing snap doesn't fix things.
I'm on RR, N baseband, latest build. I think the boot.IMG by @Silesh.Nair is the cause here. Is it incorporated into the ROM?
Here's the log, http://pastebin.com/xg7GFvvC
Just after video was taken with Snap and then played on Google Photos.
Click to expand...
Click to collapse
Sounds weird :silly: I used latest cm14.1 build non oms, clean flash. And here's the problem too.
Actually i restored a backup of RR 20161126 build (every thing was OK on this backup) without the mentioned boot.img but the problem persists(can take some vids, then slow motion again).
http://forum.xda-developers.com/moto-g4-plus/help/help-thread-custom-roms-t3513118/post70080516
http://forum.xda-developers.com/moto-g4-plus/help/help-thread-custom-roms-t3513118/post70080516
These happen to people who flashed soak test as well
strongst said:
These happen to people who flashed soak test as well
Click to expand...
Click to collapse
Something broken from source..!
I don't think we can solve this problem without developer's help.. i don't want to mention silesh nair as his conditions he said in help thread.
I hope @rahulsnair and @vache will look into this..
Can you play the recorded videos on a computer or on another phone ?
vache said:
Can you play the recorded videos on a computer or on another phone ?
Click to expand...
Click to collapse
I haven't tried video elsewhere, but you can see attachment in OP, it's photo of computer i think... So, not working...
Video getting recorded, is also getting damage at same time..
You can check Logs in OP..
vache said:
Can you play the recorded videos on a computer or on another phone ?
Click to expand...
Click to collapse
I can play the video on smartphone or as you see on my pc. But it is only with 2fps. Sometimes I get what Maddy and others said, it's only a picture with sound. Like a corrupted file
I'm actually testing this behavior on latest Vanir aosp, but at the moment and around 30 videos recorded i can't get this error. All videos are as they should be. But I'm still testing at the moment
Ok, since nearly 24h testing with latest Vanir rom the problem mentioned in op didn't happen anymore.
Only one thing: after recording a video you should close snap camera, reopen and then play the video with link on the left side. If you play it immediately after recording, the gallery app crashes/freezes. You can also close snap camera after recording and open Gallery separately or another viewer app. No matter if video will be saved to sd or internal storage.
I know it's not a solution for the problem, but a workaround for me
Maybe some dev can compare RR/cm14.1 with Vanir and check the difference that can cause this behavior.
If I can help further, I will do it.
Try this boot image on cm.
https://drive.google.com/file/d/0B1ZbHDX3hq1yVjlQMWpELVBXYnc/view?usp=drivesdk
Sent from my Moto G4 Plus using Tapatalk
Silesh.Nair said:
Try this boot image on cm.
https://drive.google.com/file/d/0B1ZbHDX3hq1yVjlQMWpELVBXYnc/view?usp=drivesdk
Click to expand...
Click to collapse
Works in RR, on Snap!
XT1643, 5.8.0. N modem (latest OTA).
Fails on OpenCamera.
Got some issues with video after flashing last soak on my XT1642. Phone rebooted after launching gallery app (even without trying to play a video), i was still able to shoot videos. I tried to flash many ROMs, some old ones, still same issue. Wiped and formatted almost every partition without success.
Then i decided to flash last MM full firmware, and now it's working like a charm. Dunno what appended here...
strongst said:
Ok, since nearly 24h testing with latest Vanir rom the problem mentioned in op didn't happen anymore.
Only one thing: after recording a video you should close snap camera, reopen and then play the video with link on the left side. If you play it immediately after recording, the gallery app crashes/freezes. You can also close snap camera after recording and open Gallery separately or another viewer app. No matter if video will be saved to sd or internal storage.
I know it's not a solution for the problem, but a workaround for me
Maybe some dev can compare RR/cm14.1 with Vanir and check the difference that can cause this behavior.
If I can help further, I will do it.
Click to expand...
Click to collapse
You didn't tried any other ROMs appart CM14 and RR before ?
vache said:
Got some issues with video after flashing last soak on my XT1642. Phone rebooted after launching gallery app (even without trying to play a video), i was still able to shoot videos. I tried to flash many ROMs, some old ones, still same issue. Wiped and formatted almost every partition without success.
Then i decided to flash last MM full firmware, and now it's working like a charm. Dunno what appended here...
You didn't tried any other ROMs appart CM14 and RR before ?
Click to expand...
Click to collapse
Nope, only cm14 and RR then vanir,hence still on MM firmware. But I flashed the provided boot.img in RR 7.1 thread to fix Hotspot issue on latest 7.1.1 RR and the snap bug happen first.
Actually restored backup of 20161226 RR and testing again together with Silesh.Nair's boot.img