Related
So today CM 7.2 RC1 was released for all supported devices. Here are some links
http://www.cyanogenmod.com/blog/cyan...rc1-is-upon-us
http://get.cm/?device=speedy
So I wiped my device clean and flashed the zip, and after booting up successfully (shows the screen that says "Touch the Android to begin") it just reboots on its own, and the process repeats. I double checked that the md5 was clean, and I tried wiping and flashing several times with the same results. Is this happening to anyone else?
Same for me here.
Probly a stupid question but if I'm going from 7.1 to 7.2 do I NEED to do a full wipe? Can't I just wipe dalvik, cache and flash?
Sent from my PG06100 using XDA
THEsunnypiglets said:
Probly a stupid question but if I'm going from 7.1 to 7.2 do I NEED to do a full wipe? Can't I just wipe dalvik, cache and flash?
Sent from my PG06100 using XDA
Click to expand...
Click to collapse
Usually you could but had risk of error, with me, it just made the reboots happen at 5 minutes intervals instead of 10.
Not sure if this is coincidence or not, but after about 5-6 reboots, I skipped the sign in, then quickly turned off the GPS. The phone stopped rebooting, even after turning the GPS back on. I have no clue what fixed this, but it has stopped rebooting now.
cloverdale said:
Not sure if this is coincidence or not, but after about 5-6 reboots, I skipped the sign in, then quickly turned off the GPS. The phone stopped rebooting, even after turning the GPS back on. I have no clue what fixed this, but it has stopped rebooting now.
Click to expand...
Click to collapse
Cool but is audio working? And why is every single RC release for speedy by CM unstable? This GPS reboot thing has been a issue before but they don't seem to fix it lol.
sparksco said:
Cool but is audio working? And why is every single RC release for speedy by CM unstable? This GPS reboot thing has been a issue before but they don't seem to fix it lol.
Click to expand...
Click to collapse
Audio is working fine for me.
cloverdale said:
Audio is working fine for me.
Click to expand...
Click to collapse
I see, I'm thinking the reboot issue has to do with the kernel. Try a different kernel and that should fix it.
sparksco said:
I see, I'm thinking the reboot issue has to do with the kernel. Try a different kernel and that should fix it.
Click to expand...
Click to collapse
Since this discussion is going in two threads, I will let everyone know that using one of Sparksco's kernel ports fixes the reboot issue.
Edit: Though the kernel ports fix the GPS reboot, they take away all audio.
cloverdale said:
Since this discussion is going in two threads, I will let everyone know that using one of Sparksco's kernel ports fixes the reboot issue.
Edit: Though the kernel ports fix the GPS reboot, they take away all audio.
Click to expand...
Click to collapse
Agreed. I have tried just about every kernel I can get my hands on. The ones that boot have no audio, the rest simply don't boot or bootloop or reboot after a moment or two (haven't tried the default kernel and turning GPS off/on yet).
I fail to understand how they let 7.2 out for the Shift when it isn't booting up reliably for the majority of users. At what point did it become safe to say it is a Release Candidate? I'm beginning to think it more a Return To Your Previous ROM Candidate.
[edit]
I just flashed back the default kernel with GPS disabled and it booted without issue. Enabled GPS after boot and it works without reboot. Rebooting phone with GPS enabled still results in bootlooping, tho.
So, here's my proposed solution to those still having problems, want audio, and can live without GPS being enabled all the time (since no audio also means no call audio, this should be the majority of you):
1. Flash the 7.2 zip.
2. Immediately flash pershoot kernel (the ones that boot without audio, like v14 port).
3. Boot and immediately disable GPS.
4. Reboot into recovery and reflash the 7.2 zip. (NO NEED TO WIPE ANYTHING BUT DALVIK CACHE, for those who are already setup on 7.2 or coming from 7.1)
5. Boot normally.
NOTES:
A. If you attempt to boot or reboot with GPS enabled, you will get caught in a bootloop again. Simply follow the steps above again to turn it back off.
B. You CAN turn GPS on after boot and use it without issue. But you MUST disable before powering off or rebooting, else you'll have to do the above steps again.
C. Even if you can live without audio, I advise AGAINST using the pershoot ports on 7.2 for daily use. Something is causing that kernel to drain battery at about 3-5 times the normal rate (may have to do with the audio issue), regardless of CPU speed.
Hope this helps until this gets officially fixed somehow.
[/edit]
Is there a fix for the camera issues in the latest build. Since 1012 build, I'm experiencing lots of reboots and my phone get stuck all the time when I'm using the camera. I have tried every build since then up until the latest 1108, including the latest gapps. All of them get my phone stuck or reboot. Please help
Sent from my One X using xda app-developers app
etai-ab said:
Is there a fix for the camera issues in the latest build. Since 1012 build, I'm experiencing lots of reboots and my phone get stuck all the time when I'm using the camera. I have tried every build since then up until the latest 1108, including the latest gapps. All of them get my phone stuck or reboot. Please help
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
I haven't had that problem since before the two EXPERIMENTAL builds. Most of that time I've been using the leaked 4.2 camera, but I did use the stock camera a few times with no issue. I would try doing a clean install (wipe everything) of the latest nightly, if you haven't tried that yet.
etai-ab said:
Is there a fix for the camera issues in the latest build. Since 1012 build, I'm experiencing lots of reboots and my phone get stuck all the time when I'm using the camera. I have tried every build since then up until the latest 1108, including the latest gapps. All of them get my phone stuck or reboot. Please help
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Haven't had that problem. The only issue I have with the CM10 camera is the high pitched whine you get when recording video. Seems to go away if you have headphones pulled in while recording?
No reboots though. I did notice that the default kernel for ViperXL rebooted a few times per day until I changed "Keep Wi-Fi on during sleep" to "Always." I know that's not related to the camera, but that was a problem when I was running MIUI on my Desire and fixed the reboots on my One XL in ViperXL.
- Joel
lauterm said:
I haven't had that problem since before the two EXPERIMENTAL builds. Most of that time I've been using the leaked 4.2 camera, but I did use the stock camera a few times with no issue. I would try doing a clean install (wipe everything) of the latest nightly, if you haven't tried that yet.
Click to expand...
Click to collapse
I already did a clean install, with factory reset, and even formatted the sdcard. Didn't help.
Further more, I'm experiencing lots of reboot with the latest nightly (ever since the EXPERIMENTALs). Playing a game for a few minutes, reboot. Surfing the web for a few minutes, reboot. Opening skype, reboot. But the reboots are not consistent, sometimes it happens and sometimes it does not.
All I wanted is a stable JB experience, and I know CM10 is still in beta, but still, I have too much problems.
yeah, I've had the same high pitched whine issue. also, my camera is unable to record in 1080p, the files just never save
I've been going back and forth from stock to CM7.2, to CM9, CM10, Hellybean, etc... and I am having a problem with the Keyboard in anything past 7.2 or stock. The "Q" "A" "W" keys will sometimes not work. I have the close out the messaging app or whatever I am using and wait 5 minutes before the keys are operational again. I've also tried multiple kernel/rom combinations and still seem to get it.
I can not repeat this problem in Stock or CM 7.2, nor can I find a calibration option for the keyboard/screen.
Currently, I am running CM 10 stable with Semaphore 2.5.0 kernel. Any ideas?
fitch220 said:
I've been going back and forth from stock to CM7.2, to CM9, CM10, Hellybean, etc... and I am having a problem with the Keyboard in anything past 7.2 or stock. The "Q" "A" "W" keys will sometimes not work. I have the close out the messaging app or whatever I am using and wait 5 minutes before the keys are operational again. I've also tried multiple kernel/rom combinations and still seem to get it.
I can not repeat this problem in Stock or CM 7.2, nor can I find a calibration option for the keyboard/screen.
Currently, I am running CM 10 stable with Semaphore 2.5.0 kernel. Any ideas?
Click to expand...
Click to collapse
What keyboard are you using and are you restoring it with tibu or doing a fresh install?
BWolf56 said:
What keyboard are you using and are you restoring it with tibu or doing a fresh install?
Click to expand...
Click to collapse
I am doing a fresh install, wiping cache/data/dalvik each time. I don't use a TiBu/nandroid backup. The keyboard is the stock CM one.
fitch220 said:
I am doing a fresh install, wiping cache/data/dalvik each time. I don't use a TiBu/nandroid backup. The keyboard is the stock CM one.
Click to expand...
Click to collapse
Have you tried different keyboards (from the market)?
BWolf56 said:
Have you tried different keyboards (from the market)?
Click to expand...
Click to collapse
I got Swype installed and the problem went away. It seems that it is only the stock android keyboard (ASOP) that comes with cyanogenmod.
Anyone know why this would happen, and if there is some set of files I need to clear maybe?
Clear the keyboard data, delete the LatinIME.apk and /system/lib/libjni_latinime.so, then install the 4.2 keyboard: http://forum.xda-developers.com/showthread.php?p=33506020
Bout damn time I made a thread
Sent from my SGH-T699 using Tapatalk
It IS about time.
ok so the cm wiki page says to use cwm. any reason i can't use twrp?
Gibson99 said:
ok so the cm wiki page says to use cwm. any reason i can't use twrp?
Click to expand...
Click to collapse
Shouldn't be any reason you couldn't use TWRP. I'm pretty sure nard himself uses it. The CWM was a CM project for a long time, and still the recovery built within it. Everyone pushes their stuff.
been running M7 for about a day now. had one fc with touchdown, my work email client, but otherwise looks good. surprised i had to manually change build.prop to set the dpi. i'm not blind, so i hate the trend towards gigantic fonts even on smallish screens like this one.
i also wasn't able to use tibu to restore securid from my old phone (vzw droid4) but i suspect that app uses some system properties like imei to create its security, so it can't be moved... not a problem. just have to do clean in stall and reimport the token.
one thing i noticed even in cm11m2 on my d4 as well as on this phone in cm11m7 is that the included sms app doesn't actually have a dark theme, and that sticks out like a sore thumb. even when you check the box for dark theme in the sms app itself, it's still white. not a huge deal obviously but doesn't match the rest of cm's normal polish.
Gibson99 said:
been running M7 for about a day now. had one fc with touchdown, my work email client, but otherwise looks good. surprised i had to manually change build.prop to set the dpi. i'm not blind, so i hate the trend towards gigantic fonts even on smallish screens like this one.
i also wasn't able to use tibu to restore securid from my old phone (vzw droid4) but i suspect that app uses some system properties like imei to create its security, so it can't be moved... not a problem. just have to do clean in stall and reimport the token.
one thing i noticed even in cm11m2 on my d4 as well as on this phone in cm11m7 is that the included sms app doesn't actually have a dark theme, and that sticks out like a sore thumb. even when you check the box for dark theme in the sms app itself, it's still white. not a huge deal obviously but doesn't match the rest of cm's normal polish.
Click to expand...
Click to collapse
The "use dark theme" option only applies to the quick reply pop up windows. The option is conveniently listed in the "quick reply" section.
orange808 said:
The "use dark theme" option only applies to the quick reply pop up windows. The option is conveniently listed in the "quick reply" section.
Click to expand...
Click to collapse
doh, you're right. my point still stands about messaging not matching the rest of cm's theming. i guess they expect people to just use chomp, go, handcent or whatever other app... i like the standard one in cm tho. except for how light it is.
What did change from the blobs for the builds after 14 /06 ?
Running 14/06 now, really good, battery charging issues are gone (i think), because a new kernel/other blobs.
Where can you find more info about blobs changes (propetary) ?
I've been having data and sms issues lately since I switched to cm11 or any of the latest 4.3.3 builds. Was there a recent radio firmware released?
Gh0sTly said:
I've been having data and sms issues lately since I switched to cm11 or any of the latest 4.3.3 builds. Was there a recent radio firmware released?
Click to expand...
Click to collapse
Which nightly?
Are you on T-Mo? Are you using a third party messenging app?
Did you wipe your data and cache before you flashed?
Gh0sTly said:
I've been having data and sms issues lately since I switched to cm11 or any of the latest 4.3.3 builds. Was there a recent radio firmware released?
Click to expand...
Click to collapse
which build are you on? i'm running cm11-20140608-Snapshot-M7 (which is 4.4.2, not 4.3.3) and have no issues to report so far. i haven't given it a full shakedown yet - still haven't tried BT or GPS but so far so good. watched netflix on the bus this morning and never had an issue. my wife and i text a lot and haven't had issues w/ that either. this evening i'm going to try out BT with my elm327 obd-ii adapter and if i have time, test audio over an avantree cara adapter. i started google maps a couple times and it found me quickly and accurately but i haven't run gps for more than a minute or so at a time so i don't know how it'll do. maybe i'll turn it on while on the bus this afternoon and see if it works well for the whole ride home.
robuser007 said:
What did change from the blobs for the builds after 14 /06 ?
Running 14/06 now, really good, battery charging issues are gone (i think), because a new kernel/other blobs.
Where can you find more info about blobs changes (propetary) ?
Click to expand...
Click to collapse
I updated ****. we're benefiting vicariously from the d2 kit-kat release
Sent from my Nexus 7 using Tapatalk
After a few minutes of playing with the CM M5 smartphone burned and became slow. Now the smartphone with the stock firmware does not burn more but it is slow. It works well this M7? You recommended me?
For a few months I used CM kitkat but I had to do a wipe. Now I do not know how to install the CM. I'm using the stock firmware.
To install:
1 rooted smartphone.
2 I copy "cm-11-20140608-SNAPSHOT-M7-apexqtmo.zip" in memory of the smartphone.
3 CWM 6.0.1.2 "install zip from sdcard -> choose zip from sdcard" I select "cm-11-20140608-SNAPSHOT-M7-apexqtmo.zip"
4 updates fail
What I'm wrong?
thanks for the help
Balthasar85 said:
After a few minutes of playing with the CM M5 smartphone burned and became slow. Now the smartphone with the stock firmware does not burn more but it is slow. It works well this M7? You recommended me?
For a few months I used CM kitkat but I had to do a wipe. Now I do not know how to install the CM. I'm using the stock firmware.
To install:
1 rooted smartphone.
2 I copy "cm-11-20140608-SNAPSHOT-M7-apexqtmo.zip" in memory of the smartphone.
3 CWM 6.0.1.2 "install zip from sdcard -> choose zip from sdcard" I select "cm-11-20140608-SNAPSHOT-M7-apexqtmo.zip"
4 updates fail
What I'm wrong?
thanks for the help
Click to expand...
Click to collapse
First, use the most up-to-date recovery; I'm pretty sure that cwm 6.0.1.2 isn't it if I see 6.0.4.7 on other devices. I like using TWRP personally, and there's a thread in this forum for that. The outdated recovery is probably the main problem right there for the failed flash.
Second, it doesn't look like you wiped anything in your steps. No factory reset, not even wiping cache and dalvik. Most people do a clean flash (that's a factory reset in recovery) when troubleshooting a failure to install a custom ROM.
Try using the latest recovery, wiping at least cache and dalvik, and see if it helps.
Good luck
Sent from my Nexus 5 using Tapatalk
reaper000 said:
First, use the most up-to-date recovery; I'm pretty sure that cwm 6.0.1.2 isn't it if I see 6.0.4.7 on other devices. I like using TWRP personally, and there's a thread in this forum for that. The outdated recovery is probably the main problem right there for the failed flash.
Second, it doesn't look like you wiped anything in your steps. No factory reset, not even wiping cache and dalvik. Most people do a clean flash (that's a factory reset in recovery) when troubleshooting a failure to install a custom ROM.
Try using the latest recovery, wiping at least cache and dalvik, and see if it helps.
Good luck
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
i second this. my steps were:
1- boot to download mode, install twrp
2- boot to recovery, flash CM
3- while still in recovery, flash gapps if you want them (make sure you have the correct version of gapps from the CM site)
4- still in recovery, wipe cache and dalvik
5- still in recovery, do factory reset
6- reboot normally (it's called 'system' in twrp) and start using phone
note that there is no need to copy/flash SU at any time because CM is already rooted.
using nightly 22/06 my phone slowed down to unusable slow, flashed 24/06 yesterday.
Never had this before on cm nightly's for the relay.
And the charging (usb) problems aren't over yet (sometimes it works fine for a few hours, sometimes a few minutes).
Did a clean install a week ago (didn't solve anything).
robuser007 said:
using nightly 22/06 my phone slowed down to unusable slow, flashed 24/06 yesterday.
Never had this before on cm nightly's for the relay.
And the charging (usb) problems aren't over yet (sometimes it works fine for a few hours, sometimes a few minutes).
Did a clean install a week ago (didn't solve anything).
Click to expand...
Click to collapse
Ok. Now, find out what version of cpu you have and get some logs to help them track down your problems.
There's a search box in the corner.
I don't have any of the problems you are describing and I am betting the developers do not, either.
orange808 said:
Which nightly?
Are you on T-Mo? Are you using a third party messenging app?
Did you wipe your data and cache before you flashed?
Click to expand...
Click to collapse
I am on T-Mo, I get this via the default android messaging app as well as hangouts, but I also have times where mobile data refuses to work as well.
Right now, I'm having this issue on 11-20140608-Snapshot-M7-apexqtmo. I did wipe data and cache before I flashed. I'm not sure what is causing my issue.
I am tempted to reflash it back to factory, and take it back under my total care and get it replaced for a S5, but I really like my keyboard. :crying:
did you wipe cache and dalvik after flashing the rom? the only quirk i've noticed on m7 is that if i don't reboot every couple of days, my work email program (touchdown) likes to get slow and crashy while composing emails. going to the recent apps drawer and closing everything there usually fixes that. gps and bluetooth work fine even at the same time and battery life is great. after having tried multiple roms on my droid4 and having gps and camera issues, i am pleasently susprised how stable cm is on this relay (which i've only had a couple weeks now).
Gibson99 said:
did you wipe cache and dalvik after flashing the rom? the only quirk i've noticed on m7 is that if i don't reboot every couple of days, my work email program (touchdown) likes to get slow and crashy while composing emails. going to the recent apps drawer and closing everything there usually fixes that. gps and bluetooth work fine even at the same time and battery life is great. after having tried multiple roms on my droid4 and having gps and camera issues, i am pleasently susprised how stable cm is on this relay (which i've only had a couple weeks now).
Click to expand...
Click to collapse
I even tried that too. My phone's about a year and a half old now. I've noticed recently if the keyboard is out, or i'm holding the phone sideways, and I get a call, the phone app crashes over and over till i rotate it upward so the display is vertical, then it stops crashing(all while the phone is still ringing so I can still answer it.)
Q&A for [ROM][5.1.1] SlimLP - Skyrocket [ALPHA][UNOFFICIAL]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][5.1.1] SlimLP - Skyrocket [ALPHA][UNOFFICIAL]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Steveromingagain said:
Installed with philz and twrp,,clean installs.
Error on both for unfortunately com.android. phone has stopped,pop's up every 2 secs and would not let do anything,like logcat. Rebooted system and installed gapps ,no change.
Click to expand...
Click to collapse
Same issue here. Wiped data, system, cache, dalvik, and installed with latest Slim_mini_gapps.
Archetype3791 said:
Same issue here. Wiped data, system, cache, dalvik, and installed with latest Slim_mini_gapps.
Click to expand...
Click to collapse
Update coming that should help fix this...
Thank you NoSpamDan! I am looking forward to checking it out.
How do I access recent apps? Double clicking on home soft key like CM doesn't work.
Shadester9 said:
How do I access recent apps? Double clicking on home soft key like CM doesn't work.
Click to expand...
Click to collapse
I have the same problem. I have searched and searched but been unable to find any way to access Recents. Long pressing the home key does nothing. I also tried the Recently app but could not figure out how to get it to activate.
pretty awesome !
after flashing "Slim-skyrocket-5.1.1.alpha.0.3-UNOFFICIAL-20150607-0208" I keep asking myself "why my battery is not draining" It's like -0.5%/hr during deep sleep.
Sealy64 said:
I have the same problem. I have searched and searched but been unable to find any way to access Recents. Long pressing the home key does nothing. I also tried the Recently app but could not figure out how to get it to activate.
Click to expand...
Click to collapse
Set a custom key action for Home key long-press to Recents... Under the navigation menu
Hi, guys, I need some help, I just installed it and almost everythings works nice but it keeps giving me troubles with Whatsapp. Anyway to fix it? It keeps forcing stop.
Vladybarr said:
Hi, guys, I need some help, I just installed it and almost everythings works nice but it keeps giving me troubles with Whatsapp. Anyway to fix it? It keeps forcing stop.
Click to expand...
Click to collapse
I tried a fresh install from play store . its working fine now.
heisenberg-001 said:
I tried a fresh install from play store . its working fine now.
Click to expand...
Click to collapse
I did so. It's working cool now.
But I'm not being able to play any video. Any idea why?
Vladybarr said:
I did so. It's working cool now.
But I'm not being able to play any video. Any idea why?
Click to expand...
Click to collapse
Not sure. Maybe stock video player doesn't support that video format.
Try MX player and tell me which video format is not working? Oh boy ! ?
[Q&A] [ROM][5.1.1] SlimLP - Skyrocket [ALPHA][UNOFFICIAL]
NoSpamDan said:
Set a custom key action for Home key long-press to Recents... Under the navigation menu
Click to expand...
Click to collapse
When I posted my statement on 6 May 2015, I was running 2 May 2015 version of the ROM. Recents works now but did not back then.
problems formatting /data /cache to f2fs format
I am using the latest twrp tried to change the format of the two listed and recieved the msg that they were invalid partitions
---------- Post added at 02:53 AM ---------- Previous post was at 02:50 AM ----------
Vladybarr said:
I did so. It's working cool now.
But I'm not being able to play any video. Any idea why?
Click to expand...
Click to collapse
have you flashed the audiofix file it fixed my facebook video issue i had
SlimLP - Skyrocket
Hey everyone. I am currently 20150607-0208 version. I am thinking of switching to the latest version with the F2FS support. I need guidance on how to install this specific rom. Just need to confirm few things. So i wipe date and cache to F2FS and i wipe dalvik cache and system in the normal way we usually do? Then I flash rom and gapps? Thats it?
sanusaeed said:
Hey everyone. I am currently 20150607-0208 version. I am thinking of switching to the latest version with the F2FS support. I need guidance on how to install this specific rom. Just need to confirm few things. So i wipe date and cache to F2FS and i wipe dalvik cache and system in the normal way we usually do? Then I flash rom and gapps? Thats it?
Click to expand...
Click to collapse
Format /data and /cache to F2FS. Then wipe /system and /dalvik (yes, clean flash). Make sure you make a nandroid backup first. This will also preserve your current file system type for data and cache for when you restore, if needed.
You might want to wait until my next build is posted to try it. There will be a bunch of things fixed as well as new features.
Help needed. Strange problem
Hey. I really need help here. I have been using SlimLP for quite sometime now. No issues no nothing. I was using the latest rom with the F2FS support. I was using it and suddenly it flashed, vibrated and kept on vibrating. I did not pay much attention. Took the battery out, reinserted it and it worked fine. I was already thinking of trying Paranoid so i had already put the respective rom and gapps in the phone.
So i changed the rom and clean flashed Paranoid. It worked fine for a few days but i started experiencing the same problem again. I use the phone, it flashes, vibrates and then keeps on vibrating. I try pressing power button so it shows samsung logo, starts to boot as i can see the paranoid icon, but breaks in between and the same thing happens. But sometimes its able to boot properly. I use the phone for a while and same thing happens.
I clean flashed this rom again. Same issue. Clean flashed the previous Slim rom. same issue. Restored backup from slim rom. same issue. Restored backup of my stock jellybean. Same issue! Please help!
My phone is currently sitting idle and i am not experiencing any issue. As soon as i use it, after a minute or two i face this problem. Please help.
Help with google
Thank you very much for the hard work and do appreciate it all.
Am coming from a different rom which is also 5.1 and am using latest philz touch recovery. I cleared everything including dalvik cache and
flashed both rom and gapps and the phone boots up successfully. Am actually enjoying the rom but my problem is i can't setup google account on the rom. It force closes during the account setup process.
Re-flashed the rom successfully, as the first time around it did not ask me Language or Google account info and Google Play services kept crashing endlessly. Maybe I just needed to flash it again, or maybe the Gapps package I got didn't agree with my setup (now using Slim_zero_gapps.BETA.5.1.build.0.x-20150820 and it seems to work ok). Thanks for the upload! I have been looking for a good custom rom to run my i727 until I upgrade to a newer phone. The BEST rom I had before was SlimKat Official for Skyrocket, but it's a bit outdated don't you think? It's very nice to see a new interface; really brings a freshness and new appreciation for my old hardware. Thank you.
Also, I am kind of curious about how to view currently opened apps. I used to hold the home button to do this so I could cycle through and kill them if needed.
-Edit- August 26, 2015 2:18 P.M. CST I really love how smooth this rom is at times, but other times it gets laggy and crashes apps after a couple moments for no reason. I did use a custom PIT file to re-partition my i727 so may be other variables as well. Has anyone else had apps crash on them?
no audio through headphone jack
i have done a clean flash and install of the new build of slimlp (nospamdan) having issues with audio coming from headphone jack when jack is removed all sound disappears music wise