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.
Related
Okay so I took the plunge and installed my first ROM (ICS Collective Base4) among other things with my SGH-I717M (Bell). Everything went very well and here are the issues that despite reading over 500 pages in threads related to these issues, I have not been able to solve them (workarounds, sure). I'm hoping that others can confirm these glitches and whether or not they have been able to remedy them:
-Upon boot, "Unfortunately, the process com.android.phone has stopped". Annoying, but doesn't seem to affect anything. No workaround or solution.
-Baseband "unknown". Tried ODIN flash install AND coming from completely stock phone via CWM flash, neither has remedied this problem. Doesn't seem to affect anything so don't really care.
-Stock calendar application missing - really don't like some of the other calendars, but I can't seem to find the APK file in any other ICS ROM's out there, so I gave up on this. So workaround, no solution.
-Time zone wrong. Workaround is to deselect automatic network management and select the correct timezone. Reverts back to incorrect upon rebooting so apparently only a workaround and no solution.
-Upon booting setCPU max/min speeds are incorrect and you have to open the application for it to correct the speeds. Perhaps it's just the widget that's broken, but for now it's a workaround and I can't seem to figure out a solution. Quandrant benchmarks seem to indicate that if I don't do this, the performance is affected as if the speeds are 1242max/384min and not 1512max/384min.
-Phone freezes on "Power Off", have to hold power button - camera flash goes off and then restarts. Workaround seems to be to use terminal emulator or other applications to reboot, etc. Don't know if there's a solution to this.
-Wallpaper incorrectly zooms - workaround: market applications. No solution that I can find yet.
-Unrelated to the ROM, but V6 Supercharger - I can only get it to report 50% supercharged, even after modifying my services.jar file and following all "step 8" instructions (that was an undertaking!!!). Don't know what's up there, but maybe some of you super-techs have figured it out.
-Only 624MB of RAM available instead of 700MB+ with GB. Haven't heard anything about why this is, so no solution or workaround.
-Doesn't seem to be an ICS keyboard available? I think this can just be installed from the market but I haven't tried it so not sure.
I'm sure there's other things like with Swype, tethering, etc.. etc... that are not working but this is just what I've noticed within the last 8 hours of flashing and trying to set-up and configure. Any comments or helpful suggestions for a n00b like me?
Thank you for any and all feedback. Thank you to all the developers working hard on this fresh release to bring us a solid ROM!
Calender: http://dl.dropbox.com/u/569065/Calendar.apk
Remember, this is a leaked firmware, these bugs are within that leak itself and a few of these issues have been addressed (unknown baseband, etc..) And will be fixed when we release the actual full ROM. this is just the base we shared in the mean time. A few are still present likesome settings not sticking through boot, and the power menu hanging.
Ithink is ur phone acting weird. Only the setcpu speeds not sticking and issue about wallpaper which can easily be fixed by using quicpics are the two issues my phone had. Just dnt use any cpu controller i noticed phone goes to sleep when no cpu controller while when there is cpu controller screen off speed sticks to 384 or 192
Sent from my SAMSUNG-SGH-I717 using xda premium
studacris said:
Remember, this is a leaked firmware, these bugs are within that leak itself and a few of these issues have been addressed (unknown baseband, etc..) And will be fixed when we release the actual full ROM. this is just the base we shared in the mean time. A few are still present likesome settings not sticking through boot, and the power menu hanging.
Click to expand...
Click to collapse
Absolutely. And considering what I've read about previously leaked versions of Android over the years, this one performs like a champ. Can't wait to see what comes out next, but I figured from what I've read this one works well enough to go the distance and install. Thanks again collective!
Felinos11 said:
Ithink is ur phone acting weird. Only the setcpu speeds not sticking and issue about wallpaper which can easily be fixed by using quicpics are the two issues my phone had. Just dnt use any cpu controller i noticed phone goes to sleep when no cpu controller while when there is cpu controller screen off speed sticks to 384 or 192
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
Yeah, just thought I would put my experience out there if it helps anyone or if someone could help me lol. It's very likely some of these are isolated problems, but most of them are problems with the leaked version. I uninstalled setCPU because I think you're right, something likes to nom nom the battery when the screen is off.
Oh and here's something odd which I don't know if anyone else has experienced with ICS or GB, but Terminal Emulator doesn't allow me to type anything unless I capitalize each individual letter. Which of course is useless because it can't accept commands in caps. When I press any key in lowercase it's like I haven't done anything. I had to switch to the pen mode where I scribe each letter and then it puts lowercase letters in for me. Anyone know what's up with this?
This is probably not the best Rom to run for your first flash. I would try one of the official releases in the development thread, unless you are an official tester for The Collective...
Can't wait till they release an official ROM ...
Sent from my SAMSUNG-SGH-I717 using Tapatalk
mk2 love i see im a vr lover Mr helios
Sent from my SAMSUNG-SGH-I717 using XDA
Helios909 said:
Oh and here's something odd which I don't know if anyone else has experienced with ICS or GB, but Terminal Emulator doesn't allow me to type anything unless I capitalize each individual letter. Which of course is useless because it can't accept commands in caps. When I press any key in lowercase it's like I haven't done anything. I had to switch to the pen mode where I scribe each letter and then it puts lowercase letters in for me. Anyone know what's up with this?
Click to expand...
Click to collapse
I had that issue in GB... In ICS it seems to be intermittent- sometimes it just works others it doesn't...
And regarding the baseband, not sure about the Collective rom, but DAGr8's ICS rom displays the modem correctly on my Bell Note.
I also had the timezone issue- strangely enough when I disabled network time and timezone, I also stopped get random slowdowns and ANRs.
Sent from my SAMSUNG-SGH-I717 using XDA
We've got the baseband unknown issue fixed in the full ROM. We just haven't released it. Still working on a couple things before we're comfortable sharing.
Hi, here are my thoughts;
1. Flash a CWM ICS modem(fixed it for me). If you cant find a modem use Dagr8's inital version of the ICS leak, it will successfully flash the modem(unlike the initial collective version(post 501 thread). The main point is to ensure you have the correct baseband(should not say unknown).
2. For now, dont supercharge the ICS leak until you have a stable running OS.
3. After fixing the baseband unknown issue(#1), reflash the collective post 501 ICS rom. It is stable, and the cleanup of the bloat was started already.
4. After installing #3, factory reset your phone.
At this point you should have a bloated, but error free ICS on your computer. Make a CWM backup, install titanium backup, and rip out the junk APK's(widgets, samsung/att garbage). Doing this will provide longer battery life and better performance.
No other wipe scripts are needed.
Factory reset BEFORE flash. The cwm script in the zip itself formats /system and /cache before it writes anything.
And the baseband unknown thing isn't a big deal. Its not that you don't have a modem at all, everything still works you get mobile data, its just the os doesn't properly report it.
if you like what you got, i say sit tight, we're working on the full ROM. You won't be disappointed
studacris said:
No other wipe scripts are needed.
Factory reset BEFORE flash. The cwm script in the zip itself formats /system and /cache before it writes anything.
And the baseband unknown thing isn't a big deal. Its not that you don't have a modem at all, everything still works you get mobile data, its just the os doesn't properly report it.
I say if you like what you got, i say sit tight, we're working on the full ROM. You won't be disappointed
Click to expand...
Click to collapse
Would be cool if you guys could make a minimalistic style rom without all the makeup and cosmetics and focused on performance
We think its cooler to do BOTH
Cause the guys at Samsung must have left their seeing eye dogs at home when it came time to theme
most of us don't usually do minimalistic... once a stable rom gets out you can expect a variety of themes. Sit tight.
studacris said:
We've got the baseband unknown issue fixed in the full ROM. We just haven't released it. Still working on a couple things before we're comfortable sharing.
Click to expand...
Click to collapse
THanks Cris, thats all im waiting for to make the jump to ICS-----is the collectives official - unofficial ics dev thread.
Studacris said:
"We think its cooler to do BOTH
Cause the guys at Samsung must have left their seeing eye dogs at home when it came time to theme"
LOVE IT!... and CAN'T WAIT! Thank you for all you do... and have a few beers on me. PayPal confirmation number: 6RE28092GB801952P
fishing.laguna.madre
NoteI717
Powered by The Unofficial
Thanked you in the ROM threads, but again, very appreciated. Thank you.
Sit tight. what we got cooking is gonna be tasty
Same experience here
well done guys excellent base.... Having the same experiences as helios909...
Really looking forward to the the fully packaged version. Not experiencing problems with cpu speed set on boot.
Face unlock not work properly yet. Device hangs on reboot as reported. Auto update time bug exists. Baseband version unknown. Phone crashes on initial boot. But recovers.
New voice type engine is amazing. As demonstrated here.
The CyanogenMod team has recently created CM10.1 nightlies for the Nook Tablet. Let's take a look at it.
At first sight it looks pretty good, and looks very clean (ditto). There is no gapps preinstalled (also ditto), so you need to flash the latest gapps ROM. This is official CM10.1, so nothing has been removed. After flashing gapps, you have to go through a brief setup process, and you're ready to go. This is a nightly build, but if reflashing a ROM every single day and losing all of your data is what disturbs you, think again; CM10/10.1 has a built-in updater tool, which is available in Settings<About tablet<CyanogenMod updates. I flashed this ROM yesterday, and today there was a new nightly (ditto), and I went into the updater, flashed the new update, and it simply was like an android upgrade when it booted after flashing the ROM from the tool. NOTE: To use the tool, you need CWM/TWRP. This does not work with other recoveries. For me, I don't even know why they call this ROM nightly. It is running perfectly stable for me. If you are on unofficial CM10, and want 4.2, but are disturbed by the alpha CM10.1s, you might want to check this out because for me, under my terms, it should at least be deemed RC. Already. If you are running another kind of CM10.1 (unofficial), you might also want to check this out because it is official, after all. If you are already running some other kind of 4.2 which you are happy with (like PA or PAC-man), you may or may not want to check this out. The new interface does have the pie launcher, due to CMs recent decision to include it, so if you are running PA simply for that, you might want to check this out.
UPDATE: Looks like the CM team has build a new RC2 at this point (which I am running of course). It eliminates basically all of the bugs I described earlier, and is much more stable than other 4.2.2 ROMs I have looked at (I have not looked at Xylon, Liquid, Carbon, or Slim however) (I have looked at PAC and Ubuntu) (Tried to flash Slim once but failed something about /tmp/sideload.zip, I reset to factory). The only problem I have had with it is that initially the Play Store didn't work (same with 20130518 nightly). I think it was the fact that I dirty reflash ROM updates. Wiping fixed it. Also, I occasionally see freezes or delays. But still, more stable than others, and I am in high anticipation for stable
Recommendations: If you are on anything, check this ROM out. Flash it. Just flash it already. It's awesome. I recommend this ROM over anything xD.
The biggest problem is battery drain too fast. Because Nook Tablet is not compatible with standard Android hardware and it's eBook Reader, I always wish it's better battery life for using every day as eReader Plus with fully Android features
Sent from my Nexus 4 using Tapatalk 2
Does anyone know how I could go about solving the deep sleep issue? I just need the alarm clock to work everything else I like. They have done a great job.
somerandomname said:
Does anyone know how I could go about solving the deep sleep issue? I just need the alarm clock to work everything else I like. They have done a great job.
Click to expand...
Click to collapse
Have you tried a different clock app? Or, changed governor settings? What happens if you use setcpu (app from play store) and forced min to say 200. What make you think it's a deep sleep issue? Are you using better battery stats app to see what's happening?
Or better yet, what have/haven't you tried?
alevineman said:
-
At first sight it looks pretty good, and looks very clean (ditto). There is no gapps preinstalled (also ditto),...
Click to expand...
Click to collapse
Please forgive me, but I have to ask before it drives me nut;What are you "ditto"-ing? Is this in reply to something else that I've missed? Sorry to ask, but I find myself completely fixated on those "dittos". Yeah, crazy, (and osessive!) I know, but I'd hate to lose out on some vital info around the beloved NT! :laugh:
somerandomname said:
Does anyone know how I could go about solving the deep sleep issue? I just need the alarm clock to work everything else I like. They have done a great job.
Click to expand...
Click to collapse
This ROM MAY NOT have the problem of WIFI radio staying ON during sleep.
My particular NT has problems using CPUtuner ( a way to trigger to turn off WIFI when the screen goes out, or if the NT goes to sleep): CPUTuner disables the radio, but leaves WIFI set as ON, like the built-in wifi sleep management.
I now use AutomateIT, which turns WIFI off, rather than turning off the radio. This works well for me. So then deep sleep works.
The problem with this, as I just got reminded, is that anything downloading (with the browser, or like magazines in Zinio... STOP or FAIL when the screen goes out.)
I just put on 041613 nightly, and the Nook disconnects from the AP when it sleeps.
I'll have to see about power usage, but it looks good. (nope, lost 10-12% overnight.... back to turning WIFI off with a service)
This ROM also seems to default to landscape. Mine has 0 degree as Landscape. 'Power widget' auto-orientation off/on is not working for me.
I had to run Fix Permissions and/or cache format in CWM 6.0.3 (what I already had loaded. I did not load the recovery in the first post. I don't know what version it is) to fix a mediascanner error at boot with this ROM.
Zinio won't connect to it's servers with this ROM.
WPA2 connections sometimes fail and need retries to get connected.
The good is that this ROM feels great, so I'm sticking with it. Most responsive I've used so far (although 'bout the same as 2/6 AOSP ROM).
Started with CM7, then updated to demetris_I's CM10 build (huge thanks for a great product) then did the CM Update from my table this morning 04/19 nightly and it is is smooth and fast. Huge props to CM and everyone that made this a possibility.
I have a Pattern Lock set and when I either re-boot or power on, the lock screen get's skipped and it launches directly to the home screen with a Clock has stopped error. But if I then launch a program and come back to the home screen it locks and I have to enter my pattern. Any body else seeing this?
Is there a way to enable larger multitasking images like in the sgt7 ROMs? And tablet ui only in landscape?
Sent from my Barnes & Noble Nook Tablet
mkenney725 said:
I have a Pattern Lock set and when I either re-boot or power on, the lock screen get's skipped and it launches directly to the home screen with a Clock has stopped error. But if I then launch a program and come back to the home screen it locks and I have to enter my pattern. Any body else seeing this?
Click to expand...
Click to collapse
I have, honestly. I'm seeing problems now. However, I'm still satisfied, especially because I use WidgetLocker anyway, but I used to use pattern lock and had the same problem. Hopefully fixed by M4 or M5 or something.
alevineman said:
I have, honestly. I'm seeing problems now. However, I'm still satisfied, especially because I use WidgetLocker anyway, but I used to use pattern lock and had the same problem. Hopefully fixed by M4 or M5 or something.
Click to expand...
Click to collapse
Many thanks. Actually installed a newer nightly, I think 4/24 directly via EMMC clearing cache/factory reset and it fixed the issue
asawi said:
Please forgive me, but I have to ask before it drives me nut;What are you "ditto"-ing? Is this in reply to something else that I've missed? Sorry to ask, but I find myself completely fixated on those "dittos". Yeah, crazy, (and osessive!) I know, but I'd hate to lose out on some vital info around the beloved NT! :laugh:
Click to expand...
Click to collapse
I mean, it's stock CM. And basically no ROM has gapps.
Sent from my Barnes & Noble Nook Tablet using xda app-developers app
alevineman said:
I mean, it's stock CM. And basically no ROM has gapps.
Sent from my Barnes & Noble Nook Tablet using xda app-developers app
Click to expand...
Click to collapse
My Nook Tablet 16GB is still on it's way so I haven't been able to do any rooting and flashing, just reading. Question, does CM 10.1 have microphone support so we can Skype and use Google Now?
GameGuru41 said:
My Nook Tablet 16GB is still on it's way so I haven't been able to do any rooting and flashing, just reading. Question, does CM 10.1 have microphone support so we can Skype and use Google Now?
Click to expand...
Click to collapse
All good. Just tested using my nook, which has 4/30 nightly loaded as of this morning and voice search works well as does Skype for voice, of course no video, since Nook doesn't have a camera
Just installed the Nook on Fire Showtime kernel on top of the official CM 10.1 ROM. It is AWESOME!!!
Sent from my Barnes & Noble Nook Tablet using xda app-developers app
heissman said:
Just installed the Nook on Fire Showtime kernel on top of the official CM 10.1 ROM. It is AWESOME!!!
Sent from my Barnes & Noble Nook Tablet using xda app-developers app
Click to expand...
Click to collapse
Ditto. I am running RC2 with 3.2 and loving it. I really should update Cm, but hate the pain.
Sent from my Barnes & Noble Nook Tablet using Tapatalk HD
Moving up to the official CM 10.1 wasn't painful at all. In fact, it was probably the most pain-free experience I've had with my NT
Sent from my Barnes & Noble Nook Tablet using xda app-developers app
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,
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