[ROM] [1/7/12] MIUIAndroid [2.1.6] [Glitch v13] - Fascinate Android Development

UPDATE: Due to cdma issues that I have been unable to resolve with the last 2 MIUI releases, I am not sure when I will be able to provide a current MIUI port for the Fascinate. I am still working on finding a fix for this issue in my spare time and will have a current port up as soon as I can. I will, however, post a link to a port with the apps and some of the framework updated. This will not be a full port of 2.1.20 because it will have some of the old framework along with the new framework. I'll have it up sometime today or tomorrow.
All my previous MIUI releases can be downloaded here: http://goo-inside.me/devs/weblexa/MIUI.
Here's the first release of 2012! Been running it for a few hours and seems everything is working very well! Let me know if you experience any bugs.
Download: http://goo.gl/n4n8y
md5: 93ad543c00fefafb1e43d39bae33c283
2.1.6 Full Changelog: http://goo.gl/gYzPg
As requested, link to Glitch v13.1 Kernel below:
Download: http://goo.gl/unvGP
Download MIUI Bloatware:
This flashable zip includes the MIUI apps which originally comes with MIUI that I have removed from my build. Apps include: Gmail.apk, miliao.apk, MIUIStats.apk, and Updater.apk. If I'm missing any, let me know and I'll add them.
Download: http://goo.gl/YbNKw
PATCH FOR NON-VERIZON DEVICES
If you're using a Non-Verizon device, flash this over the weekly release. I take no credit for this patch, as I did not create it. Credit goes to massaint. I'm just including it in my thread so people can find it easier.
Download: http://goo.gl/WZ0T0
md5: 501d61ee0d837db04af8620150c72c0b
Known Bugs:
1. Facebook Contact Sync only syncs all Contacts even when "Sync to existing contacts" is selected
Enjoy!
Follow me on Twitter for instant release notifications: @weblexa

Is there a official port for the mesmerize as well?
Sent from my MIUI'd Mesmerize

Thanks again!

Working great! Thanks! Anyway to add the Reboot to Recovery option to the Reboot menu? I know I can do it on the command-line, it's just easier to have it on the reboot menu. Otherwise, working very smooth....

Stupid question, but how is this different than all the dev builds? Is this like the "official" CM7 release while there are still devs making nightly builds?
Sent from my SCH-I500 using XDA App

Signal bars aren't working
Sent from my SCH-I500 using XDA App

Eris _2.1_2010 said:
Is there a official port for the mesmerize as well?
Sent from my MIUI'd Mesmerize
Click to expand...
Click to collapse
miuiandroid doesn't have an official Mesmerize port at this time. There may be some unofficial ports floating around on XDA.

Rexxe said:
Working great! Thanks! Anyway to add the Reboot to Recovery option to the Reboot menu? I know I can do it on the command-line, it's just easier to have it on the reboot menu. Otherwise, working very smooth....
Click to expand...
Click to collapse
The Reboot Recovery option was removed from the kernel. The only way to get this functionality back into the ROM would be to use one of JT's old kernels that have support for this. The 3-button method works though.

MR H3LLMAN said:
Stupid question, but how is this different than all the dev builds? Is this like the "official" CM7 release while there are still devs making nightly builds?
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
There's not many differences. Each dev tweaks their version a little bit, but this version is the official miuiandroid.com build. There haven't been any tweaks to the ROM. Its exactly the way MIUI China made it. All I did was port it to the Fascinate.

Vinnie981 said:
Signal bars aren't working
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Thanks. I'm working on this now. I will try to have a fix uploaded for this sometime tomorrow. Just to clarify... The signal does work, its just that the signal bar consistently shows no signal when there is a signal.

Any chance we could get the MMS app to split or convert long sms to mms? Right now it just FCs. Thanks in advance.

I'm still getting soft button vibrates, switching from wifi to 3g requires going to airplane mode inbetween, and holding down home on the main screen does not enable torch. So basically same old November build of miui.
Sent from my SCH-I500 using XDA App

weblexa said:
Thanks. I'm working on this now. I will try to have a fix uploaded for this sometime tomorrow. Just to clarify... The signal does work, its just that the signal bar consistently shows no signal when there is a signal.
Click to expand...
Click to collapse
Correct and thankyou
Sent from my SCH-I500 using XDA App

Phasze said:
I'm still getting soft button vibrates, switching from wifi to 3g requires going to airplane mode inbetween, and holding down home on the main screen does not enable torch. So basically same old November build of miui.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Have you wiped cache/dalvik? If that didn't work, have you wiped data? I haven't had any of these issues in any of my November builds, with the exception of the long press the home button to activate the torch app. This feature was removed. Anybody else experiencing any of these issues on my 1.11.18 build?

Alright guys! Bug fix released! Fixes signal bars and MMS! See OP for download link and details.

just flashed 1.11.18.1 last night. coming from 1.11.11.
noticed 3 bugs that im experiencing. yes i wiped properly and tried a battery pull..
1. long press on power button drops the toggles/notification screen and not the reboot menu. i cant get to restart/recovery menu.
2. my icons are randomly disappearing and reappearing.
3. im losing radio during deep sleep..on wake, the 3g icon isnt there. takes about 15 seconds to light up.
Samsung Fascinate :: MIUI 11/11 RickS :: JT 11/3 kernel :: EH03 radio

mrjake1970 said:
just flashed 1.11.18.1 last night. coming from 1.11.11.
noticed 3 bugs that im experiencing. yes i wiped properly and tried a battery pull..
1. long press on power button drops the toggles/notification screen and not the reboot menu. i cant get to restart/recovery menu.
2. my icons are randomly disappearing and reappearing.
3. im losing radio during deep sleep..on wake, the 3g icon isnt there. takes about 15 seconds to light up.
Samsung Fascinate :: MIUI 11/11 RickS :: JT 11/3 kernel :: EH03 radio
Click to expand...
Click to collapse
Thanks for the feedback! I've been looking into this all morning. It seems that if you're coming from a previous release, or someone else's MIUI release, these bugs occur. As a temporary fix, I have added a link to my 1.11.18 release in the OP. Until I get this issue fixed, you will need to flash my 1.11.18 and then flash my 1.11.18.1. I know its an extra step, but that will fix the bugs until I can figure out what's causing it.

Thank you sir for the note..
I know the builds you guys have to work with have been wonky lately, and y'all do the best you can to get these puppies running.
as an add on - something else is borked somewhere as well. and let me preface these additional comments with the statement that it very well could be just my phone, and me screwing something up with it somewhere.
i tried to recover from these using every method i know and i get nothing but bootloops at the MIUI main screen.
ive:
- tried a nandroid restore from the latest backup right before flashing this. it wont boot..get a bootloop.
- tried a nandroid restore from a backup from a week ago. phone will boot but cant get past the lockscreen..its unresponsive.
- tried flashing kernel again - didnt help, still bootlooping.
- wiped everything again, and tried 2 different MIUI builds (yours again, and the 1.11.11) and they still bootloop at the splash screen.
im going to odin back to ed05 and start over.. ive got just enough time to do this before football starts
hopefully you can figure out what bugs china has sent you for the ports.. love what you do with this!
rock on
-
EDIT: Found the culprit. Voltage control is borked somehow. i reinstalled everything from a clean ED05 ODIN. Soon as i set up my voltage control and got it where it needed to be, i selected "save as boot settings" .. i noticed that it said it saved settings to "ect/int/d..." but the last part didnt look right? it had something like d5 at the end of it.. voltage control exited on its own and phone went blank.. took me 4 tries to get it to turn on, and then i got my famous boot looping mess that i have had all day.
i three fingered into recovery, flashed GLITCH to clear the kernel.. booted right up like normal. rebooted into recovery again, used GLITCH to clear the voltage settings, and then reflashed "3 finger fix" kernel by JT. everything running normal for now.. however i do notice now that soon as i jumped into voltage control again - my settings were already set for me? but this time it didnt lock up and die.
there is something wrong with the latest greatest of Voltage control. i would suggest being careful when using it with the 1.11.xx builds..
weblexa said:
Thanks for the feedback! I've been looking into this all morning. It seems that if you're coming from a previous release, or someone else's MIUI release, these bugs occur. As a temporary fix, I have added a link to my 1.11.18 release in the OP. Until I get this issue fixed, you will need to flash my 1.11.18 and then flash my 1.11.18.1. I know its an extra step, but that will fix the bugs until I can figure out what's causing it.
Click to expand...
Click to collapse

Ok, new update package available. See OP for download link. You must be running 1.11.18 in order to update to 1.11.18.1. 1.11.18.1 is just an update package, not the full ROM. If you try flashing 1.11.18.1 without being on 1.11.18, it will fail. Let me know how it works!

1.11.25.1 is now available! See OP for download links.

Related

CM7 Thunderbolt Help Thread

I'll preface with this:
1. I am not a dev.
2. I don't intend to take credit away from any of the CM7 devs.
3. I don't intend to take credit for any of the solutions posted here.
I like to keep up with the main thread, but it has become a little unruly, with the same questions being asked and answered repeatedly. I was thinking we could keep this thread as something of a troubleshooting thread, with known problems and solutions in the OP, in an attempt to keep the main CM7 thread (here) a bit more organized for dev related stuff.
Mods, if this thread is in the wrong forum or inappropriate, feel free to deal with it accordingly.
OK:
----------
CM7 for Thunderbolt
Current Version: RC1.4 (MR2/2.5 Radio Only)
Merged to Mainline: No
Wipe Required: No if upgrading from RC1.2 or RC1.3 (although if you are having ANY problems, first troubleshooting step is to reinstall following a complete wipe). Yes if you are coming from ANY OTHER PREVIOUS VERSION OR ROM
Problems With Known Fixes
Problem:
I just installed CM7, where is the Market?!
Solution:
Not a problem, you just have to install gapps.
- Easiest way is to download and install through ROM Manager: Rom Manager -> Download ROM -> Google Apps.
- Alternatively, you can download and install manually. Link. Flash using Recovery.
Problem:
GPS is not getting a fix
Solution:
1. Be sure that you are on RC1.2, and that you did a full wipe prior to installing.
2. Backup CM7 in Clockwork Recovery.
3. Do a full wipe.
4. Flash a Sense based ROM, such as BAMF.
5. Boot into the Sense based ROM that you flashed in Step 4, and obtain a GPS fix.
6. While your GPS is locked, reboot to recovery. (Hold Power -> Reboot to Recovery)
7. Do a full wipe.
8. Restore the CM7 backup you made in step 1.
9. Boot into CM7. Your GPS should now be working.
Problem:
Inaccurate signal bars/I only have two bars on LTE
Solution:
FIXED ON RC1.3
Problem:
Non-GPS geolocation is (very) inaccurate
Solution:
wraithdu said:
The inaccurate non-GPS location can be fixed by turning on WiFi (does not need to be connected, just ON). Obviously a temporary fix, but works for me - I can get location now in Beautiful Widgets, SiMi Clock, The Weather Channel, and the browser. I increased my WiFi scan interval to 3 minutes to try and help battery. But it beats getting the weather for Guam.
Click to expand...
Click to collapse
Problem:
Choppy Netflix playback
Solution:
Netflix now has official Thunderbolt support. Install the updated Netflix App from the Market.
Problem:
Unlock lag and/or no backlit softkeys
Solution:
Turn off auto brightness, should take care of both of these issues. (thanks to Mustang302LX)
Problems With Fixes of Questionable Effectiveness
Problem:
Problems with in-browser flash
Solution:
chmod 000 /data/data/com.android.browser/app_plugins/com.adobe.flashplayer/.macromedia/Flash_Player/config.data
Varying reports of this working/not working
Problem:
Low volume
Solution:
Since perception of volume is subjective, it's difficult to say whether or not this is a true problem, and whether or not it's been fixed. Slayher has stated that it's been fixed since one of the earlier releases. Another possible solution is here (credit to utkanos), which has been used with varying results - again, volume perception is subjective.
Problem:
Included wireless tethering not working
Solution:
From what I've seen, you will be able to connect to the wireless network, but you will not be able to obtain an IP address. I have found that forcing an IP release/renew upon connecting generally takes care of this problem. On Windows, this can be done with the following:
1. Start -> Run -> "cmd"
2. ipconfig /release
3. ipconfig /renew
Problems Without Known Fixes
Problem:
Streaming audio over bluetooth is choppy
----------
OK, post problems (and fixes, if there are any) and I'll do my best to keep the OP updated in an attempt to keep the main dev thread more organized. When posting an issue, please include:
CM7 version
Kernel
Radio
Wipe
all aosp roms including gingerbread roms reads data strength instead of cellar radio strength. that's why it appears to have less bars. if you search there are mods i believe to give you the appearance of higher signal strength on the forums here.
cm7 and Netflix issues
I believe this is a CM7 issue, as it only happens with is rom and previous versions but I'm not sure if its FPS or just choppiness but Id like to get this fixed other fixes like chmod 000 have not worked.
On a different note I would like to thank everyone involved with CM7 its by far the best ROM.
Thank You Devs.
arkshel said:
I believe this is a CM7 issue, as it only happens with is rom and previous versions but I'm not sure if its FPS or just choppiness but Id like to get this fixed other fixes like chmod 000 have not worked.
On a different note I would like to thank everyone involved with CM7 its by far the best ROM.
Thank You Devs.
Click to expand...
Click to collapse
This is also true for embedded flash videos. If I use the chmod 000 it skips if I go above 360 but it works. Older versions don't let me go above 360 because the video menu, it just closes whenever I open it.
The one issue that bugs me the most about this ROM is that it does not find my location correctly. Not talking about GPS because that works perfectly, but how I'm found through the network does not work. Google Maps works perfectly at finding my location but apps like fancy widget and even google.com locate me in different places.
I live in Buffalo, NY but my phone insists I move frequently around the world. First I'm in Fort Wayne, IN, then Houston, TX, then Nairobi, Kenya, and sometimes in Lawndale, CA.
Something's wrong and no one seems to have a fix that'll work for me. I'm assuming that's cause no one cares about it because its so miniscule.
Tried different radios and GPS status but nothing has worked.
Fix? Slayher?
I am absolutely loving this rom, I flashed it on my girls Droid x and instantly had to have it on my tbolt. GPS works great, more than great, and no other issues except two things.
First, when streaming Pandora or slacker through bt the skip like crazy, but when played through the phones speaker they're fine. No big deal.
Secondly I must be doing something wrong because my battery life is terrible. I have an extended battery that the phone ate through in 8 hours moderate use. And my stock battery is dropping about 30% an hour...
I'm not a noob with screen time out to 10 mins and brightness all the way up, so its got to have something to do with my CPU settings. I'm using set CPU to over clock to 1450. Tried different goveners. I assume there's different kernels out there I'm gonna have to try out, what kernel is included? Running mr2 ota
Sent from my ThunderBolt using XDA App
Cm7. 2
Stock kernel
OTA radio
Full wipe
Volume is too low. Volfix. Zip hasnt worked for me. Otherwise Cm7 is flawless.
Yes i cleaned my ears.
Suggestions?
Thanks for this thread and to the devs for their work
Sent from my ThunderBolt using XDA Premium App
i flashed it and im running the mr2 radio. it didnt install the market and im not able to download another and it work properly. when i go into recovery and try to flash the market zip it aborts. anyone know how to fix this?
dearbeloved said:
i flashed it and im running the mr2 radio. it didnt install the market and im not able to download another and it work properly. when i go into recovery and try to flash the market zip it aborts. anyone know how to fix this?
Click to expand...
Click to collapse
What rom were you running before, and did you wipe?
In any case, easiest solution would be to install GAPPS from ROM Manager.
Can't seem to connect to my home wifi network. Anyone else experience this issue?
From looking through the main thread, saw one suggestion, which didn't work for me: post 7360
OTA MR2; full wipe; RC1.1; gapps; set up accounts; cache wipe; RC1.2
bliang said:
Can't seem to connect to my home wifi network. Anyone else experience this issue?
From looking through the main thread, saw one suggestion, which didn't work for me: post 7360
OTA MR2; full wipe; RC1.1; gapps; set up accounts; cache wipe; RC1.2
Click to expand...
Click to collapse
Try a full wipe before installing 1.2. I believe that was recommended by slayher.
Is it only your home wifi, or are you having trouble with all wifi connectivity?
problem: voice to text works intermittently and not at all with any background noise
corrective solutions taken that haven't corrected problem: installed talkback, kickback and google voice search.
CM 1.2
OTA radio
stock kernel
full partition wipe, also formatted SD prior to install
Let's merge our threads, yeah?
http://forum.xda-developers.com/showthread.php?t=1125466&highlight=CM7
joshnichols189 said:
Let's merge our threads, yeah?
http://forum.xda-developers.com/showthread.php?t=1125466&highlight=CM7
Click to expand...
Click to collapse
Yes! Sorry, thought I did a thorough search. Apparently not. Mods please merge.
Sent from my ThunderBolt using XDA Premium App
minazaki said:
Try a full wipe before installing 1.2. I believe that was recommended by slayher.
Is it only your home wifi, or are you having trouble with all wifi connectivity?
Click to expand...
Click to collapse
Didn't think it would matter. Did a full wipe and reinstalled -- everything working okay now. Thanks
Installed CM7 and purchased ROM Manager Premium. I enabled advanced mode in settings. But I still can't download Cyanogenmod ROMs via ROM Manager? It doesn't appear in the list. Anyone have a similar problem, and preferably a solution? What's going on? Thanks.
darknesis said:
Installed CM7 and purchased ROM Manager Premium. I enabled advanced mode in settings. But I still can't download Cyanogenmod ROMs via ROM Manager? It doesn't appear in the list. Anyone have a similar problem, and preferably a solution? What's going on? Thanks.
Click to expand...
Click to collapse
it's not officially supported by cyanogenmod yet, therefore you can't obtain it via ROM manger.
you can find CM 1.2 here: http://forum.xda-developers.com/showthread.php?t=1049542
make sure you download the ROM and the Gapps
Oh ok, thanks!
Sent from my ThunderBolt using XDA Premium App
darknesis said:
Oh ok, thanks!
Sent from my ThunderBolt using XDA Premium App
Click to expand...
Click to collapse
feel free to push the "thanks" button under my post
stayin100 said:
I am absolutely loving this rom, I flashed it on my girls Droid x and instantly had to have it on my tbolt. GPS works great, more than great, and no other issues except two things.
First, when streaming Pandora or slacker through bt the skip like crazy, but when played through the phones speaker they're fine. No big deal.
Secondly I must be doing something wrong because my battery life is terrible. I have an extended battery that the phone ate through in 8 hours moderate use. And my stock battery is dropping about 30% an hour...
I'm not a noob with screen time out to 10 mins and brightness all the way up, so its got to have something to do with my CPU settings. I'm using set CPU to over clock to 1450. Tried different goveners. I assume there's different kernels out there I'm gonna have to try out, what kernel is included? Running mr2 ota
Sent from my ThunderBolt using XDA App
Click to expand...
Click to collapse
I'm interested to know the answer to this battery issue. Which kernel is best for battery life/stability? I'm running stock right now, but I really haven't ran it long enough to get good usage stats.

[ROM][CM10][CM10.1][CM-10.2][CM-11.0][GT-S7710] Samsung X Cover 2

This is a dedicated thread for the CM10, CM10.1 and CM10.2 port for the Samsung X Cover 2 (GT-S7710). The port is in a beta state. The source is based on the CM port for golden from OliverG96!
Recovery
A working CWM port with minor issues is discussed and available here.
Download
All files are available here or here.
Changelog CM 10:
2013/07/26: Initial preview
2013/07/27: Fixed Wifi
2013/07/29: Fixed GPS
2013/09/04: Userdebug build to get rid of red frame
discontinued, but porting changes for the camera, USB etc from cm-10.1 branch should not be a big deal
Changelog CM 10.1:
2013/09/15: Alpha release 0:
Phone and mobile data
GPS
WIFI (tethering is untested and probably broken)
Bluetooth (tested a2dp and a headset/car)
Audio (EQ is untested)
Front and rear camera work. Video recording is broken!
USB MTP works. PTP is untested.
SD card
adb
Flash light
Video playback is broken.
2013/09/30: Alpha release 1:
Fixed video playback and recording.
CM updates and account wizard added.
2013/10/14: Alpha release 2:
AOSP lpm animation
Updated video processing (Thanks Oliver)
CM Updates
2013/10/20: Alpha release 3:
Fixed Torch
Removed automatic brightness menu
2013/10/27: Alpha release 4:
Fixed WIFI tethering
Changelog CM 10.2:
2013/11/02: Alpha release 5:
Bump to CM 10.2 - same functionality as in Alpha 4.
CWM build on cm-10.2 branch is broken - use from cm-10.1 if needed.... fixed.
2013/11/19: Alpha release 6:
CM Updates
Added fix for low volume in incoming calls (Thanks Oliver!)
Some source cleanup
2013/11/24: Alpha release 7:
CM Updates: Wallpaper, Bootanimation
2013/12/05: Alpha release 8:
CM: Build with cm-10.2 stable sources
2014/01/12: Alpha release 10:
CM: Source update.
2014/02/04: Alpha release 11:
CM: Source update.
Fixed random reboots.
Changelog CM 11.0:
2013/12/31: Alpha release 9:
Preview CM11 image. OMX/Camera is broken. Just for testing and not ready for daily usage. Needs latest recovery and full wipe.
Known Issues
BT hands free. Connection/pairing works, but the audio path is broken.
stock MMS app
Source
The source is stored in my github account.
Questions and Bug
Please do not contact me directly if you encounter bugs or you have questions about the port. When you're not yet allowed to post is this thread - post somewhere else, but don't send me a PM. Thanks for that.
Disclaimer
Don't flash this image unless you really know what you're doing! I'm not responsible for any damage what-so-ever done to your phone, as with any ROM, you accept this risk. You use this software at your own risk.
Thanks to:
OliverG96 for his CM10/CM10.1/CM10.2 port of golden.
TeamCanjica for the u8500 common stuff.
TheBoegl for hosting the images
You're great, its super:good:
That's the problem with me -
And again you did a very good job :good:
Can I flash the new rom with GPS like an update, so that i do not have to install everything again?^^ just wipe cache and dalvik and leave the rest as it is?
Btw now the camera is the last thing missing for my holiday^^, then I can test your rom for 2 weeks outdoor
So keep on your excellent work :victory:
after flashing your latest rom, there is sometimes a red frame around the display.
Hello, I used the new Custom ROM, I liked but did not know why constantly loses coverage of the mobile operator. I have not tried GPS, WIFI is working well.
I hope you like comment on Custom ROM to help clear the error that occurred. This is not a criticism. I have great respect for you and what you do with it.
Cheers.:laugh:
BTW battery lifetime is much better than on stock rom. 6 h without charging, gps and wifi off, a lot of facebook, whatsapp, email and some gaming, 91% left :good: seems to be that you can use the Xcover now for a couple of days without charging
p.Lipov said:
Hello, I used the new Custom ROM, I liked but did not know why constantly loses coverage of the mobile operator. I have not tried GPS, WIFI is working well.
Click to expand...
Click to collapse
Thanks for testing! I didn't notice any difference by now - the link has been pretty poor with the stock image as well. I'll put it on my list and make a comparison. Anyone knows a app to plot the link quality?
cheers,
flxo
aufdroge said:
And again you did a very good job :good:
Can I flash the new rom with GPS like an update, so that i do not have to install everything again?^^ just wipe cache and dalvik and leave the rest as it is?
Click to expand...
Click to collapse
In this special case: yes. The image from the 29th just has one config file added. Sometimes it's simple
after flashing your latest rom, there is sometimes a red frame around the display.
Click to expand...
Click to collapse
Yep. I noticed that also. No concrete idea where it comes from but I think there's a problem with the settings provider....
cheers,
flxo
GPS is not working for me, any idea how to fix it?
Sent from my GT-S7710 using xda app-developers app
Camera and flashlite(torch) not work
USB connection - windows cannot find drivers
Red frames around display
Wifi ok
Gps ok
Bt not tested
Nice work, thx :good:
Hi guys,
thanks for testing! I will be off for a week. So maybe you can fix some issues in the meantime?
cheers,
flxo
I like the Custom ROM. I can not wait to get the new clean fix. Phone with him is not the same, it is great. Thank flxo
Hey, I am really interested in testing this, just want to verify that I flash latest from CWM correct? I am fairly used to custom roms, but this is my first samsung and they seem to do things a bit different so better ask then sorry. ^^
Great job, keep on goin'. Thank you for your work...
EDIT: flashed it and gapps, and works fine. feels faster than stock. thx
Problems:
- sponatneous reboots
- red frame
Hello,
Loving the mod, could not wait to get away from Samsungs mess.
Does anyone experience call drops after a couple of minutes? (Sound cuts out but does not seem to disconnect)
Also:
Red frame and reboots
Nevertheless, keep up the good work!
Hey, has this project moved somewhere and I missed it or is it just a low peak atm? I am asking as it seemed to have a lot of activity last month but nothing this. I would love to see CM10 fully working on the Xcover 2 as the phone has no custom roms what so ever that I can find.
Superbia said:
Hey, has this project moved somewhere and I missed it or is it just a low peak atm? I am asking as it seemed to have a lot of activity last month but nothing this. I would love to see CM10 fully working on the Xcover 2 as the phone has no custom roms what so ever that I can find.
Click to expand...
Click to collapse
Me too... *push*
Superbia said:
Hey, I am really interested in testing this, just want to verify that I flash latest from CWM correct? I am fairly used to custom roms, but this is my first samsung and they seem to do things a bit different so better ask then sorry. ^^
Click to expand...
Click to collapse
Yep - thats the latest version.
Hi,
Superbia said:
Hey, has this project moved somewhere and I missed it or is it just a low peak atm? I am asking as it seemed to have a lot of activity last month but nothing this. I would love to see CM10 fully working on the Xcover 2 as the phone has no custom roms what so ever that I can find.
Click to expand...
Click to collapse
I've been off for three weeks and hope I can continue working on the port in the next days. Next item is the camera and some annoying stuff like the need to enable/disable the airplane mode once to get mobile data to work..
cheers,
flxo
flxo said:
Hi,
I've been off for three weeks and hope I can continue working on the port in the next days. Next item is the camera and some annoying stuff like the need to enable/disable the airplane mode once to get mobile data to work..
cheers,
flxo
Click to expand...
Click to collapse
Sweet. Your vacation was well deserved! I was just curious if CM team had shut you down for some unknown reason or if you just changed phone etc
The red frame is gone, but therefore an errormessage pops up, when I try to install something from google play --> unknown errorcode "-24". I have flashed the rom 4 times, but nothing changes
Sent from my GT-S7710 using xda app-developers app

[5.0.1][ROM] Cyanogenmod 12.0 Semi-Official [12-05-2014]

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,

Unofficial SlimLP 5.1.1 for Jewel - 6/7 Build

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.

[ROM] CyanogenMod14.1 {Nightlies and Snapshots} & Cm13

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--nightly​last--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

Categories

Resources