Related
Hello, I installed PA 3.99 RC2 and everything works fine, except native camera apk.It FC when I try to open it, I installed a 3rd party one, but I 'm wondering if there is a solution for the native camera.
Have you posted this in the PA forum? I don't mean this question doesn't belong here, but the team seems pretty on-top-of-things with answering end-user questions. Might be a problem that nobody else has reported yet.
WiFi gave me a problem on the 3.99 8/28 CDMA release. I rebooted once, and the issue was fixed (though, it was not a FC problem, it just wasn't identifying the hardware).
LuckiestNut419 said:
Have you posted this in the PA forum? I don't mean this question doesn't belong here, but the team seems pretty on-top-of-things with answering end-user questions. Might be a problem that nobody else has reported yet.
WiFi gave me a problem on the 3.99 8/28 CDMA release. I rebooted once, and the issue was fixed (though, it was not a FC problem, it just wasn't identifying the hardware).
Click to expand...
Click to collapse
I can't post in the development forum, since I didn't make 10 posts(and I don't want to spam to achieve this). I tried to clear cache and then did a factory reset, but nothing changed(although it did work for the Wi-Fi problem you mentioned). I guess it's rom's problem and I found another minor conflict. When I start musixmatch apk, dsp fc's
sent from my xt910, using tapatalk 2
Most RAZR roms seem to have camera Problems, even cyanogenmod. Some alternative cameta apps like camera360 work better - maybe. It depends on your ROM.
Einheit-101 said:
Most RAZR roms seem to have camera Problems, even cyanogenmod. Some alternative cameta apps like camera360 work better - maybe. It depends on your ROM.
Click to expand...
Click to collapse
I mentioned in my 1st post that I installed a 3rd party apk for camera, camera mx works fine for me(has video recording too)
Sorry if this thread already exists.
You have no idea how happy I am this ROM exists!! But I cannot get SMS working. I get FC's on every SMS app I try including Hangouts. Anybody else getting this and/or have a remedy? Thanks
I was about to post the same error here, I have an Amaze with Videotron, S-Off, Super CID, HBOOT-1.93.2222 (JuopunutBear), TWRP as a recovery.
I tried everything, I tried different Gapps, I also tried without installing Gapps, I tried sms apps from the Play Store and Hangouts too. The only thing I haven't tried is formatting my internal SD card. (it was a clean install, all formatted and cache cleared). I also tried switching to ART but I had the same problems.
Everytime I try to just open the sms apps, the app crashes. I managed to see the error once and it was something about SQL but it might be a misinterpretation from my part.
Calls, 4G and WiFi were all working perfectly too.
After some research on Google, I tried installing busybox, xposed framework and uninstalling Voice+, but nothing works. The basic messaging app just closes without any kind of message and other apps show that it stopped working.
(I tried the Evervolv rom 4.4 and SMS were working on that one, maybe it's a setting with my network type as I am on Videotron in Canada and it is using AWS, maybe a setting under *#*#4636*#*# ??)
I want to contribute and sen some log of that error, how can I do that? I am familiar with roms, kernels, etc but not that much with logs... I tried many roms before and never got that specific problem...
Thanks to anyone who can help with this issue!
It's not just you SMS simply doesn't work on this rom and I was surprised to see that no one else pointed this out in the original thread. The default Messaging app closes immediately when you try and open it. Other SMS apps also crash either immediately upon opening them, or when you try to send a message (hangouts & SMS Pro for example). This is the only thing keeping me from using this amazing rom as my DD.
I have the same exact problem with SMS- will try the evervolv 4.4 though was really looking forward to CM11
Edit: also didnt have any other problems with the rom except for the black boxes and the camera
Let's hope there is a way to fix it!
I would post the question in the official thread but I do not have enough posts to do so unfortunately
Heck I couldn't even try SMS due to the black box issue, that's why I didn't mention it in the original thread.
For those with the black box issue--are you using the correct gapps?
In olden days there were some issues with some google things not working, and people uninstalling the ones that came in gapps and downloading them fresh from the play store.
Have you gone into recovery and fixed permissions?
Again, in days of yore, this might straighten some things out.
Is it possible that black-boxing has something to do with CPU frequency, and is it possible to tweak up the speed through developer options and lose the boxes?
I haven't tried this rom yet, as I'm currently sticking with the stable(r) cm10.
Good luck.
anybody get the SMS working on this ROM so far?
pbergonzi said:
For those with the black box issue--are you using the correct gapps?
In olden days there were some issues with some google things not working, and people uninstalling the ones that came in gapps and downloading them fresh from the play store.
Have you gone into recovery and fixed permissions?
Again, in days of yore, this might straighten some things out.
Is it possible that black-boxing has something to do with CPU frequency, and is it possible to tweak up the speed through developer options and lose the boxes?
I haven't tried this rom yet, as I'm currently sticking with the stable(r) cm10.
Good luck.
Click to expand...
Click to collapse
The black box issue has nothing to do with GPU or CPU speeds. There are discussions on the dev threads. The issue affects other legacy devices on various KK based source builds, not just Amaze and CM. The consensus is this seems to be related to the default browser which has changed in KK. This would also explain why it effects other gapps too.
MS92 said:
anybody get the SMS working on this ROM so far?
Click to expand...
Click to collapse
Not that I'm aware of.
Media Issues
The ROM is pretty good for the most part.
I just have this problem where Play Music gives this error, "Cannot play the music track you requested"
I clear my media storage and try to rescan my SD card but none of the apps work. They all crash.
Is there anyway to fix this?
ranwal said:
The ROM is pretty good for the most part.
I just have this problem where Play Music gives this error, "Cannot play the music track you requested"
I clear my media storage and try to rescan my SD card but none of the apps work. They all crash.
Is there anyway to fix this?
Click to expand...
Click to collapse
Maybe app settings for the app and Erase App Data?
can i get a link for the updated adreno drivers? thanks!
865DETH said:
can i get a link for the updated adreno drivers? thanks!
Click to expand...
Click to collapse
Yes you can its on last three pages of orignal thread you also have to sign up for that
Sent from my HTC_Amaze_4G using Tapatalk
as the OP says and i quote that only non working things are
1. camera exposure
2. tethering
but as the thread goes ahead we read more prolems/bugs
May i ask what is the current status for bugs/not working and other issues and what has been fixed and any other stuff we should flash over the ROM like driver, may it be upoaded to the OP for ease as its reall hard to search for those things on mobile app. thank you and good luck.
Anyone else have issue disabling their microphone while in a call? I tried with both the speaker phone and regular handset mode, the "no mic" icon enables but my caller can still hear me. The Hold button seems to work fine though.
FYI, it took a while for the battery to figure itself out. I wiped the battery stats before flashing everything and the first few days I got a lot of jumping battery levels. I let it charge all the way down as much as I could then rebooted and did a full charge and rebooted again and then full charge again. That seemed to reset the battery level to the correct state.
I also , enabled Device/GPS only for the location detection other wise the google services at 50% or more battery.
I'm running the 2014-02-16 build, with the updated video drivers.
Camera is not working
I have also installed this pacman rom 4.4.2. all is well instead of camera.
Any updates for the camera isssue??
Shahxz said:
I have also installed this pacman rom 4.4.2. all is well instead of camera.
Click to expand...
Click to collapse
Since PAC uses the CM device tree for its source any issues with CM will also be evident in PAC. Until the CM devs are able to resolve the camera exposure issue it will exist in both ROMs.
Librastar said:
Any updates for the camera isssue??
Click to expand...
Click to collapse
Think about your question for a minute. Have you seen any recent posts in the CM dev thread indicating an update which solves this issue? If you had just taken a moment to look at the dev thread instead of posting this you would have answered your own question. It's not like the CM-11 thread is incredibly long, it's only 28 pages total. This post is just laziness on your part and an unnecessary waste of bandwidth.
is there any alternate app in the market, i tried couple of apps but nothing useful
@Odysseus1962
If I were to compile AOSP, which variant would you suggest for me to build?
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Hello all,
I´m sorry Administrators but not sure about which forum to create the post, once the issue affects my HTC One X but also several other brands like Motorolas, Samsungs, etc. mobiles.
I already search on several other forums and also here on XDA Dev (https://forum.xda-developers.com/htc-one/help/m7-mute-calls-please-help-t2921985), but with no success for a real/final solution for the issue.
All of these mobiles can´t make/receive a phone call. Both sides can´t hear voice.
Looks like it is a Google problem.
In my case, I using Resurrection Remix but it happens with Stock roms also.
Solutions like wipe cash/data, diseable Google Store, Google Service and Google Framework, diseable WiFi, diseable 3G or 4G are just temporary solutions which doesn´t fix defenitively the issue.
According my searches, it is a problem that exists since mid of 2013 and I can´t believe there is no solution since then, so please help me at least just indicating where is the final solution (thread), ´cause I can´t find it and I believe XDA Dev is the TOP forum for that.
Thank you in advance.
Any tip, Please ??
Tks !
If this problem is across multiple phones then it's not a phone or rom problem. How did you handle those calls. Which app did you use? Cellphone and dialer? Wifi and dialer(vowi) chat app or whatever?
Strongst,
This problem happens with multiple phones from lots of people, based on several forums I already looked for solution and not only with me at more than one phone.
I have just my HOX with RR rom as mentioned.
Just looking for a real and final solution.
I can´t believe there is no solution for this issue !
I´m reading about this problem since october 2017, of course not every day and ound several people looking for solution, but all treads/topics I found and read til the end, had no final solution !
I´m using an old LG that alows me phone calls, but I want a solution for my HOX !
Tks for the answer.
The linked thread is 2 years old... I never heard of it and I'm reading multiple device forums... Any actual links?
Unfortunatelly not.
I´m facing this issue since 1 year ago and since then, looking for a solution but just find old threads with no final solution.
I have few other threads for other forums but I believe XDA is the best one. Even so, I couldn´t find a solution here.
The fact is: I´m using a handheld instead a smartphone...LOL...
I can´t believe lots of people without a final solution. The point is: where is the final solution ?
I don´t want to give up, but it is hard !
Of course I´m not looking for everyday, all day long, but at least once a week I´m trying.
Another point is that I know my HOX is an old mobile but it is not the problem once I saw several M7, M8 and other new mobiles with the same problem.
Anyway, I´ll keep looking.
If you Strongst or somebody else have a tip, please let me know.
Tks !
cassio gebara said:
Unfortunatelly not.
I´m facing this issue since 1 year ago and since then, looking for a solution but just find old threads with no final solution.
I have few other threads for other forums but I believe XDA is the best one. Even so, I couldn´t find a solution here.
The fact is: I´m using a handheld instead a smartphone...LOL...
I can´t believe lots of people without a final solution. The point is: where is the final solution ?
I don´t want to give up, but it is hard !
Of course I´m not looking for everyday, all day long, but at least once a week I´m trying.
Another point is that I know my HOX is an old mobile but it is not the problem once I saw several M7, M8 and other new mobiles with the same problem.
Anyway, I´ll keep looking.
If you Strongst or somebody else have a tip, please let me know.
Tks !
Click to expand...
Click to collapse
Maybe you have warranty? If you can't use your phone like a phone you should give it back or repair it. Otherwise I don't have good ideas... Maybe baseband/modem updates can help, but I'm sure you tried that too, right?
No warranty. It is a 5 years mobile, and I´m sure it isn´t a hardware problem so no reason to repair.
Still think it is a conflict between Google apps or WiFi/Network and some software at ROM (not specificaly my RR).
cassio gebara said:
No warranty. It is a 5 years mobile, and I´m sure it isn´t a hardware problem so no reason to repair.
Still think it is a conflict between Google apps or WiFi/Network and some software at ROM (not specificaly my RR).
Click to expand...
Click to collapse
You can try installing the ressurection remix rom without Gapps and test. And what I don't know yet: which way you did the call(wifi, cellphone, volte, others?). As I wrote: could be modem/baseband issue...
That´s a good idea Strongst. I´ll wipe all after back up and re-install RR only for some tests.
Regarding calls, I´m using cellphone calls, so nothing related to WiFi or 3G/4G which I believe also not related to modem/baseband.
Is that right ?
cassio gebara said:
That´s a good idea Strongst. I´ll wipe all after back up and re-install RR only for some tests.
Regarding calls, I´m using cellphone calls, so nothing related to WiFi or 3G/4G which I believe also not related to modem/baseband.
Is that right ?
Click to expand...
Click to collapse
Modem/baseband are the drivers for cellphone and wifi, not on every device. But maybe on yours. Good luck :good:
Hello strongst,
I wiped (Dalvik, System, Cache and Data) and installed again RR without Gapps.
On the first call I made, after few minutes sound stoped I mean, the other person coudln´t hear. I realize the screen locked.
I hang up the phone and tryed again avoiding screen to be locked.
Everything was fine.
After that made some calls turning WiFi on and off and also Network (3G/4G) on and off.
Everything was fine again.
On the last test I allowed the screen was locked and calls kept 100% OK.
Now I´m don´t know if I have problems with lock screen also, but without Gapps, calls were OK.
You mentioned modem/baseband. Can it also be a problem ? How can I check it (if necessary) ?
Would be the next step re-install Gapps and check the malfunction ?
I almost trying Red-X methodology as I used at GM during Hummer H3T launch on Shreveport plant...LOL...
cassio gebara said:
Hello strongst,
I wiped (Dalvik, System, Cache and Data) and installed again RR without Gapps.
On the first call I made, after few minutes sound stoped I mean, the other person coudln´t hear. I realize the screen locked.
I hang up the phone and tryed again avoiding screen to be locked.
Everything was fine.
After that made some calls turning WiFi on and off and also Network (3G/4G) on and off.
Everything was fine again.
On the last test I allowed the screen was locked and calls kept 100% OK.
Now I´m don´t know if I have problems with lock screen also, but without Gapps, calls were OK.
You mentioned modem/baseband. Can it also be a problem ? How can I check it (if necessary) ?
Would be the next step re-install Gapps and check the malfunction ?
I almost trying Red-X methodology as I used at GM during Hummer H3T launch on Shreveport plant...LOL...
Click to expand...
Click to collapse
Settings - about - baseband. Here you can see the version. Then look at your device forum if it's latest baseband.
And yes, now you should try with gapps the same tests
Thanks Strongst.
I found one thread on Searching in One X Q&A, Help & Troubleshooting forum that mentioned Baseband 5.1204.168.31 and my baseband version is 5.1204.167.31.
As far as I understood, Baseband is related to signal, same as Radio (I´m not an Android expert, so please correct me if I´m wrong) and I´m not facing problems with signal during phone calls. Do I need to proceed with some specific test ?
Keep HOX without Gapps bring lots of problems in terms of limitations (Contacts, Location for Waze, etc.)
I was using a Gapps Pico version (open_gapps-arm-5.1-pico-20161217.zip), with just few Apps, to avoid that huge quantity of Google aplications with no utility for me, in order to save space.
It was downloaded from opengapps.org
I was checking and realized there is a 5.1 Pico Gapps version available for 5.1 from 20180204 (yesterday) !!! I´ll try to instal the new one.
Tks again for your patience and support !
cassio gebara said:
Thanks Strongst.
I found one thread on Searching in One X Q&A, Help & Troubleshooting forum that mentioned Baseband 5.1204.168.31 and my baseband version is 5.1204.167.31.
As far as I understood, Baseband is related to signal, same as Radio (I´m not an Android expert, so please correct me if I´m wrong) and I´m not facing problems with signal during phone calls. Do I need to proceed with some specific test ?
Keep HOX without Gapps bring lots of problems in terms of limitations (Contacts, Location for Waze, etc.)
I was using a Gapps Pico version (open_gapps-arm-5.1-pico-20161217.zip), with just few Apps, to avoid that huge quantity of Google aplications with no utility for me, in order to save space.
It was downloaded from opengapps.org
I was checking and realized there is a 5.1 Pico Gapps version available for 5.1 from 20180204 (yesterday) !!! I´ll try to instal the new one.
Tks again for your patience and support !
Click to expand...
Click to collapse
Yeah, without Gapps it's not smart anymore Pico gapps are always my choice in terms of minimal Google functionality:good:
I don't know if it's possible to flash another baseband/modem to the HOX like on other devices to check whether it's better or not.
Maybe you can check the HOX forum if there's a problem tread with modems and if they can be up/downgraded without bricking your device.
New version of Gapps 5.1 pico installed.
All apps (non Google) instaled also.
No issues until now.
I don´t believe modem/baseband is the real problem.
Let me try some calls (make/receive) for some days and then I´m going to feedback on forum.
Thank you Strongst.
cassio gebara said:
New version of Gapps 5.1 pico installed.
All apps (non Google) instaled also.
No issues until now.
I don´t believe modem/baseband is the real problem.
Let me try some calls (make/receive) for some days and then I´m going to feedback on forum.
Thank you Strongst.
Click to expand...
Click to collapse
Maybe it was a dialer problem of the gapps you used
Anyway, good luck and waiting for report back!
Extremely frustrating and desapointing !!!
Mobile worked just for no more than 4 or 5 phone calls.
After that, only after deleting all data from Google Play Services, Play Store, Services Framework and re-starting mobile for 2 or 3 phone calls with poor sound quality and than problem comes again.
For sure it is not a dialer problem of the gapps once I´m using the basic dialer from mobile and not any other app for phone calls.
There is one interesting point that make phone calls with Whatsapp works 100%., even without deleting Google apps "buffer" as mentioned.
Sounds like some conflict between Gapps and internaal memory or some phone management app.
Almost quiting...umbeliveable !!!!
cassio gebara said:
Extremely frustrating and desapointing !!!
Mobile worked just for no more than 4 or 5 phone calls.
After that, only after deleting all data from Google Play Services, Play Store, Services Framework and re-starting mobile for 2 or 3 phone calls with poor sound quality and than problem comes again.
For sure it is not a dialer problem of the gapps once I´m using the basic dialer from mobile and not any other app for phone calls.
There is one interesting point that make phone calls with Whatsapp works 100%., even without deleting Google apps "buffer" as mentioned.
Sounds like some conflict between Gapps and internaal memory or some phone management app.
Almost quiting...umbeliveable !!!!
Click to expand...
Click to collapse
That's really a specific problem... Can you please give me the link to the thread you speak about? I want to read a little bit.
Hi Strongst,
See below the main thread.
I sent to you a Private Message with some other links I read about the issue.
https://forum.xda-developers.com/htc-one/help/m7-mute-calls-please-help-t2921985
Tks !
Hello everyone, im here to ask the comunity about a little problem present on many aosp based roms and is the low volume on thirdparty apps (Whatsapp, Snapchat, others) and my question is, someone know the way to fix this? I try to google it and search for support but i didnt find anything. I hope you can help me.
Have a nice day to everyone.
jodytejada said:
Hello everyone, im here to ask the comunity about a little problem present on many aosp based roms and is the low volume on thirdparty apps (Whatsapp, Snapchat, others) and my question is, someone know the way to fix this? I try to google it and search for support but i didnt find anything. I hope you can help me.
Have a nice day to everyone.
Click to expand...
Click to collapse
You can try Audio Compatibility Patch. It has worked for me on other devices, and the Dev just updated Samsung support two days ago. I'm about to give it a try myself. I have the same problem. Viper doesn't process audio from my browser. I believe it's a deep buffer issue. Only my system apps get processed. It should work without magisk too. Definitely read the post before flashing it. I've honestly never had an issue using it in the past though.
Correction, will not work without magisk! I can't get it flash using SuperSU for root. If you have magisk, I would definitely give it shot. I'm going to look into swapping my superuser so I can test it.
And there is a another mic problem in whats app only on AOSP based roms
Spaceminer said:
You can try Audio Compatibility Patch. It has worked for me on other devices, and the Dev just updated Samsung support two days ago. I'm about to give it a try myself. I have the same problem. Viper doesn't process audio from my browser. I believe it's a deep buffer issue. Only my system apps get processed. It should work without magisk too. Definitely read the post before flashing it. I've honestly never had an issue using it in the past though.
Correction, will not work without magisk! I can't get it flash using SuperSU for root. If you have magisk, I would definitely give it shot. I'm going to look into swapping my superuser so I can test it.
Click to expand...
Click to collapse
Let me be more speciffic on this problem, the problem is the mic on thirdapps using voip service like whatsapp, line, and others. (The robotic voice) i try to find the fix of this for any 3rdparty app.
Thak you for your response.
Lrdkenway said:
And there is a another mic problem in whats app only on AOSP based roms
Click to expand...
Click to collapse
This is not another mic problem, is the same present on all the aosp based roms for our devide, im testing the AOSP Extended 4.6 and AICP 7.1.2 and i fix every bug (low volume speaker, incall problems like low volume incall, low volume in record voice fixed too, but the unique bug i cant fix is the 3rdpartyapp robotic voice bug.
I hope to clear everything here and thakyou for your response.
jodytejada said:
This is not another mic problem, is the same present on all the aosp based roms for our devide, im testing the AOSP Extended 4.6 and AICP 7.1.2 and i fix every bug (low volume speaker, incall problems like low volume incall, low volume in record voice fixed too, but the unique bug i cant fix is the 3rdpartyapp robotic voice bug.
I hope to clear everything here and thank you for your response.
Click to expand...
Click to collapse
My mistake. I read AOSP, and for some reason thought stock touchwiz. I did some searching around, and it might be related to Ok Google. I found many reports saying that turning it off fixes the robotic voice. This might be a good place to start looking.
Does anyone tried any Android Pie Treble GSI roms on our device? is it working fine?
I know our device supports Treble but I didn' t see any successful installation with 9.0 GSI roms, always bootlooping..
phone bootloops so do not try it
TurkO546 said:
phone bootloops so do not try it
Click to expand...
Click to collapse
Can anyone try to help one of the treble devs figure it out why it bootloops on our device? I think phhusson might be willing to help + it seems like the treble roms are built on top of his gsi.
Redcalibur said:
Can anyone try to help one of the treble devs figure it out why it bootloops on our device? I think phhusson might be willing to help + it seems like the treble roms are built on top of his gsi.
Click to expand...
Click to collapse
Do you contacted @phhusson ?
SGH-i200 said:
Do you contacted @phhusson ?
Click to expand...
Click to collapse
I reached out for him in his thread so he should be aware, but I got no answer back probably because I couldn't provide logs of the bootloop (my device isn't unlocked yet). If you got any logs that you could provide him, please do so either in his thread in the treble forums or his github issues page.
https://github.com/phhusson/treble_experimentations/issues
Redcalibur said:
I reached out for him in his thread
Click to expand...
Click to collapse
Can you provide a link to your post, please? In the XDA app I can't see a list of your posts.
SGH-i200 said:
Can you provide a link to your post, please? In the XDA app I can't see a list of your posts.
Click to expand...
Click to collapse
https://forum.xda-developers.com/pr...velopment/aosp-9-0-phh-treble-t3831915/page63
It isn't anything special really. I just asked him if he might know any reason why it doesn't boot for our devices.
Redcalibur said:
Can anyone try to help one of the treble devs figure it out why it bootloops on our device?
Click to expand...
Click to collapse
Redcalibur said:
https://forum.xda-developers.com/pr...velopment/aosp-9-0-phh-treble-t3831915/page63
Click to expand...
Click to collapse
This ROM is very much experimentel, as the many error reports in that thread show. I will try the ROM in a month or so, when it is more stable.
SGH-i200 said:
This ROM is very much experimentel, as the many error reports in that thread show. I will try the ROM in a month or so, when it is more stable.
Click to expand...
Click to collapse
I think nearly every Pie Treble rom is based on this rom, so you got to wait for this one to get updated before the other ones also get updated. Most people are pretty happy with how they perform. We also need to get it to run first before he fixes device specific bugs, so if anyone can get him the logs of the bootloop, please do so.
Pontential solution
This may not matter anymore(given that the last post was from a while ago), but I manged to get the GSI's to boot by flashing magisk right after flashing the image. I found the solution in this thread.
Hopefully this helps anyone who comes upon this thread and needs help getting the GSI's to work.
Generic123. said:
This may not matter anymore(given that the last post was from a while ago), but I manged to get the GSI's to boot by flashing magisk right after flashing the image. I found the solution in this thread.
Hopefully this helps anyone who comes upon this thread and needs help getting the GSI's to work.
Click to expand...
Click to collapse
May I asked which one you tried as I've been reading though them an they all seem to have one bug or another?
lilbrat said:
May I asked which one you tried as I've been reading though them an they all seem to have one bug or another?
Click to expand...
Click to collapse
Sure! I have to mention that I'm not the most tech savvy, so I don't use these ROM's looking for bugs or anything like that, nor do I really read the forums for the GSI's(I just flash and try it out).
I've tried 2 of them: HavocOS and Resurrection Remix(currently using). Both are Pie GSI's. These are my initial impressions.
Both of them seem to work fine to me(calls, videos, data, Bluetooth, audio, etc.), but they do have a few bugs.
HavocOS's brightness slider is screwed up; scrubbing through it will give you random brightness values. All of the brightness values are there; they just seemed to be placed at random along the slider.
Resurrection Remix is 1.5GB, and you will not have enough space to flash any GAPPS(at least for me). To fix this, resize your system partition using TWRP after flashing the GSI and Magisk(go to wipe -> advanced -> select system -> repair or change file system -> click resize once -> flash GAPPS). Other than that and a crappy minimum brightness, I can't find any other significant issues(although I have not used it for very long).
The fingerprint sensor doesn't seem to be always active for both, which bums me out a little.
Other than those things, these GSI's are stable enough(take note that I have been using these GSI's for a short amount of time, so be careful), and the fact that they are Pie means that the camera should work(although the pictures are not too great).
There are most likely bugs that you may notice that I have not; like I said, I don't really look for bugs in these things. Sorry.
Generic123. said:
Sure! I have to mention that I'm not the most tech savvy, so I don't use these ROM's looking for bugs or anything like that, nor do I really read the forums for the GSI's(I just flash and try it out).
I've tried 2 of them: HavocOS and Resurrection Remix(currently using). Both are Pie GSI's. These are my initial impressions.
Both of them seem to work fine to me(calls, videos, data, Bluetooth, audio, etc.), but they do have a few bugs.
HavocOS's brightness slider is screwed up; scrubbing through it will give you random brightness values. All of the brightness values are there; they just seemed to be placed at random along the slider.
Resurrection Remix is 1.5GB, and you will not have enough space to flash any GAPPS(at least for me). To fix this, resize your system partition using TWRP after flashing the GSI and Magisk(go to wipe -> advanced -> select system -> repair or change file system -> click resize once -> flash GAPPS). Other than that and a crappy minimum brightness, I can't find any other significant issues(although I have not used it for very long).
The fingerprint sensor doesn't seem to be always active for both, which bums me out a little.
Other than those things, these GSI's are stable enough(take note that I have been using these GSI's for a short amount of time, so be careful), and the fact that they are Pie means that the camera should work(although the pictures are not too great).
There are most likely bugs that you may notice that I have not; like I said, I don't really look for bugs in these things. Sorry.
Click to expand...
Click to collapse
Did you just put the system image over the stock rom, or flashed the AOSP based roms first then system image?
The stock based setup is more stable while latter I can use gcam… But both are unstable with the network for me, I mean phone and the data connection
Riskypedia said:
Did you just put the system image over the stock rom, or flashed the AOSP based roms first then system image?
The stock based setup is more stable while latter I can use gcam… But both are unstable with the network for me, I mean phone and the data connection
Click to expand...
Click to collapse
You should first flash a stock firmware using newflasher or flashtool, then flash TWRP. Then factory reset or format using TWRP, and flash the GSI(AOSP ROM) and Magisk right after.
Not sure what bootloops you guys talk about, but I tried 2 GSI ROMs on my XZ1 and both worked fine. Tried these:
https://forum.xda-developers.com/pr...0-resurrection-remix-v7-0-arm64-32-b-t3891636
https://forum.xda-developers.com/pr...-device-development/gsi-havocos-v2-0-t3855601
manxp85 said:
Not sure what bootloops you guys talk about, but I tried 2 GSI ROMs on my XZ1 and both worked fine. Tried these:
https://forum.xda-developers.com/pr...0-resurrection-remix-v7-0-arm64-32-b-t3891636
https://forum.xda-developers.com/pr...-device-development/gsi-havocos-v2-0-t3855601
Click to expand...
Click to collapse
Are you still using one? Which one do you prefer? Resurrection Remix seems to do it for me.
Yes, I still use RR. It has some annoying bugs, which were also reported by other users; BT sound only works with headphones and doesn't work with in-car hands-free device, scrollable widgets don't work, battery charging light doesn't work, auto-updater is broken, no adaptive lighting support. I think that's all, so ROM is pretty usable still.
Havoc has a serious bug with brightness (also reported by many users) - sliding brightness slider has 0 effect or works totally randomly, so it's impossible to set desired brightness. Which makes whole ROM unusable.
manxp85 said:
Yes, I still use RR. It has some annoying bugs, which were also reported by other users; BT sound only works with headphones and doesn't work with in-car hands-free device, scrollable widgets don't work, battery charging light doesn't work, auto-updater is broken, no adaptive lighting support. I think that's all, so ROM is pretty usable still.
Havoc has a serious bug with brightness (also reported by many users) - sliding brightness slider has 0 effect or works totally randomly, so it's impossible to set desired brightness. Which makes whole ROM unusable.
Click to expand...
Click to collapse
Thanks for the info! Scrollable widgets seem to work for me(using calendar right now). The battery light does not work, like you mentioned. Auto update is also broken. Can't really test Bluetooth car audio right now. I'm bummed out by the lack of auto brightness.
Do you use this month's build? I have January build, maybe they fixed widgets in February build after many complains...
If you can test and report car's BT later, that would be great... It's the most serious issue for me so far...
manxp85 said:
Do you use this month's build? I have January build, maybe they fixed widgets in February build after many complains...
If you can test and report car's BT later, that would be great... It's the most serious issue for me so far...
Click to expand...
Click to collapse
Yeah, I'm using this month's build. I'll check car Bluetooth later when I get home.