Related
Q&A for [ROMS][SGH-T679]Mass CM Thread
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
I noticed that the kernels are linked separately from the ROMs. Am I supposed to download and flash the kernels separately? I've flashed about half a dozen ROMs, but I've never flashed a kernel before. From what I've read, though, it sounds like following the same procedure. How about GApps? Do I need to download and flash those, too? And, if so, which pack should I use?
fajrero said:
I noticed that the kernels are linked separately from the ROMs. Am I supposed to download and flash the kernels separately? I've flashed about half a dozen ROMs, but I've never flashed a kernel before. From what I've read, though, it sounds like following the same procedure. How about GApps? Do I need to download and flash those, too? And, if so, which pack should I use?
Click to expand...
Click to collapse
Roms come with a kernel the kernel linked is just special some have overclock under volt etc etc.
Explains the kernel options.
If you do flash them do it after rom.
Gapps you dont technicly have to but yes. (for a standard setup flash gapps)And there should be a gapps linked at the start of rom. If not there will be soon.
Can't import contacts from SIM
Thanks! That clears up a lot.
I installed CM, and it looks very cool and smooth. But when I tried to import contacts from my SIM card, it said "No contacts". I thought maybe it was because I hadn't installed GApps, so I downloaded the "small" GApps package linked from the CM wiki and installed it from CWM. Still no contacts on the SIM card. Next, I thought that maybe my contacts actually weren't on my SIM for some reason. So, I booted back into CWM recovery and restored my previous system. Then, from the phone app, I went to Import/Export > Manage SIM card contacts. Sure enough, all of my contacts were there.
It seems like CM isn't reading my SIM. Any idea what's causing this?
Edit: Never mind. I found out that newer versions of Android don't allow you to store contacts locally. Somehow, the contacts got silently added without me having to import them, though. That's odd, because I don't remember allowing Google to store them in the cloud, and the SIM card appears blank... Oh, well, I installed MyLocalAccount, so I'll see if I can store the contacts locally that way.
@cars1189 running 10/18 build with 10/19(PAgapps micro) and 9/9k^k UV vhm kernel and have had no issues! Thanks for the great work, this runs solid and smooth!
I recently installed 10.2 and am loving it so far. One thing I ran into though was that the cLock widget was showing lots of wakelocks, so I disabled it and battery life has been great. Haven't run into any other issues (other than the screen staying on when off and charging), so this one is a keeper for me.
Didn't see this problem with 10.1, so curious if this is a known issue or not with the cLock widget? Also, are there any other planned updates coming for 10.2?
Thanks.
@RobbyG2112 I noticed it too when I was on 10.2 how ever I only ran it for a week maybe b4 going to cm11 I will say not sure if cars will update 10.2 but if you haven't tried cm11 its super stable and gets updated monthly!!
Thanks for confirming canodroid15, I wasn't sure what the lock screen would show when I disabled the widget but it put the default digital clock and date in it's place so it works out ok. I had disabled the weather and alarm widgets also so wasn't sure why having only the clock widget would cause wakelocks.
I'll probably get around to installing CM11 next, I'm a little slow on upgrading. I had been using CM10 for a long time and finally got tired of seeing the green preview pictures every time I used the camera so decided to go to CM10.1/10.2 recently.
Sure man, about the wakelocks you can try to catch it in a log. Enjoy 10.2 bro!!
kernel for cm11 (SGH-T679)
I recently installed @cars1189's CM11 10-4-14 build for the SGH-T679, with kernel 3.4.104-cyanogenmod-gda4bf58. It took a few tries, but it finally succeeded.
However, there's a slight issue in that I can't access my SIM card contacts. When I try to import from the dialer, it says "no contacts." I've searched around these threads and on the internet, and it seems that it is an issue with the kernel. Would it be possible for someone to recommend or point me to a compatible kernel that would fix that issue for me? Thank you so much for your help!
@valmeras I really don't think it has anything to do with the stock cm kernel but if your on 10/4/14 you can flash 9/9k^k kernels safely on that build about sim contacts idk I use my Google account to sync my contacts hope this helps good luck!
Edit: look for the rom & kernel dates/links in OP.
@canodroid15 - thanks for the response and suggestion. I'll give that kernel a try in the next few days. Not sure this is the solution, but hopefully that works. I've also seen some reference to SIM Tool Kit (STK), but I wasn't able to figure out if it that was the issue.
I would definitely use Google for syncing the contacts once I get this fixed, but for now, that's not possible because my phone is not able to read the SIM properly. I've tried saving a contact to the SIM, but I get an error like "unable to write, SIM is full" but I know for sure that's not the case. Alternatively, I might try to revive my old dumb phone and try to retrieve the contacts that way, then hopefully export that in some way.
@valmeras no prob man, if you have contacts on your sim and u put the sim in the dumb phone and export to storage u could then send a vcard via Bluetooth to the exhibit go into contacts and import from storage then Google sync good luck let me kno if u get it
So I flashed the kernel, but that didn't fix my issue. I do have some more free RAM now though
My old phone doesn't support exporting multiple contacts/vcards via bluetooth, but fortunately, Motorola has a contact exporter utility that exported everything into a CSV file to my laptop via USB. I had to install the drivers for the old phone to be recognised first. I was skeptical it would work given it was a new all-in-one driver thingie and my Motorola was quite old, but somehow it did! The whole process took several hours, but my contacts are now synced!
Sensors/rotation problem
Thanks for posting these ROMs! I just upgraded from Peach Sunrise and I'm really impressed with how well CM11 runs on this phone.
I want to report a problem I had and my solution for the next guy's benefit. With the latest 12-9-14 CM11 ROM, my sensors and compass didn't work correctly. The biggest symptom was auto-rotation did not work at all. Downgrading to the 9-9-14 ROM fixed everything. I didn't try any other ROMs, so they might work too.
Question about getting Google apps running on a SGH-T679
I installed CM 10.2 (cm-10.2-20140627-UNOFFICIAL-ancora_tmo) and it worked fine. I tried a couple different gapps downloads (doing a reinstall of CM10.2 between tries although I may have done that step incorrectly). But no matter what 4.3 gapps build I tried, Google Play Services would crash.
My main goal is to get to 4.3 or higher, so CM 10.2 or CM 11 would be great. (I'm open to other ROMs too. The only reason I'm choosing CM is because those are the only ROMs indicated as still maintained here: http://forum.xda-developers.com/wiki/Samsung_Galaxy_Exhibit_4G )
My question is whether anyone has either CM version running on a T679 and which gapps did you use? I nearly bricked my phone and would like to know that someone else has gapps running okay before I try again.
Thanks!
EDIT: I followed the 2 following threads to install CM 11 with the PA pico gapp package and added a few other Google apps manually from the Play store. I also made sure to reboot several times to make sure everything got fully initialized.
http://forum.xda-developers.com/showthread.php?t=2542793
http://forum.xda-developers.com/showthread.php?t=2397942
masteff said:
Question about getting Google apps running on a SGH-T679
I installed CM 10.2 (cm-10.2-20140627-UNOFFICIAL-ancora_tmo) and it worked fine. I tried a couple different gapps downloads (doing a reinstall of CM10.2 between tries although I may have done that step incorrectly). But no matter what 4.3 gapps build I tried, Google Play Services would crash.
My main goal is to get to 4.3 or higher, so CM 10.2 or CM 11 would be great. (I'm open to other ROMs too. The only reason I'm choosing CM is because those are the only ROMs indicated as still maintained here: http://forum.xda-developers.com/wiki/Samsung_Galaxy_Exhibit_4G )
My question is whether anyone has either CM version running on a T679 and which gapps did you use? I nearly bricked my phone and would like to know that someone else has gapps running okay before I try again.
Thanks!
EDIT: I followed the 2 following threads to install CM 11 with the PA pico gapp package and added a few other Google apps manually from the Play store. I also made sure to reboot several times to make sure everything got fully initialized.
http://forum.xda-developers.com/showthread.php?t=2542793
http://forum.xda-developers.com/showthread.php?t=2397942
Click to expand...
Click to collapse
Hey man! I hope you got it figured out! The only Gapps I use are PA Gapps! There are others but PA is the most complete package & has many options "IMO". You need to use a package that will fit your phone I use the micro package, or the nano. You need to use a package that matches your ROMs version, if your on 4.4.x then use 4.4.x Gapps. If on 4.3 use 4.3 Gapps. PA Gapps has a 4.3 package but its hard to find if you don't know where to look. 4.3 package can be found in the devs (Tkruzze) files on android file host, same place as the 4.4.x Gapps! Sorry if you didn't get answered b4 this I haven't been on this thread for weeks it seems! Hope this helps
So I've been trying out the CM11 OS2SD ROM (the last one in December), but I need to switch back as the bugs are just too much. I need my phone to work and stay charged, which is not happening on this ROM. And since it looks like CM12 is being worked on now that it's not likely the bugs in CM11 OS2SD will get fixed any time soon.
So first the problem. My USB socket on the phone is a little iffy, so I know that is where most of the problem is coming in. However, on the CM11 OS2SD ROM I'm using right now (the one dated 12/25) it frequently says it is plugged in, but is not charging. I've actually seen times where the battery monitor I'm using shows it has discharged the battery as much as 20% before I caught it, yet the status bar battery icon shows it as full and plugged in. On the older ROMs it didn't do this, so something isn't right with how the ROM handles the charging circuits in the phone. Plus, I've had frequent periods of "cpu hogging" (massive CPU load that doesn't seem to come from any one source and that doesn't seem to show up in OS Monitor) that can end up in a crash-reboot of the phone.
So as a result, I want to switch back to an older version of the CM11 ROM. I was using one of the November builds for quite a while, only having to put up with an occasional crash-reboot (the current ROM seems to do this at least every other day, the older one could go a whole week and maybe have it happen only once). What is the process to undo what was done to the phone for the OS2SD build to be loaded?
can't install
I have a problem after installing it via cwm and rebooting, the ensender shows me a screen where I order a factory reset but when I was I do not ensiende the phone
CM 12 Android is upgrading every boot
Ever since I flashed Cyanogenmod 12 every time I reboot it says "android is upgrading optimizing app 1 of 1" and it takes about 8 minutes. There are no odex files in data/app so that cant be the problem. Someone please help. The first time I flashed CM 12 I wiped data and factory reseted but since i seen this happen I flashed Cm 12 again but this time I formatted System, Data, Boot, and SDcard 0 but it still seems to happen. Also, recently my phone has been shutting off by itself every time I turn off the screen. And I know this isn't a hardware problem because the phone never turns off while music is playing with the screen off. It didn't start happening with CM 12. It was already happening with CM11 but it only started happening about a week ago. Im really thankful for cars1189 working on the rom and anyone else who worked on it. You guys are great. Hopefully you can help me out.
hi, my friend called me on a different fone to walk them thru the process of rooting/twrp'ing an h811 using this as a guide ( https://www.youtube.com/watch?v=epcXXkMPRWk ).
and it booted up fine and the touchscreen worked. so i suggested they also try cyanogenmod (11.12.2015 nightly). they booted into twrp and did a backup then factory wipe and installed the cm-12.1...zip.
they booted into cyanogenmod and the touchscreen worked. but the t-mobile lte internet wasnt working so they wanted to go back.
good thing they created a backup first...
so they did a factory wipe then restored their image. when they rebooted the got a message process system not responding and the screen doesnt acknowledge any touch.
we tried going into twrp and doing wipe dalvik/cache ... we tried re-rooting using the steps outlined in the youtube video ... but the same problem persists.
after playing around with twrp and wiping random stuff the fone eventually allowed them to unlock the screen but there was no t-mobile service and after about a minute the screen stopped responding while they were scrolling thru the app-drawer.
i think as of now the only os where the touch-screen works is cyanogenmod; is it possible that cyanogenmod/twrp broke the touchscreen or lte modules in android ?
i thought they were two different os's that used different software/firmware ?
suggestions ?
thanks,
It's possibly a corrupt backup file. I would use TWRP to flash the stock ROM & see what happens.
i assumed re-rooting would clean everything since it uses the send-command program (essentially dd's the whole disk) but i guess not.
we also tried installing the rooted stock rom using twrp but still no joy.
Re-rooting doesn't do anything to the rom or drivers unless you're doing the easy root using a system img file. Then you're pretty much replacing your rom with one that has superuser already on it. That being said, did you upgrade to the 10n firmware/bootstack? The easy root is for 10h firmware/bootstack so that could be the source of your issues.
schneidz said:
hi, my friend called me on a different fone to walk them thru the process of rooting/twrp'ing an h811 using this as a guide ( ).
and it booted up fine and the touchscreen worked. so i suggested they also try cyanogenmod (11.12.2015 nightly). they booted into twrp and did a backup then factory wipe and installed the cm-12.1...zip.
they booted into cyanogenmod and the touchscreen worked. but the t-mobile lte internet wasnt working so they wanted to go back.
good thing they created a backup first...
so they did a factory wipe then restored their image. when they rebooted the got a message process system not responding and the screen doesnt acknowledge any touch.
we tried going into twrp and doing wipe dalvik/cache ... we tried re-rooting using the steps outlined in the youtube video ... but the same problem persists.
after playing around with twrp and wiping random stuff the fone eventually allowed them to unlock the screen but there was no t-mobile service and after about a minute the screen stopped responding while they were scrolling thru the app-drawer.
i think as of now the only os where the touch-screen works is cyanogenmod; is it possible that cyanogenmod/twrp broke the touchscreen or lte modules in android ?
i thought they were two different os's that used different software/firmware ?
suggestions ?
thanks,
Click to expand...
Click to collapse
I relatively had the same problem where I flashed CM and did not like it because it was buggy and so I restored an nandroid and the once working nandroid was plagued with errors of the touchscreen not working, the phone would freeze, system crashes... It ended up being caused by the fact that I did not flash the 10N bootstack update before hand. After I flashed the new firmware and then flashed CM; all of CM's bugs disappeared. I haven't gone back to stock LG software since CM works flawlessly and is now my dailydriver so I cant say for sure if it will fix the stock rom but It probably will since it cleared up all my bugs like the camera not working, videos now playing...
btw to get data working in CM go to settings/mobile networks/Access point Names/ then scroll down and click "T-Mobile US LTE IPv6" and that should fix the internet issues you have since it fixed it for me.
they didnt do anything with the 10n bootstack (i dont know what that is).
maybe cyanogenmod automatically does the 10n thing (how to manually go back to 10h) ?
i assumed re-loading the 5 gb .img file would bring us back to square-1 but i guess not.
also, how to know what bootstack they are running. i told them to check about fone but they told me nothing in there mentions 10n or 10h.
About phone > Software Info > software version will will say h81110n if on 10n.
Same here on Stock...
I have this running stock H81110n software, which I flashed using a KDZ. However, it only freezes up occasionally, and turning the screen on and off once or twice always gets rid of the problem. It's not bad enough for me yet to warrant any factory resets or tweaking so far, but the problem is there...
I successfully rooted my droid (that came with lollipop), using this guide
https://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684
installed twrp backed up the stock OS and installed resurrection remix lollipop rom. I did not install any different modems or radios as I planned to stay on lollipop.
Everything worked great yet after a day or two the display/phone would appear to lock up. I can press power, the display doesn't come on and when (usually) moving the the volume up/down I do hear sounds. Sometimes at this point it will reboot by itself, other times I have to reboot it.
When it comes up it goes through the android is upgrading thing, and sometimes works fine after, sometimes not, regardless eventually this problem repeats.
Thinking it was perhaps RR I tried straight Cyanogenmod, and eventually the rooted stock OS, both have this same problem.
I've tried using it with very minimal installed in the way of apps, same issue.
I've tried saving the log to SD to peer at later, but going through it I don't really see anything obvious to show what the problem is.
I"m wondering if there's a problem with the phone itself (it's a refurb) and am considering unrooting it and returning it.
Anyone seen this or thoughts on what might be the issue?
p.s.
if you happen to have a good link handy to an unrooting guide you might shoot it my way thanks.
thanks in advance!
What versions of the other ROMs did you use? Lollipop also, or Marshmallow? Nougat? For rooted stock ROM did you upgrade to Marshmallow? None of the Lollipop ROMs are supported anymore, so hard to answer for those.
There are ways to grab logs after a reboot, but here's another suggestion...
I use Auto Reboot app (needs root) to schedule a reboot my phone every day while I'm asleep.
This seems to keep the cobwebs cleared out, so the phone runs better. I know you want to find the issue, but maybe it's an accumulation of apps not releasing RAM orb something. This might help prevent that.
thanks for the reply
ChazzMatt said:
What versions of the other ROMs did you use? Lollipop also, or Marshmallow? Nougat? For rooted stock ROM did you upgrade to Marshmallow? None of the Lollipop ROMs are supported anymore, so hard to answer for those.
Click to expand...
Click to collapse
I tried the last released CM lollipop snapshot, as well as the last nightly.
For RR it was last released, "ROM OS Version: 5.1.x Lollipop"
ChazzMatt said:
There are ways to grab logs after a reboot,
Click to expand...
Click to collapse
Yeh I've been saving it to the SD so I can view it after a reboot, I've looked at 4 or 5 of them after the problem occurred and at least to me nothing really stood out
ChazzMatt said:
but here's another suggestion...
I use Auto Reboot app (needs root) to schedule a reboot my phone every day while I'm asleep.
This seems to keep the cobwebs cleared out, so the phone runs better. I know you want to find the issue, but maybe it's an accumulation of apps not releasing RAM orb something. This might help prevent that.
Click to expand...
Click to collapse
Yeh I expect it might periodically need a reboot but if it's just unpredictiably locking up or rebooting on its own it's not very usable.
I think I'm just going to have to try to unroot and return, maybe I'll go with a LG V20 as I don't want to have pay to re-root another one of these and possibly have same issue. Also the whole pay to have some app do something secret to my phone does leave me a bit uneasy.
Kind of a bummer as I'm actually pretty impressed with this device, fast, good battery, takes nice photos, only drawbacks for me are no removable SD and lack of LED notification, but I was willing to live without those given how good everything else was.
thanks
Same here,
I tried with different Roms 7.X, still blocking and display not turning on.
I'd appreciate some help.
Thanks!
Android Version: 7.1.2
Current Rom: AOKP
Kernel: 3.10.107-Stock-bhb27-nougat-kerneL
MrN00b said:
Same here,
I tried with different Roms 7.X, still blocking and display not turning on.
I'd appreciate some help.
Thanks!
Click to expand...
Click to collapse
FWIW and in case it helps you or someone else, I seem to have fixed mine finally, here's what I did.
First I installed latest twrp (mod 4) https://androidfilehost.com/?w=files&flid=39562 (there's a thread on this twrp if you want tor read on it). That in itself didn't fix the issue but did finally let me format and got rid of an 'mkfs.f2fs: invalid option -- r, ERROR=1' type error I used to get.
I installed this stock zip from twrp as described in thread:
https://forum.xda-developers.com/droid-turbo/development/rom-su4tl-49-100-stock-t3390041
It would never actually boot it would shut my phone off not long after showing the boot screen, and I'm not sure if doing that was necessary or not.
Taking some suggestions from here:
https://forum.xda-developers.com/droid-turbo/help/help-request-custom-rom-phone-unlocked-t3767070
I dug up the last official CM 13 snapshot:
https://www.google.com/search?q=cm-13.0-20161221-SNAPSHOT-ZNH5YAO3Y5-quark.zip
sha1: 9a219dd487c27e51b0c5c4922812838f394099c5
Wipe and installed with no gapps and voilà it would boot consistently. Without reinstalling I tried installing pico gapps and it would still boot though it took maybe 15 mins initially.
I want Nougat so I wiped and installed lineage-14.1-20180612-UNOFFICIAL-quark.zip from https://forum.xda-developers.com/moto-maxx/development/rom-t3494646 again no gapps and it also booted fine, whereas previously it would hang on booting. Without reinstalling ROM I tried installing opengapps nano and it would just hang.
I could then no longer get it to boot again, so I reinstalled CM13 no gapps, which booted fine, wipe and install lineage-14.1-20180612-UNOFFICIAL-quark.zip no gapps, and now it boots fine though currently it's taking a while.
I should perhaps note I took twrp backups inbetween steps whenever I had a working boot, (ex before installing gapps), but once the phone went back to hanging on boot, those restores didn't help. Only reflashing CM13 seemed to clear things up.
My ultimate goal is a LOS ish Nougat/Oreo ROM with no gapps using microg, and running tmobile, I'll see what I end up with.
Hi all guys,
yesterday i updated my Mi5 to miui 10 but after rebooting to system i got an annoying bluetooth problem so it just didn't work at all.
So i repeated the same procedure (uploaded another .zip via usb, rebooted to TWRP installed the zip) and as a poor dumb i checked wipe data..
And i don't have any recent backup
So i'm trying to get my data back because there they are, i found two softwares that promise to do the job (minitool and Gihosoft) but both get stacked asking me to root my phone (which i remember i already did). Anyway i followed xda guide about magisk and installed from TWRP, so now i have the app installed but the software still stacked.
Can anybody help me please?
I really need to get those data back.
Ps. now the bloody bluetooth works
Pps. i found this topic and i'm now trying the other software.. Still if anyone has better option they will be more than welcome.
Hello everyone. I am opening this thread for the sake of convenience of us users of this ROM so that we stop hijacking the Oreo version thread and have a "clean" place where we can discuss about our experience with this great ROM. So I suggest anything regarding this ROM to be posted here!
You can find the official builds here: https://get.resurrectionremix.com/?dir=hammerhead
DISCLAIMER: I am by no means a developer or maintainer of this ROM, so this cannot be considered an official support thread, just conversation, plain and simple! Moderators can close this thread as soon as an official support thread opens.
Cheers!
I just installed the rom,came from stock. My first impressions are:
-It took 2 reboots to get the camera working. Installed google camera app since the integrated one doesnt show up on app drawer(you can access it from lockscreen though) and it seems to work kinda bad(picture goes black on it sometimes).
-It runs a bit hotter than stock rom. It might be just me though,I have opened the phone a few times to fix the power button which seems to get stuck for me once in a while.
-The default DPI doesn't seem right,everything looks a little bit smaller than it does on stock rom. There is an option to change it though, I set mine to 380 and it looks about right.
I haven't found any other issues yet.
Another note,I think the rom fixed my notification led lol. It didn't work for me on stock rom for some reason.
Pretty good rom overall,I haven't faced any stability issues yet.
edit: Is there any way to lower the resolution?
I upgraded from RR's Oreo build. Before flashing I repartitioned the phone using the method described here and the even more detailed instructions posted by douguluskaien on page 12 of that thread. The flash went very smoothly and although the phone initially ran hot it cooled back to normal after a few hours of what was probably background processing. With the 1.5G system partition I was able to install the micro version of GAPPS. I've had that experience after flashing new ROMs on other phones as well. I also discovered the bundled camera doesn't work and installed Google Camera. After starting up Google Camera, the original camera worked also. I tried connecting bluetooth headphones, and even though I could pair the headset I couldn't get the phone to send audio - it just kept playing through the phone speaker. I also found the default font size a little small, but changing it to Large in the Font Size menu got it back to what seems like normal.
I have one major issue which I realize is not directly related to the ROM. A custom version of TWRP is required to support the non-standard partitions, and that version is based on TWRP 3.2.3 and doesn't support device encryption. Does anyone know if an updated TWRP will be available that will allow me to encrypt the phone and still do recovery-related stuff?
In summary, this is impressively well along for a build that's only been live for a couple of weeks. This isn't my daily driver so I don't need absolute stability, so this is plenty for me for now. I just won't leave the house with it until I can encrypt.
I've been using this ROM for about a month now as a daily driver, so here's my feedback:
ROM is very nice and smooth and feature rich (as expected for RR). I installed it with Opengapps nano, rooted with Magisk. It works very well with the Pixel launcher I grabbed from here.
Some drawbacks I noticed:
Battery life is rather bad. I get 1h30m SOT at best with very mild usage (mostly site browsing and a little bit of social apps and YT video watching) . Then again I am still using the 5yr old battery that came with the phone...
The phone runs very hot (too hot to hold!) after using it for some time. It cools down rather fast if you let it be for a while, though.
Sometimes the camera is crashing (the notorious "can't connect to camera" error). usually a reboot fixes this.
Sometimes it takes a while for the device to wake up after pressing the power button.
I got some soft reboots under device heavy load. Mostly I get them when using the Rocket player music app, and it tries to load a large music folder. Phone freezes, then soft reboots.
SElinux is set to permissive and the build is signed with test keys. Maybe the first thing is caused by the latter, I don't know really....
Overall, it is a good ROM with room for improvement. However, I am concerned about its maintenance status. No update since May 14, so I keep my fingers crossed.
New build (28/07) uploaded!
hammerheadache said:
New build (28/07) uploaded!
Click to expand...
Click to collapse
I am not able to install it giving me ERROR 7
hammerheadache said:
New build (28/07) uploaded!
Click to expand...
Click to collapse
Do you know about change log??
What features added?
I want to update it tonight
As I state at the first post, I am not a developer, neither I have any involvement in this project and the people behind it. So I can't provide any support apart from my experience as a user.
sacmat said:
I am not able to install it giving me ERROR 7
Click to expand...
Click to collapse
I didn't flash this build so I don't know if it works or not. I have switched to a different ROM. However, could you elaborate? Do you come from another ROM? Did you dirty flash? Is your device repartitioned? Usually error 7 in TWRP means there's not enough system space...
m.morcielago said:
Do you know about change log??
What features added?
I want to update it tonight
Click to expand...
Click to collapse
I do not see any changelog file on the download page. Unfortunately with no official support thread, there are no official answers as well...
I flashed this build this morning by dirty way
Unfortunately Bluetooth is not working
It can find the other devices but can not connect to them
1- How can I fix it?
2-How can I downgrade to previous build?
hammerheadache said:
As I state at the first post, I am not a developer, neither I have any involvement in this project and the people behind it. So I can't provide any support apart from my experience as a user.
I didn't flash this build so I don't know if it works or not. I have switched to a different ROM. However, could you elaborate? Do you come from another ROM? Did you dirty flash? Is your device repartitioned? Usually error 7 in TWRP means there's not enough system space...
I do not see any changelog file on the download page. Unfortunately with no official support thread, there are no official answers as well...
Click to expand...
Click to collapse
Thanks for the idea, I had just repartitioned, so I had format my entire phone, (before that i had taken the backup ), and I had successfully installed the rom, I got an strange issue of WIFI connectivity, as I am not able to connect to my wifi which is having Hidden SSID, but i am successfully connected with the hotspot from my another primary phone. i haven't tested the bluetooth yet.
I dirty flashed the new build this morning. Haven't tried bluetooth or camera yet, but Wifi is working fine. As usual, the phone heated up for about a half hour after the flash and then the temp dropped and stabilized. Battery life is not great, like the May build, and there is often a long delay responding to the power button, especially shortly after power-up, but the build seems pretty solid.
Casting isn't finding anything to cast to in the most recent build. Camera worked fine.
New build available (Aug 4) as seen at ROM's dl page.
Bluetooth pairing now working for me on last release
Hi installed this ROM in clean maner but i got intermitent issue with sim card. Not sure if it is only sim issue or reboot but phone ask my pin code.
Looks like @voidz777 is the maintainer for RR Pie as well:
https://github.com/ResurrectionRemix-Devices/api/commit/8388c5df5069cf04df04facbdc22a2bfd8890185
New build (09/08) in case someone missed it... Link in OP
sacmat said:
I am not able to install it giving me ERROR 7
Click to expand...
Click to collapse
okay so to fix this you will have to repartition your system.
This thread will help you. https://forum.xda-developers.com/go...ment/repartition-nexus-5-repartition-t3844395
Repartitioning is the fix to error 70 while flashing gapps as well as error 7.
New build (Sep 16) available! Link in OP.
princeknockouts said:
okay so to fix this you will have to repartition your system.
This thread will help you. https://forum.xda-developers.com/go...ment/repartition-nexus-5-repartition-t3844395
Repartitioning is the fix to error 70 while flashing gapps as well as error 7.
Click to expand...
Click to collapse
Thank you for the tip, I followed the thread and was able to install RR 7 without any trouble. This might not be the right place to ask, but would you have any info on how to install SuperSU on RR 7, or is there perhaps another root method that we must use? Thanks in advance, I can't seem to find information on it anywhere and rather than continuing to bang my head against the wall I thought I'd ask.