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.
Related
Cyanogenmod 12.0 Semi-Official
HTC Evo 4G LTE ( jewel )
Basic Overview
Source built Cyanogenmod 12.0 hot off the server. No changes at all to anything. Sync and build.
This has not been officially released as of yet. Still very early code, there will be random bugs, and missing features still. They are coming.
Please refrain from reporting bugs because of this. Thank you.
Besides that It seems good enough for a "Daily Driver". No major malfunctions, just the random glitches as the code evolves as normal.
Requirements:
S-Off, HBOOT 2.10+ & 4.13.651.4 Firmware Update to function correctly. @Captain_Throwback's TWRP 2.7.1.0b , 2.8.0.x, 2.8.1.x recoveries recommended.
NPL recovery though. That's the only catch here.
Installation...
Wipe, reboot recovery.
Install CM-12.0, reboot.
One it finishes booting, reboot to recovery.
Install gapps, wipe dalvik & cache, reboot.
Profit
ROM Source: https://github.com/CyanogenMod/android/tree/cm-12.0
Original Kernel Source: https://github.com/CyanogenMod/android_kernel_htc_msm8960/tree/cm-12.0
Bugs...
Superuser settings cause Settings to FC currently. But remains functional.
Previous Release:
https://www.androidfilehost.com/?fid=95832962473395998
Current Release:
https://www.androidfilehost.com/?fid=95832962473397836
Current Release Gapps:
https://www.androidfilehost.com/?fid=95832962473397837
Partner Builds & Sub-projects
Partner Builds:
11-29-2014 Build: https://www.androidfilehost.com/?fid=95832962473394878 by @fizbanrapper
And it begins...
First Android 5.0 ROM for Jewel that works... And based off of one of the best Android 4.4.4 ROMs there was for Jewel as well. Enjoy everyone. Much more to come.
Cool. Sounds good. I may give it a try, just to say that I have 5.0. But I would like to have the camera working... But it is probably something that I can live with.
I've tried a flash, for the first time I experienced stuck in the boot, after I restarted again and then succeed, what becomes of bugs on camera?I have tried to take a picture with my camera and it worked fine, but I want to report that when opening the case of mobile networks in settings force close , thanks for dev , sorry for my bad english
ermariio said:
I've tried a flash, for the first time I experienced stuck in the boot, after I restarted again and then succeed, what becomes of bugs on camera?I have tried to take a picture with my camera and it worked fine, but I want to report that when opening the case of mobile networks in settings force close , thanks for dev , sorry for my bad english
Click to expand...
Click to collapse
First off, great work beating me to the punch on this. I was tinkering with CM 12 code all month.
Secondly, I can repeat what was said previously. I got a bootloop the first time, but after I turned it off, it booted up fine.
ocarinaz64 said:
First off, great work beating me to the punch on this. I was tinkering with CM 12 code all month.
Secondly, I can repeat what was said previously. I got a bootloop the first time, but after I turned it off, it booted up fine.
Click to expand...
Click to collapse
same here but it is running great so far
Ok. Camera bugs. I don't know. I just cut what lines out the compiler broke because of. And I have no cam. Idk why. My mobile network seems fine.. But come on guys. This is early code, so there's going to be bugs I have no control over. That would be more CMs thing. I just am basically doing what LSX64 did. No boot loop for me either. Weird...
I was saying this rom is running great thanks for the hard work. :good: I didn't expect to see a 5.0 rom for this phone. so thanks again for this rom.
jarheadusmc67 said:
I was saying this rom is running great thanks for the hard work. :good: I didn't expect to see a 5.0 rom for this phone. so thanks again for this rom.
Click to expand...
Click to collapse
Ok. No worries. I didn't either. So when I got it to even fire up.. I knew what I had to do. 5.0 for everyone, and making it a UnityROM, just a bonus
Does LTE work?
Psycario said:
Does LTE work?
Click to expand...
Click to collapse
I have no idea. I think so.. I have no LTE where I live
jarheadusmc67 said:
I was saying this rom is running great thanks for the hard work. :good: I didn't expect to see a 5.0 rom for this phone. so thanks again for this rom.
Click to expand...
Click to collapse
I can say that as long as I've got my Jewel, and as long as the code works, I'll be cranking things out. I'm really partial to Slim series ROMs, but I was super eager to try out L so I flashed this one. Also, it looks like CM is going to continue to support this thing for the foreseeable future. Once they start their nightly builds, it should be available there, too. Though, without the extra butter.
Thanks for the work and the build.
ocarinaz64 said:
I can say that as long as I've got my Jewel, and as long as the code works, I'll be cranking things out. I'm really partial to Slim series ROMs, but I was super eager to try out L so I flashed this one. Also, it looks like CM is going to continue to support this thing for the foreseeable future. Once they start their nightly builds, it should be available there, too. Though, without the extra butter.
Thanks for the work and the build.
Click to expand...
Click to collapse
No problems there man I know you do your thing. But.. Do you happen to know how to do that dark ui button
ZX64 said:
Ok. Camera bugs. I don't know. I just cut what lines out the compiler broke because of. And I have no cam. Idk why. My mobile network seems fine.. But come on guys. This is early code, so there's going to be bugs I have no control over. That would be more CMs thing. I just am basically doing what LSX64 did. No boot loop for me either. Weird...
Click to expand...
Click to collapse
Well done! Glad to have you back!
This is working surprisingly well for a first build. The first KitKat builds were total garbage, comparatively.
I'm using it as a daily driver for now. The latest Beta SuperSU will get you properly rooted on LP too. I'll post the link when a bit later (have to find it again), but Google will get you there for now.
Issues (none of which are controllable by the OP) and fixes
Issue one - keyboard doesn't always pop up like it's supposed to. So far I've been able to fix it every time by simply turning my phone sideways, then back.
Issue two - Sometimes not all choices are viewable in pop up boxes. I was able to get around this by changing screen density to 280.
Issue 3 - APN menu doesn't do anything of value. To change apn settings, download sql editor. Open telephony.db which is located at data/data/android.providers.telephony/databases. Then locate the 310120 lines and edit the values as you normally would for your carrier. Your phone will now use the desired APN settings.
Is it possible to turn off your modem like it was in 4.4? I don't see any option for that anywhere. The reason being is that I don't like my phone downloading things when I don't tell it to. It wastes my data, and gets annoying.
ocarinaz64 said:
Is it possible to turn off your modem like it was in 4.4? I don't see any option for that anywhere. The reason being is that I don't like my phone downloading things when I don't tell it to. It wastes my data, and gets annoying.
Click to expand...
Click to collapse
Does this help?
http://forum.xda-developers.com/showthread.php?p=56866237
fizbanrapper said:
Does this help?
http://forum.xda-developers.com/showthread.php?p=56866237
Click to expand...
Click to collapse
Theoretically that is what I was looking for. But now that I'm testing my phone, I realized that I'm not able to actually make or receive calls. Idk if that was because of the widget or what. It might also be a carrier problem.
EDIT - It was a carrier problem, but caused by what, I can't say.
fizbanrapper said:
Well done! Glad to have you back!
This is working surprisingly well for a first build. The first KitKat builds were total garbage, comparatively.
I'm using it as a daily driver for now. The latest Beta SuperSU will get you properly rooted on LP too. I'll post the link when a bit later (have to find it again), but Google will get you there for now.
Issues (none of which are controllable by the OP) and fixes
Issue one - keyboard doesn't always pop up like it's supposed to. So far I've been able to fix it every time by simply turning my phone sideways, then back.
Issue two - Sometimes not all choices are viewable in pop up boxes. I was able to get around this by changing screen density to 280.
Issue 3 - APN menu doesn't do anything of value. To change apn settings, download sql editor. Open telephony.db which is located at data/data/android.providers.telephony/databases. Then locate the 310120 lines and edit the values as you normally would for your carrier. Your phone will now use the desired APN settings.
Click to expand...
Click to collapse
Yeah kk was garbage for the first few months even. So LP way better so far in that way. Glad to have me back? I was here before?
Ok so next build I'll set to 280 and see about that. I have no idea on the KB lol I just used google KB cause it has a dark ui option.
But properly rooted... Big must have there. That I want fixed lol.
I have tried this rom full day, very nice, I just restart sometimes problematic when there is no data connection and GPS is not accurate,
Welcome to SlimLP for the Jewel!
NOTE: This ROM requires the new HBOOT 2.10+ partition table. I may provide links later on how to get that if you aren't up to speed yet. You will also want to use the newest recovery from Captain_Throwback.
Downloads:
Slim-Jewel-LP-5.1.1
Slim Gapps
My older Slim Builds are still available.
Install Process:
Flash the .zip, Gapps, & SuperSU, then reboot. It will dirty flash fine for future 5.1 builds. Make sure you do a clean wipe from other ROMs, or from 5.0 builds.
Word of warning - Let it take some time on the first boot. As much as 4+ minutes, but it's good after that.
Not working - Nothing that I know of yet...
Special thanks to Slim team for all your work, and for guiding me through the new build process.
Also thanks to Captain_Throwback, Fizbanrapper, Tolipohs and ZX64 for your personal help to me along the way.
Sources:
ROM:
https://github.com/SlimRoms (lp5.1)
Kernel:
https://github.com/CyanogenMod/android_device_htc_jewel/tree/cm-12.1
XDA:DevDB Information
SlimLP 5.1.1 for Jewel, ROM for the Sprint HTC EVO 4G LTE
Contributors
ocarinaz64
Source Code: https://github.com/slimroms
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: 2.10+ Firmware
Based On: SlimLP
Version Information
Status: Alpha
Created 2014-12-16
Last Updated 2015-06-07
Reserved
I'll take a look when I get the time. Glad you got it working. I'm happy to see some lollipop ROMs popping up.
Sent from my BN NookHD+ using Tapatalk
One of my favorites. Thanks for bringing it forward. I'll try and install tonight when I'm bored at work.
I installed it tonight. It behaved oddly. I first flashed the ROM and booted it up without gapps as is my habit. I tried to set up wifi and it gave me "authentication error" and never connected (to either of the 2 hot spots I have access to) I also didn't have any network access but didn't worry about it to much yet
I booted back into recovery and flashed gapps as well as a file of commonly used apps I keep so I don't have to download them every time. Anyway once I booted back I still couldn't get WiFi working, and the crazy thing was that it would not even give me a home page, like there wasn't even a launcher installed. So I could get nowhere except for the settings. I decided to restore a nandroid I had, and will give this a try again later with a different build.
Sent from my BN NookHD+ using Tapatalk
Similar experience to mine. I was having trouble with WiFi turning on. It never did fully. It just said "scanning."
bpaulien said:
I installed it tonight. It behaved oddly. I first flashed the ROM and booted it up without gapps as is my habit. I tried to set up wifi and it gave me "authentication error" and never connected (to either of the 2 hot spots I have access to) I also didn't have any network access but didn't worry about it to much yet
I booted back into recovery and flashed gapps as well as a file of commonly used apps I keep so I don't have to download them every time. Anyway once I booted back I still couldn't get WiFi working, and the crazy thing was that it would not even give me a home page, like there wasn't even a launcher installed. So I could get nowhere except for the settings. I decided to restore a nandroid I had, and will give this a try again later with a different build.
Sent from my BN NookHD+ using Tapatalk
Click to expand...
Click to collapse
Boy, that's confusing. Mine worked great. I installed the same way that you did. Well, the only thing I can think of is that, since I'm not S-OFF, I first flash the .zip, and then I go into the bootloader and flash the kernel. Then, after I booted up, I went back to the recovery and flashed Slim Gapps and SU. That shouldn't have any difference in the end result though. Then again, it shouldn't be working for me and giving you problems.
I will say this the only lollipop rom which i have been able to send and recieve mms with no issues. Im s-off and i have zero issues right now. wifi works perfect i can even change apns from the celluar network settings. Great work on this one, i do have a request though, could you incorporate the butttons menu to change double tap and long press actions aswell as the long press back to kill current app?
ocarinaz64 said:
Boy, that's confusing. Mine worked great. I installed the same way that you did. Well, the only thing I can think of is that, since I'm not S-OFF, I first flash the .zip, and then I go into the bootloader and flash the kernel. Then, after I booted up, I went back to the recovery and flashed Slim Gapps and SU. That shouldn't have any difference in the end result though. Then again, it shouldn't be working for me and giving you problems.
Click to expand...
Click to collapse
Strange. Well, I may give it another try. I just realized, I didn't clear cache/dalvik after I flashed the zip of apps I installed... I wonder if that's what gave me issues?
bpaulien said:
I installed it tonight. It behaved oddly. I first flashed the ROM and booted it up without gapps as is my habit. I tried to set up wifi and it gave me "authentication error" and never connected (to either of the 2 hot spots I have access to) I also didn't have any network access but didn't worry about it to much yet
I booted back into recovery and flashed gapps as well as a file of commonly used apps I keep so I don't have to download them every time. Anyway once I booted back I still couldn't get WiFi working, and the crazy thing was that it would not even give me a home page, like there wasn't even a launcher installed. So I could get nowhere except for the settings. I decided to restore a nandroid I had, and will give this a try again later with a different build.
Sent from my BN NookHD+ using Tapatalk
Click to expand...
Click to collapse
I had the same issue with the launcher not working. Took me a while, but figured out you have to pick a launcher in the HOME settings.
Other than that, this rom hasn't given me any issues. So far everything I've tried works good.
I do agree with rontonomo though. A button menu would be nice.
Well, I have it another try last night. I didn't have the issue with the launcher this time. But I still can't use Swiftkey. Every time I try to change the keyboard it just shows a grey block where the keyboard should be.
I read in another thread that some visibility issues could be solved by setting the GPU rendering option in developer options. But that didn't seem to help with the keyboard issue. Unless I did it wrong.
Anyway, seems pretty stable to me so far.
bpaulien said:
Well, I have it another try last night. I didn't have the issue with the launcher this time. But I still can't use Swiftkey. Every time I try to change the keyboard it just shows a grey block where the keyboard should be.
I read in another thread that some visibility issues could be solved by setting the GPU rendering option in developer options. But that didn't seem to help with the keyboard issue. Unless I did it wrong.
Anyway, seems pretty stable to me so far.
Click to expand...
Click to collapse
You are correct. You need to enable developer options, and then force GPU rendering. That's what did it for me.
I posted a new build. Give it a shot. Word of warning: I feel like it took quite a while on the first boot. So give it a fair chance before you assume there is a bootloop issue or something.
ocarinaz64 said:
I posted a new build. Give it a shot. Word of warning: I feel like it took quite a while on the first boot. So give it a fair chance before you assume there is a bootloop issue or something.
Click to expand...
Click to collapse
I'll give it a try. Just a comment on the previous build, though. I wasn't able to get 3rd party keyboard working, even when I turned on the Force GPU rendering option. So I wonder if there's something else in addition to that, or I just have bad luck?
anyway, at least it works with the built in keyboard, so even if it's not my favorite, at least it's not keeping me from using it.
bpaulien said:
I'll give it a try. Just a comment on the previous build, though. I wasn't able to get 3rd party keyboard working, even when I turned on the Force GPU rendering option. So I wonder if there's something else in addition to that, or I just have bad luck?
anyway, at least it works with the built in keyboard, so even if it's not my favorite, at least it's not keeping me from using it.
Click to expand...
Click to collapse
I use Google keyboard. You might give that a shot if you don't want to use AOSP keyboard.
ocarinaz64 said:
I use Google keyboard. You might give that a shot if you don't want to use AOSP keyboard.
Click to expand...
Click to collapse
I may give it a try. I have used SwiftKey for a while and like it, but might be willing to give Google keyboard a try at least until this issue is resolved.
One question I had was is there any good third party apps that you know of and would recommend for capturing screen shots? I'm used to having that option on the quick settings pull down, but since that isn't configurable right now, I'm looking for an alternative.
EDIT: Never mind. I was just reminded that if you hit power and volume-down it will take a screen shot. Thanks.
rontonomo said:
I will say this the only lollipop rom which i have been able to send and recieve mms with no issues. Im s-off and i have zero issues right now. wifi works perfect i can even change apns from the celluar network settings. Great work on this one, i do have a request though, could you incorporate the butttons menu to change double tap and long press actions aswell as the long press back to kill current app?
Click to expand...
Click to collapse
I'm not very good with doing stuff like that unless I have pretty specific instructions on how to do it. If you are looking for a ROM with more features than Slim, you can try my new AICP build.
newest build 5.0.2 just bootloops over and over
rontonomo said:
newest build 5.0.2 just bootloops over and over
Click to expand...
Click to collapse
Thanks for the review. I hadn't actually tested it yet. I'll get right on it.
EDIT - I rebuilt it and I can say it takes a LONG time (over 3 minutes) to boot the first time. But it isn't caught in a bootloop. I posted the newest build for you to use just a minute ago.
Tried the previous build
Thank you for bringing Lolipop to Slim.
I tried your previous build and it looked stable. I had issues with blue tooth. It would pair with my speakers, head set but sound does not come through. It said "play back error" on the phone.
Q&A for [ROM][LP][5.0.2][UNOFFICIAL]BlissPop v1.8 - Updated 01/23/2015
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][LP][5.0.2][UNOFFICIAL]BlissPop v1.8 - Updated 01/23/2015. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Torch and camera
torch don't work, camera take a shoot will crash
zeronatdo said:
torch don't work, camera take a shoot will crash
Click to expand...
Click to collapse
Torch working for me. Google camera from play store works as a replacement for the broken stock camera.
dandrumheller said:
Torch working for me. Google camera from play store works as a replacement for the broken stock camera.
Click to expand...
Click to collapse
Thanks, i will try :good:
GPS still isn't working
I dirty flashed from 1.8 to 2.0 but the gps still doesn't work.
edit: i used the gps tool box app and actually it works now, but it still takes a long time to lock onto GPS, anyway thanks for this rom!
omgitslink said:
I dirty flashed from 1.8 to 2.0 but the gps still doesn't work.
edit: i used the gps tool box app and actually it works now, but it still takes a long time to lock onto GPS, anyway thanks for this rom!
Click to expand...
Click to collapse
Agreed, GPS locks seem slow. Might be what we are stuck with given the cm12 fix.
Havent been on any other gproj ROMs to compare.
Google camera
Does all functions work in the google camera (panorama, photo sphere and lens blur)? Right now I'm using CM12 official with Solid Kernel and only regular photo and video is working.
ryupunk said:
Does all functions work in the google camera (panorama, photo sphere and lens blur)? Right now I'm using CM12 official with Solid Kernel and only regular photo and video is working.
Click to expand...
Click to collapse
Sure, go and find something not working why don't you.
I hadn't tried any of them. Sphere and pano only show black screens, apparently not working. Lens blur is functional
dandrumheller said:
Sure, go and find something not working why don't you.
I hadn't tried any of them. Sphere and pano only show black screens, apparently not working. Lens blur is functional
Click to expand...
Click to collapse
Actually, that's a problem with all the lollipop roms that I have tried for the e970 (and most of the KK, except for some the MAKO based). Seems that our camera is quite difficult to please....
BTW dandrumheller, it seems that you have tried most of the roms out there for our device, which one did you find more stable? At the time I'm using the official CM12 with Solid Kernel and in my opinion is really good (except for the camera and the bluetooth address, which aren't dealer breakers for me). Thanks.
ryupunk said:
Actually, that's a problem with all the lollipop roms that I have tried for the e970 (and most of the KK, except for some the MAKO based). Seems that our camera is quite difficult to please....
BTW dandrumheller, it seems that you have tried most of the roms out there for our device, which one did you find more stable? At the time I'm using the official CM12 with Solid Kernel and in my opinion is really good (except for the camera and the bluetooth address, which aren't dealer breakers for me). Thanks.
Click to expand...
Click to collapse
I actually haven't tried many of the Lp roms. Candy5 has been the most stable and battery efficient for me. Had some issues with bsod on beanstalk 5.0, though 4.4 versions were excellent. Blisspop has been quite stable, but uninspiring in terms of battery life. My phone hates solid kernel - tons of freeze and crash issues. In general I seem to have better luck with mako based roms. Have not tried CM12 yet.
dandrumheller said:
I actually haven't tried many of the Lp roms. Candy5 has been the most stable and battery efficient for me. Had some issues with bsod on beanstalk 5.0, though 4.4 versions were excellent. Blisspop has been quite stable, but uninspiring in terms of battery life. My phone hates solid kernel - tons of freeze and crash issues. In general I seem to have better luck with mako based roms. Have not tried CM12 yet.
Click to expand...
Click to collapse
Cool. I might try Candy5 and see how it goes. Thanks for you answers!
I'm having an issue where the contact names aren't showing up in the stock messenger, or gosms (haven't tried at other). The full number shows, but never the names. I've tried clearing caches and data on contacts and messengers. Tried resyncing the contacts from Google. I've double checked the privacy guard settings. Basically, I've searched around and tried everything I can think of, but still no luck! So I figured I'd ask the experts! Any ideas???
Ive noticed a few other minor issues. ...
I've had the problem with not being able to move the download, as someone mentioned above. Ive had to connect to PC, transfer from phones internal storage to the PC, then back to EXT SD card in the phone.
The 2/13 build does seem to be a little harder on the battery, and runs a lil warm (also mentioned above). I haven't had any crashing issues, but can feel the temp difference over the average.
Possibley related to the heat and battery issues; I noticed that there are two interfaces for the CPU/GPU clocking and scheduling, under the Performance section of System Settings. Maybe there's a conflict happening there? From memory, I don't remember the "Device Control" section being there in the previous build. It seems redundant to have both. Although Device Settings is much more robust, and I would prefer it be integrated instead of keeping the old, minimal interface. Some adjustments to Device Settings, while disabling the other minimal settings on boot, seems to have helped with heat and battery drain a little bit.
No problems with GPS, that I've noticed
Titanium Backup v6 has problem gaining root access in all cm12 ROMs I've tried. To fix, go to Titanium BU Preferences, scroll to bottom, select Troubleshoot Options (or something like that), and highlight/select the option to force the app to use the SYSTEM busybox, not the one baked into Titanium BU. Restart the app, and root works. Also worth mentioning is that you may have to enable root access under Developer Options in System Settings before any app can gain root. Otherwise, no issues with root, or Super SU.
Hi,
After using Beanstalk 4.4 for several months, finally I tried first LP based ROM BlissPop...so far it seem good, only couple of crashes in last week, few issues are present that are highlighted already (like camera panorama not working...battery life affected).
Since last couple days, the strange issue is being encountered, when i get a call, phone rings but there is no interface to receive the call, i then have to go to call screen and there it says "return to the active call" when i click, i get to the screen where i can receive the call. This started happening without any updates so not sure what caused it? I even tried latest version of ROM but same issue present.
Any ideas?
P.S: thanks to everybody who contributes to this excellent site, i have been a regular reader of the site but got to post something today for the first time.
dandrumheller said:
I actually haven't tried many of the Lp roms. Candy5 has been the most stable and battery efficient for me. Had some issues with bsod on beanstalk 5.0, though 4.4 versions were excellent. Blisspop has been quite stable, but uninspiring in terms of battery life. My phone hates solid kernel - tons of freeze and crash issues. In general I seem to have better luck with mako based roms. Have not tried CM12 yet.
Click to expand...
Click to collapse
---------- Post added at 07:35 AM ---------- Previous post was at 06:49 AM ----------
Okay, it turned out to be a feature that some one must have activated on my cell (my little kiddo likes to tinker with my cell)
In App Notification section, Dialer was blocked and that was causing it to not show up whenever i got a call.
Its working great now
idreamido said:
Hi,
After using Beanstalk 4.4 for several months, finally I tried first LP based ROM BlissPop...so far it seem good, only couple of crashes in last week, few issues are present that are highlighted already (like camera panorama not working...battery life affected).
Since last couple days, the strange issue is being encountered, when i get a call, phone rings but there is no interface to receive the call, i then have to go to call screen and there it says "return to the active call" when i click, i get to the screen where i can receive the call. This started happening without any updates so not sure what caused it? I even tried latest version of ROM but same issue present.
Any ideas?
P.S: thanks to everybody who contributes to this excellent site, i have been a regular reader of the site but got to post something today for the first time.
Click to expand...
Click to collapse
system control issue
I went through all 9 pages of the thread and didnt notice anyone else having this issue. In 2.2 under performance and then system control app when one goes to features and then vibration intensity it just force closes on me...is anyone else having this issue? Any suggestions on what I can do to fix?
So I'd like to see what was being discussed in the normal thread for this great rom but the following link isn't working and since I'm a forum baby I'm not allowed to post in the grownup thread... Can anyone help me out with this? Does anyone check this side of the thread?
http://click.xda-developers.com/api...ww.reddit.com/r/oneplus/comm...updateservice/
---------- Post added at 10:43 PM ---------- Previous post was at 10:39 PM ----------
Also, the last build(the one before latest) ... The vibration control in performance>device control was fixed and working.... In the latest build it's broken once again and force closing every time I select it. Just wanted to mention in case no one is aware of it.
So if 4.8.15 is the latest build why does the ota update app found in the app drawer ask me to update to the latest version so my configuration will be appropriate for ota updates? Is there something specific I have to do in order for that feature to work properly?
Lol is this thing on?
In the latest build, was the performance tab in settings cut out of the build?
---------- Post added at 02:40 PM ---------- Previous post was at 02:33 PM ----------
MitchRapp01 said:
In the latest build, was the performance tab in settings cut out of the build?
Click to expand...
Click to collapse
It contained the free app that allowed you to do all kinds of different things with the phone...I forget what it was called....I know part of the file name was x.nameless rom.com
You can try kenvinjoa kernel or nitro kernel
Does this build allow encryption?
Can everyone post a list of stable roms for I717? I don't like going through the trouble of backing up all my data and flashing a new rom only to have it crash multiple times per day and have something like bluetooth not work reliably at all. Maybe some people enjoy playing with that (a lot of the most popular roms at the top of the forum are like this), but I don't!
I'll start the list and say that Beanstalk 4.4 is extremely stable, only had it reset on me twice in one year, and bluetooth works 100%. Only issue is that you can't move apps to SD so you run out of space quick (thanks to kitkat). I'd love to find something above kitkat this stable...
And I'll add some that I have tried and failed:
Candy5: No matter what Gapps I tried (yes pico etc), none of them installed and even after going through every suggestion in the thread I could not get a simple google play installed. Stock browser crashes every 2 minutes.
Pac-rom: Promising but crashes 10+ times per day. Often does not power on unless you boot into recovery and select reboot. GPS is terrible, google maps often loses it's place and gives turn-by-turn directions 60 seconds too late. Stock browser crashes all the time as well.
CM: Bluetooth reliability is terrible. Quincyatt not updated since 2014.
Sounds like you should stick with beanstalk or return the device to stock. When you rooted your device, it opened up security issues so it'll never be as solid as you'd like. What hasn't been updated since 2014?
Sent from my SM-G920P using Tapatalk
gimmeitorilltell said:
What hasn't been updated since 2014?
Click to expand...
Click to collapse
CM for I717.
I don't like going back to stock because IMO it's less secure (heartbleed is a pretty big security hole). If you leave root access disabled and don't download shady apps a custom rom isn't any more insecure.
fwbfwb said:
CM for I717.
I don't like going back to stock because IMO it's less secure (heartbleed is a pretty big security hole). If you leave root access disabled and don't download shady apps a custom rom isn't any more insecure.
Click to expand...
Click to collapse
I don't know what website you're looking at for this SGH-I717 but I can promise you that I personally have kept this phone alive with many updates this year my friend!!! Google my username if you can't find anything on xda? Surely you've used the search button?
Sent from my HTC0P3P7 using Tapatalk
---------- Post added at 12:50 AM ---------- Previous post was at 12:46 AM ----------
gimmeitorilltell said:
I don't know what website you're looking at for this SGH-I717 but I can promise you that I personally have kept this phone alive with many updates this year my friend!!! Google my username if you can't find anything on xda? Surely you've used the search button?
Sent from my HTC0P3P7 using Tapatalk
Click to expand...
Click to collapse
Edit: Just seen you have tried my roms? You should check the dates on them because most are from 2015. If you need more help than that then post in the thread for the rom you need help with. Read read read. Your issue with gapps has been discussed over and over again! Nobody is here to spoonfeed anyone.
Sent from my HTC0P3P7 using Tapatalk
gimmeitorilltell said:
I don't know what website you're looking at
Click to expand...
Click to collapse
Sorry ment stock CM, here download.cyanogenmod.org/?device=quincyatt
Just listing the roms I've tried and have been unusable (crashing 1 or more times per day and something major like bluetooth being unreliable)
Edit: Just seen you have tried my roms? You should check the dates on them because most are from 2015. If you need more help than that then post in the thread for the rom you need help with. Read read read. Your issue with gapps has been discussed over and over again! Nobody is here to spoonfeed anyone.
Click to expand...
Click to collapse
Yes, I tried every suggestion in the thread and it still didn't work. After trying pac-rom for a couple days (and having it crash 20+ times) I just tried wiping it and flashing candy again, and now Gapps with google play worked the first time with no troubleshooting. Shrug.
Seems rock-solid so far though. Can't post in that thread since I have too few posts, so one question, if I do the OTA download for the new 4.0, can I just flash it on top of my 3.9 version or do I need to wipe everything and start over? Also, under Settings, Apps, if I click an app and move to SD card, it will sit there and say "moving" forever. If I exit settings and come back sometimes the app will actually show moved to SD list though.
And the stock calendar app doesn't seem to let me log in, it says "Sign in to get the most out of your device". Then I enter the email I've always used and it says "This account already exists on your device." But there's no other way to actually select that account. What am I doing wrong?
fwbfwb said:
Sorry ment stock CM, here download.cyanogenmod.org/?device=quincyatt
Just listing the roms I've tried and have been unusable (crashing 1 or more times per day and something major like bluetooth being unreliable)
Yes, I tried every suggestion in the thread and it still didn't work. After trying pac-rom for a couple days (and having it crash 20+ times) I just tried wiping it and flashing candy again, and now Gapps with google play worked the first time with no troubleshooting. Shrug.
Seems rock-solid so far though. Can't post in that thread since I have too few posts, so one question, if I do the OTA download for the new 4.0, can I just flash it on top of my 3.9 version or do I need to wipe everything and start over? Also, under Settings, Apps, if I click an app and move to SD card, it will sit there and say "moving" forever. If I exit settings and come back sometimes the app will actually show moved to SD list though.
And the stock calendar app doesn't seem to let me log in, it says "Sign in to get the most out of your device". Then I enter the email I've always used and it says "This account already exists on your device." But there's no other way to actually select that account. What am I doing wrong?
Click to expand...
Click to collapse
Don't do the OTA yet since BB won't let me upload my roms. The ota notification is a fluke. You'll have to flash the rom fresh between trying to find the right gapps which will work on your device. Candy is the most stable of all my builds currently.
Sent from my SM-G920P using Tapatalk
The ota is ready now if you wish to try that.
Sent from my HTC0P3P7 using Tapatalk
gimmeitorilltell said:
The ota is ready now if you wish to try that.
Sent from my HTC0P3P7 using Tapatalk
Click to expand...
Click to collapse
Still can't post in the main thread but:
-If you turn on "Directly show pattern view", nothing shows on the lock screen besides the dots (time, weather, owner info, notifications).
-I had the dreaded bluetooth bug happen the other day, do you get many reports of this? (bluetooth stops working while streaming music, and does not turn back on until a phone reset).
-Stock calendar cannot be logged into (edit: just installed the google calendar from the app store which worked fine)
Unfortunately these are all deal breakers for me but I really like the rom otherwise, I don't want to switch back
Any way to enable HDMI output? (I have the adapter which worked before).
fwbfwb said:
Any way to enable HDMI output? (I have the adapter which worked before).
Click to expand...
Click to collapse
Must be on stock based rom and that being said, not all of those work. I know Saurom, Blackstar Blackjelly and OnlyOne Goldie work.
Edit: on my device.
Sent from my SAMSUNG-SGH-I717
I heavily utilize the "Move to SD card" option because otherwise the default storage doesn't hold more than 10 or so apps, but I've had a problem with Candy5 twice now where my phone will crash, and upon reboot, all the apps that were moved to SD card are gone. Anyone else encounter this?
I wish I could post in the normal thread.
Installed the latest Candy5 20151031, did a complete wipe of everything per the instructions, and after installing 1 app (gmail), the phone reboot the first time gmail opened while placing the gmail widget down.
Here's a list of ROMs I've tested:
BlackSTAR XI - Best ROM for the i717. Super stable and fast.
CM Official - Good, but very buggy. SD card breaks, phone reboots often, HW overlays, etc.
Padawan - Not much new here, just a simple modded version of stock. Very stable but not too fast.
Candy5 - Very laggy, as LP is still in development for i717.
CM11 Unofficial - A bit laggy, HW overlays.
All in all I'm a huge fan of BlackSTAR XI, best ROM I've seen so far.
HackedBotato said:
BlackSTAR XI - Best ROM for the i717. Super stable and fast
Click to expand...
Click to collapse
-on that users phone with their carrier and settings and preferences on their particular device.
HackedBotato said:
CM Official - Good, but very buggy. SD card breaks, phone reboots often, HW overlays, etc.
Click to expand...
Click to collapse
-Which CM official version (10.1, 10.2,etc)? HW overlays can be worked around by switching off in developer options.
HackedBotato said:
Padawan - Not much new here, just a simple modded version of stock. Very stable but not too fast.
Click to expand...
Click to collapse
-stock is intended to be stable.
HackedBotato said:
CM11 Unofficial - A bit laggy, HW overlays.
Click to expand...
Click to collapse
-developer options
HackedBotato said:
All in all I'm a huge fan of BlackSTAR XI, best ROM I've seen so far.
Click to expand...
Click to collapse
-If i had a dollar for every time I've read that.
Search, read, try, choose based on your use.
Sent from my SAMSUNG-SGH-I717
HackedBotato said:
Here's a list of ROMs I've tested:
BlackSTAR XI - Best ROM for the i717. Super stable and fast.
CM Official - Good, but very buggy. SD card breaks, phone reboots often, HW overlays, etc.
Padawan - Not much new here, just a simple modded version of stock. Very stable but not too fast.
Candy5 - Very laggy, as LP is still in development for i717.
CM11 Unofficial - A bit laggy, HW overlays.
All in all I'm a huge fan of BlackSTAR XI, best ROM I've seen so far.
Click to expand...
Click to collapse
Thanks, exactly the kind of stuff I'm looking for, wish there were more user experiences like this posted!
DISCLAIMER: I AM IN NO WAY RESPONSIBLE FOR ANY PROBLEMS ON YOUR DEVICES CAUSED BY FLASHING THESE BUILDS. THE UPSTREAM CODE AND BUILDING IS MAINTAINED BY THE CYANOGENMOD TEAM, NOT ME. I AM NOT ASSOCIATED WITH THEIR TEAM, I AM JUST THE THREAD OWNER.
What is CyanogenMod ? It is an aftermarket firmware for a number of cell phones based on the open-source Android operating system. It offers features not found in the official Android based firmwares of vendors of these cell phones.
Notes: CyanogenMod's stock kernel forces encryption. If you're unencrypted use a custom kernel to keep it.
Also this thread assumes you have kept up to date bootloader and radio !!!
The latest can be downloaded here Shamu Factory images around 1gb!. But i recommand you to flash through TWRP the Bootloader and Radio from here Radio and Bootloader around 60mb.
Installation is simple
1/Download rom + gapps (C-apps optional)
2/flash through recovery (Twrp or CM recovery)
3/Enjoy!!!
----->CyanogenMod Download<-----
----->Open GApps<-----
last--CM13--nightlylast--CM12.1--nightly
Changelog
CyanogenApps
Twrp
Sources: Kernel & Rom
XDA:DevDB Information
[ROM] CyanogenMod14.1 {Nightlies and Snapshots} & Cm13, ROM for the Nexus 6
Contributors
Dead-neM
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Up to date firmware (Fastboot+Radio)
Version Information
Status: Nightly
Current Stable Version: Everymonth
Current Beta Version: Everyday
Created 2016-04-22
Last Updated 2016-11-21
Reserved
Q&A
hum yes post your problem here after some research and you'll be helped
...
Reserved
Do not declare a bug here in the idea that they'll be fixed. Here we discuss, share everything related to our CM N6
so this is where we post from now on?
wmfreak said:
so this is where we post from now on?
Click to expand...
Click to collapse
Yes
Sent from my Nexus 6 using Tapatalk
Yay! Best ROM IMHO.
Can i run this in F2FS partitions Lety me know Thank's in advance!!!
Sent from my shamu using XDA Labs
caballon said:
Can i run this in F2FS partitions Lety me know Thank's in advance!!!
Sent from my shamu using XDA Labs
Click to expand...
Click to collapse
Sure, CM13 has been compatible since at least the beginning of this year
Hi, Thank you all making CM work and supporting this device. I particularly love this phone since this is Motorola (well, sort of) with a AMOLED screen, but more importantly it's the CM's custom features that urged me chose this phone.
I have been using the 160402 nightly with no major problem, only having two live lock screen force closes after reboot. Yesterday I hoped to upgrade to a more recent nightly, but that turned out to fail. I got constant FC's on Phone app, although the LLS ones were gone.
I tried cleaning Phone app's data, disabling xposed, but no help. I don't want to wipe data or otherwise I have to TiBu and then manually set up a ton of things.
The new post OP gives me a hint maybe my radio is too old (MDM9625_104662.22.05.32R) so I'm now trying to flash the latest factory radio and flash the yesterday's nightly again. Also it may be true but not so obvious that my cell signal (Tmobile LTE) gets frequently dropped (no signal/emergency only). I didn't test long before TWRPing back to the old working nightly.
Just want to check out at now if there is any other thing I have missed? Or why am I getting constant Phone app FC?
Edit: I updated the radio to .34R but it didn't help. The Phone app crashes every time I launch it, without giving a report button and it even didn't give me a chance hit the OK button before it disappears. I managed to call somebody with the contacts app and I heard the dialing tone. I was able to hang up the call with the notification action button. Everything looks fine except for the "Dialer" app.
Has the Sprint LTE issue been fixed by CM yet? IIRC the issue is once the Nexus 6 (running CM13 of course) drops down to 3G, it will never go back to LTE.
@cyrildtm
Going to have to bite the bullet and clean flash then.
Lawlrus said:
@cyrildtm
Going to have to bite the bullet and clean flash then.
Click to expand...
Click to collapse
True. Maybe in the future.... Now rolling back to and sticking with the post-april-fool version with the one-time LLS FC. (hey I even survived the MOD one!)
Last time when I did a "clean flash" I TiBu-ed the system settings and all things messed up ending in another clean flash.... and TiBu again but this time with painful manual settings go-over.
Snap camera in this version yet?
cyrildtm said:
True. Maybe in the future.... Now rolling back to and sticking with the post-april-fool version with the one-time LLS FC. (hey I even survived the MOD one!)
Last time when I did a "clean flash" I TiBu-ed the system settings and all things messed up ending in another clean flash.... and TiBu again but this time with painful manual settings go-over.
Click to expand...
Click to collapse
Yeah, I mean I clean flash everything but I know everyone is different.
That's the nice thing about ROMs though, you don't HAVE to flash every nightly, I know I sure don't lol.
If they push a new commit I like then I update, but if everything is kosher, then the hell with it.
Yeah, is the sprint LTE issue fixed?
Sent from my Nexus 6 using XDA-Developers mobile app
cyrildtm said:
Hi, Thank you all making CM work and supporting this device. I particularly love this phone since this is Motorola (well, sort of) with a AMOLED screen, but more importantly it's the CM's custom features that urged me chose this phone.
I have been using the 160402 nightly with no major problem, only having two live lock screen force closes after reboot. Yesterday I hoped to upgrade to a more recent nightly, but that turned out to fail. I got constant FC's on Phone app, although the LLS ones were gone.
I tried cleaning Phone app's data, disabling xposed, but no help. I don't want to wipe data or otherwise I have to TiBu and then manually set up a ton of things.
The new post OP gives me a hint maybe my radio is too old (MDM9625_104662.22.05.32R) so I'm now trying to flash the latest factory radio and flash the yesterday's nightly again. Also it may be true but not so obvious that my cell signal (Tmobile LTE) gets frequently dropped (no signal/emergency only). I didn't test long before TWRPing back to the old working nightly.
Just want to check out at now if there is any other thing I have missed? Or why am I getting constant Phone app FC?
Edit: I updated the radio to .34R but it didn't help. The Phone app crashes every time I launch it, without giving a report button and it even didn't give me a chance hit the OK button before it disappears. I managed to call somebody with the contacts app and I heard the dialing tone. I was able to hang up the call with the notification action button. Everything looks fine except for the "Dialer" app.
Click to expand...
Click to collapse
Hi I'm not using the stock dialer app but the Google one from playstore and i don't have force close so that's not a radio problem but an app problem. In fact having radio up to date normally improve stability over network cell comprehension etc... That's not a big deal but it is better to have a Marshmallow fastboot + radio on a Cm13 build which is Marshmallow based
Cm13 nightly can be really messed up a day but not an other. i think you just catch the wrong one
cyrildtm said:
True. Maybe in the future.... Now rolling back to and sticking with the post-april-fool version with the one-time LLS FC. (hey I even survived the MOD one!)
Last time when I did a "clean flash" I TiBu-ed the system settings and all things messed up ending in another clean flash.... and TiBu again but this time with painful manual settings go-over.
Click to expand...
Click to collapse
Used titanium to restore data of system app have always been buggy for me on every phone tablet that i've possessed. TiBu is usefull for data app
Btw a clean flash doesn't mean to restore data of a previous rom lol
Lawlrus said:
That's the nice thing about ROMs though, you don't HAVE to flash every nightly, I know I sure don't lol.
If they push a new commit I like then I update, but if everything is kosher, then the hell with it.
Click to expand...
Click to collapse
I agree with you. Nightlies sometimes can be awesome but sometimes awful. I went to look at the github page for the dialer app and found they recently put quite a lot of commits so maybe one or two is breaking things but anyways those smart people will figure it out sooner or later. I will just wait and take another free software
I bumped up from a March nightly mainly because of a recent CVE patch (of course that went into the 0401 build mod). Other than that I don't really see any urgent reason for increasing the counters in my daily driver again.
Dead-neM said:
Hi I'm not using the stock dialer app but the Google one from playstore and i don't have force close so that's not a radio problem but an app problem. In fact having radio up to date normally improve stability over network cell comprehension etc... That's not a big deal but it is better to have a Marshmallow fastboot + radio on a Cm13 build which is Marshmallow based
Cm13 nightly can be really messed up a day but not an other. i think you just catch the wrong one
Click to expand...
Click to collapse
I'm now on MOB30D radio (34R shown in settings, didn't copy down the version number shown in bootloader, but it did increase after flashing) and I can always make a phone call even now with an older nightly. so I can confirm the radio is working. I also noticed after flashing and first boot, when CM is about to finish "optimizing apps" the system gets a hot reboot (restart from animation) - oh btw another long-time bug is i never get themed boot animation unless i make a hot reboot (by FCing or any other way). Anyone same here?
From what I can remember the Dialer app has been a failure to me for more than a week. They did make a NPE fix there but seemed no help. Maybe I should install the Google's dialer as you do. I can still remember the AOSP English keyboard endless crash :silly: when I was on CM12.1 with an older device
Dead-neM said:
Used titanium to restore data of system app have always been buggy for me on every phone tablet that i've possessed. TiBu is usefull for data app
Click to expand...
Click to collapse
One of the hard lessons I have learned.
Lawlrus said:
Yeah, I mean I clean flash everything but I know everyone is different.
Click to expand...
Click to collapse
Dead-neM said:
Btw a clean flash doesn't mean to restore data of a previous rom lol
Click to expand...
Click to collapse
Oh lol it never means that! A clean "flash" is no more than 90 seconds to me but a clean "install" means recovering a whole shelf of over a hundred apps from .... the play store .... no the auto re-install only works if i got the same android id
Custom Kernel
I've been using nightlies for quite a while now, since my Nexus One and then my Samsung GS3. I've been reading up on Kernels but there are just so many... and they all say the same thing "Best balance of battery life and performance."
Yes, I could just try all 10 or so out there, but would like to be a little more efficient with my time, so I ask: What do you guys think is a good starting point for trying Kernels? I'm looking for obviously a good balance, but I'm a little more towards the performance side... CM13 has been a little laggy for me, especially with Swapps and rendering backgrounds loaded by chainfire's 500 Firepaper app. And I'll be damned if a colleague's iPhone is faster or more responsive than my Nexus!!!! :laugh:
Franko? ElementalX?
skim7x said:
I've been using nightlies for quite a while now, since my Nexus One and then my Samsung GS3. I've been reading up on Kernels but there are just so many... and they all say the same thing "Best balance of battery life and performance."
Yes, I could just try all 10 or so out there, but would like to be a little more efficient with my time, so I ask: What do you guys think is a good starting point for trying Kernels? I'm looking for obviously a good balance, but I'm a little more towards the performance side... CM13 has been a little laggy for me, especially with Swapps and rendering backgrounds loaded by chainfire's 500 Firepaper app. And I'll be damned if a colleague's iPhone is faster or more responsive than my Nexus!!!! :laugh:
Franko? ElementalX?
Click to expand...
Click to collapse
Try this one https://www.androidfilehost.com/?fid=24499762636000737
This is the latest singularity kernel
Also on post 2 I've post 2 kernel Blackbird and Singularity which in my opinion are the best
I don't like elementalx and Franco but I'm open mind and I'll add link if you find an other good kernel