Hey thanks for the reply! I wouldn't quite say that I go really in-depth! I am in no way savy about how exactly the develoment works but I've been around long enough and always been a flashalcoholic to know a little bit I guess . To the point now:Hi! It's nice to encounter someone who goes in-depth for this kind of stuff. While yes it is true that the device launched with a 32bit kernel and is now running a 64bit kernel camera issues mostly stem from the blobs being 8.0 based, between android O MR1 and R a lot of changes to fw_av have been merged fundamentally changing how camera is supposed to work. I've done my best to patch them up but some still slip through. Is the shifting colors green-ish in nature? If so i might know the issue, otherwise a logcat might help. Otherwise setting persist.camera.HAL3.enabled to 0 in build.prop will disable camera2 and might help you out.
PS: I know it's not a kernel issue because even devices like Moto One that launched with a 64bit kernel use 32bit camera blobs, that is because the kernel driver is 32bit always
Curious, after the last update everything should be smooth (I'd forgotten to pin SystemUI), mind attaching /data/lspeed/log/main_log.log?
Do tell? How long have you been around if you don't mind me asking? Me i've been around since ICS days, not as a dev of course.Hey thanks for the reply! I wouldn't quite say that I go really in-depth! I am in no way savy about how exactly the develoment works but I've been around long enough and always been a flashalcoholic to know a little bit I guess . To the point now:
I have been waiting to take the phone from my girlfriend into my hands and I tried to deactivate camera 2 api. It seems it's working! I checked that it was correctly deactivated with a play store app and it's really working and the washed off colors intermitent switching have disappeared from whatsapp video calls. I couldn't quite test lots of camera apps but for the moment it's certainly a succes. I could still changue it back and grab some logs if you think that would be useful nontheless.
Thank you very much for keeping such a old device alive! In my opinion, it still has a pretty capable cpu even for this days. A pity how the companies always let die the hardware to get the new sales right?
Have a wonderful day my friend. I'll be sending you some beer/cafe money soon .
EDIT: I see a donation button in OP but it's fur AICP. While I appreciate the work, I was wondering if you personally had a link from yourself. Thanks =)
Haven't heard of that sdcard bug; care to explain?In case I'm asking stuff that was mentioned a number of times - just shoot me in the foot.
I'm using XT1635-02 (I have SD-card bug but I guess I messed up repairs again).
1. My camera is not doing 4K video recording - it doesn't go higher than 1920x1080 (FullHD).
Is this intentional or "bug" or related to my hardware?
2. In other ARM64 ROMs encryption was broken - is it fixed here? If so - how can we check?
3. Is there a recommended version of TWRP recovery? Links aren't necessary, version number should suffice.
If these things are global - can you add information in the OP so people get less confused (I hope).
P.S. I have to applaud for the amount of work done to get this running
P.P.S. Sooner (or later) I will be testing AICP on Moto G4 Play (have to fix broken bootloader on hardware level).
SDCard bug - almost none of my SD cards (16,64 or 128GB) are no longer recognized. When I plug them in (in device mode) in logcat I get only one message:Haven't heard of that sdcard bug; care to explain?
1. If you are talking about the included camera, that's because it isn't designed to do so; snap cam is designed to just cover the basics, something like opencamera or gcam will allow you to record at 4k (tho i wouldn't recommend it due to hw encoding limitations)
2. It works here, go to settings->security->encryption->encrypt device and if you have >80% battery you'll see the encrypt button, click it and the phone will reboot to start encrypting, after that it will reboot again, fully encrypted
3. The official one, as is expected unless specified, i'm working on a build of twrp-9 because otherwise you can't decrypt the phone in twrp (twrp limitation) but it's slow and it will be available through official channels when it's done
Usually issues like these are added in the "Know issues" section, if it isn't there it's expected to work
Not that much work thankfully, some oddities here and there, but that's the fun part of it
Ah, harpia, i'm good friends with the developer for it
That log indicates that the device can read that something is in the slot, if it isn't recognized you might have damaged a data line for itSDCard bug - almost none of my SD cards (16,64 or 128GB) are no longer recognized. When I plug them in (in device mode) in logcat I get only one message:
--- mmc_gpio_cd_irqt: mmc cd gpio status: 1 (which may not even be related to SD card slot at all)
and it changes to status: 0 upon unplugging. Most likely some hardware failure - I had to replace screen and battery and during assembly might have misaligned some parts (because speaker sounds like complete garbage unless I press onto the screen)
BTW - this issue persists in any TWRP recovery, definitely pointing to hardware error - If I use USB-C hub and plug the same SD in card reader - it's recognized without any issues.
About my questions:
1. But 4K video recording is available in Stock ROM - was it a "hack" on Motorola/Lenovo part?
3. Still would like to hear which version is preferred. For instance I cannot flash anything above version 3.5.0. unless I repartition Recovery (they're 16.5 MB while partition is only 16.0). And version 3.5.0. in particular after several boots will not be able to work with "internal_sd" or data partition properly. Leaving me with 3.3.1.
That log line actually indicated whether SIM/SDCard tray is installed or removed. Even if I install empty tray I get these lines.That log indicates that the device can read that something is in the slot, if it isn't recognized you might have damaged a data line for it
1. Because motorola shipped their motocam, i could ship it too, but it's 8.0 based, and arm based so i'd have to do a lot of work for a camera that's honestly not that great. Snap is there just as a basic camera, giving you the choice that if you want more you can download anything
3. Wouldn't be able to answer, but hearing that it really sounds like i gotta step up the twrp application
That log line actually indicated whether SIM/SDCard tray is installed or removed. Even if I install empty tray I get these lines.
Since reassembly was in order - and yes, contact group was misaligned. Surprisingly both SIM card slots worked (which made me very confused). But now I've broken a flex cable (battery temp sensor) and now battery is "cold"(-26°C), so I'm into some additional expenses (it's not that bad though).
Additionally I have more questions:
1. Battery - Why is "nominal" capacity reported as 3000 mAh? Can't we update that value in next builds to proper factory value of 3510 mAh? I know it's a nitpick and phone is half a decade old (so not even replacement batteries will get that capacity) but it would be nice.
2. (Probably not your specialty) In AICP Extras there are two Statusbar network activity - normal works but provides only bytes/s value - I would like the option to choose between bytes and bits per second. And "Expanded statusbar network activity" doesn't seem to work at all (if logs would be helpful - can provide, but I require some pointing towards proper logs of that matter)
3. About that camera app - including motocam is completely up to you and optional (OpenCamera cannot record video in 4K btw, I tested).
4. Since I'm onto subject of included apps and features - Digital TV app doesn't work at all for me - no on-screen error messages or anything - it isn't a big deal, but might as well share this info (hopefully it's not a double report) - can possibly assist with logging that.
3. I managed to get 4K recording to work. In OpenCamera you have to pick "Camera2 API" before anything else.1. I have no idea as that isn't handled from my side, it might be that something changed in how android expects the battery capacity to be reported between O and now, but i'll have to look into it
2. I'll have to ask the team and come back to you on that. The "Expanded statusbar network activity" works as intended, maybe the wording is a bit vague, but it adds that activity to the expanded statusbar. I.E, when you pull down to show all of your quicksettings it appears in the corner
3. I wont do it because it's a huge time investment for a terrible camera app, opencamera IS capable of 4k recording (that's why i recommended it in the first place). You need to go settings-> Recording settings -> Video resolution and there you can select 4k. I know it is recording in 4k because the bitrate matches and so do the dimensions
4. It's for a tv moto mod; this one
Sorry, i forget; i've used it for so long that i always forget it comes by default using Camera13. I managed to get 4K recording to work. In OpenCamera you have to pick "Camera2 API" before anything else.
If "Original Camera API" is used - resolution does not show up in the list and "Force 4K UHD" toggle does nothing - none of the recordings using "original API" were made in 4K, only in FullHD.
Also about 2. I thought "Expanded" version adds stuff so shame on me for not checking properly. Cheers
#include <std_disclaimer.h> /* * Your warranty is now void. * * We are not responsible for bricked devices, dead SD cards, * thermonuclear war or you getting fired because the alarm app failed. Please * do some research if you have any concerns about features included in this ROM * before flashing it! YOU are choosing to make these modifications and if * you point the finger at us for messing up your device, we will laugh at you. Hard & a lot. * */