This is a direct port of the MIUI build for the Optimus 2x to the T-Mobile G2x. I have ported this myself and will do so every week as long as it meets my standards. Right off I would like to thank whitehawxk for his post on how to port MIUI, it was a huge help!
Features:
*All features of Official MIUI
*Wi-Fi Calling (Yes it works!)
*Zipalign and Permission scrips by Team Kang
*Trinity Kernel by morfic
The Zipalign and Permission scrips zipalign and repair the permissions to /system/app, /system/framework, and /data/app on every boot.
There are two options for this ROM: MIUI ELP and MIUI T15.
*MIUI ELP has the ELPmax Trinity kernel, for best battery life
*MIUI T15 has the T15max Trinity kernel, for most overclock
*For both I sugest having SetCPU to regulate the CPU.
MIUI 2.2.24 ELP and T15 >>Download<<
My ROM is also available through ROM Manager.
Instructions:
*Boot into CWM Recovery
*Do a Factory Reset
*Wipe Dalvik
*Format /system (under mounts and storage)
*Install ROM from sdcard
This ROM is for the G2x (P999) only. Do NOT flash this on an O2x (P990).
Any comments or suggestions just post below or on my Google+ (I check this just as often if not more).
Changelog
Code:
[SIZE=2][COLOR=black]2.2.24
*Fixed Reboot issue
*Improved stability
*Improved performance
*Included newest files and drivers from latest CM Nightly
2.2.3
*MIUI User Feedback Application
*Fixed FC when screen capture
*Included CM Nightly Jan 31
2.1.20
*Included updated files from CM Nightly (v2)
*Added Boot Menu Options back in
*Some stability changes
2.1.13
*Boot Animation Fix (Me)
[/COLOR]*Added support of sending text messages at a set time (feature from 4.0)
*Added support of drop-down notification bar in full-screen mode (feature from 4.0)
*Added support of clearing data in contact setting
*Optimized hangup prompt and animation [/SIZE]
[SIZE=2][COLOR=black] *[URL="http://miuiandroid.com/2012/01/miui-rom-changelog-2-1-13-gingerbread/"]Full MIUI Changelog Here[/URL]
2.1.6[/COLOR]
*Theme Fix (Me)
*Optimization of lockscreen turn-off strategy
*Fix FC due to insufficient memory problems in some cases
*Optimization plug-in model support of online music, data source can easily switch, enhanced stability[/SIZE]
Previous Versions:
All Versions can be found in my SourceForge Folder.
HUGE Thanks to:
Team Kang
morfic
The CM Team
MIUI.us
Reserved For Later
First ;-)
Downloading now will post results..thanks for another rom..keep up the good work
Edit: so far not bad although I have one issue so far and that is after rebooting my phone wifi calling doesn't work, says "invalid sim" now..any clue on how to fix?
Also might want to add that you need the theme folder fix as themes don't/won't install..
Not sure if ill get in trouble but I can always remove the link if needed.. but here's the link for a theme install folder fix, tested and works in this rom..
http://android-maisters.net/roms/index.php/rom-downloads/viewcategory/32-addons
Sent from my LG-P999 using xda premium
Give a try..
....Bloody Phoenix....
htcfresh said:
First ;-)
Downloading now will post results..thanks for another rom..keep up the good work
Edit: so far not bad although I have one issue so far and that is after rebooting my phone wifi calling doesn't work, says "invalid sim" now..any clue on how to fix?
Also might want to add that you need the theme folder fix as themes don't/won't install..
Not sure if ill get in trouble but I can always remove the link if needed.. but here's the link for a theme install folder fix, tested and works in this rom..
http://android-maisters.net/roms/index.php/rom-downloads/viewcategory/32-addons
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
With the Wi-Fi calling, that is something that I get on almost every ROM I have tried. When it says that the SIM is invalid if you look at your APN list it will be empty and that is why it is saying that. Either reboot with Wi-Fi off or do a hard reboot.
As for the theme issue, yes that fix does work but, I am working on fixing it. It is a problem with the kernel. It is not reading the init.d scripts right and that is causing the issue. I will reupload once I get the problem solved. Thanks for the feedback!
OK thanks for the help on wifi calling..didn't know apn gets cleared will try your fix, and great rom..keep up the awesome work and thanks for your work to put another rom on our phones
Update: tried rebooting with wifi off, pulled battery, hard reboot, nothing fixed the "invalid sim" message..and I checked my apn's and there's two "simple" and "Tmobile"..tried everything listed above switching to both apn's but still didn't work..
Sent from my LG-P999 using xda premium
I have patched the theme problem in the current ROM (1.12.30) by integrating the theme folder creation patch into the ROM. I have reuploaded both verions. I am going to keep working on fixing the kernel and I hope to have it done by the next release.
Been running all day. Bad ass battery life and no issues knock on wood so far. Great rom
Sent from my LG-P999 using xda premium
Having problems with the rom. It installs and goes to the load screen where it shows MIUI Android and then it just keeps showing that screen don't go past it. Any advice? I formatted everything twice. before each install. and I also have tried both versions. Both do the same thing.
Did u format system as well? What rom u coming from?
Sent from my LG-P999 using xda premium
sabwjawdjw said:
Having problems with the rom. It installs and goes to the load screen where it shows MIUI Android and then it just keeps showing that screen don't go past it. Any advice? I formatted everything twice. before each install. and I also have tried both versions. Both do the same thing.
Click to expand...
Click to collapse
Maybe you got a bad DL. Try Downloading it again.
Sent from my LG-P999 using XDA Premium App
Same thing here. Getting to MIUI screen and just looping.
Redownloaded 3 times, wiped everything 3 times still doing it. ELP download if that helps.
Just downloaded it on a different machine and tried again, wiped data/cache, system and dalvik still same results.
Yes have downloaded both copies. From numerous different mirrors. Did factory reset twice, wiped dalvik twice, and formatted system twice before installing the second time. Now I have went multiple times with both of these roms tried SEVERAL different things and still nothing but loops on the "MIUI Android" screen.
I am coming from the Weapon rom. So if that tells you anything.
notinterested said:
Same thing here. Getting to MIUI screen and just looping.
Redownloaded 3 times, wiped everything 3 times still doing it. ELP download if that helps.
Just downloaded it on a different machine and tried again, wiped data/cache, system and dalvik still same results.
Click to expand...
Click to collapse
sabwjawdjw said:
Yes have downloaded both copies. From numerous different mirrors. Did factory reset twice, wiped dalvik twice, and formatted system twice before installing the second time. Now I have went multiple times with both of these roms tried SEVERAL different things and still nothing but loops on the "MIUI Android" screen.
I am coming from the Weapon rom. So if that tells you anything.
Click to expand...
Click to collapse
sabwjawdjw said:
Having problems with the rom. It installs and goes to the load screen where it shows MIUI Android and then it just keeps showing that screen don't go past it. Any advice? I formatted everything twice. before each install. and I also have tried both versions. Both do the same thing.
Click to expand...
Click to collapse
I believe your boot problem are from the Trinity Kernel included with the rom...
try waiting a little longer since Trinity takes a while on first boot (the "bootloops" are just the animation replaying since the boot is taking longer that usual) . Or try asking the OP dev for stock miui/cm7 kernel..
Sent from my LG-P999 using Tapatalk
notinterested said:
Same thing here. Getting to MIUI screen and just looping.
Redownloaded 3 times, wiped everything 3 times still doing it. ELP download if that helps.
Just downloaded it on a different machine and tried again, wiped data/cache, system and dalvik still same results.
Click to expand...
Click to collapse
sabwjawdjw said:
Yes have downloaded both copies. From numerous different mirrors. Did factory reset twice, wiped dalvik twice, and formatted system twice before installing the second time. Now I have went multiple times with both of these roms tried SEVERAL different things and still nothing but loops on the "MIUI Android" screen.
I am coming from the Weapon rom. So if that tells you anything.
Click to expand...
Click to collapse
I have reuploaded the ROM. I found an issue in the installer script that may have been causing your boot problem. Try flashing now and see if that works. Sorry for the trouble.
redownloading from Multiupload, filesonic, and fileserve. I will try those 3 if each fail. I will post back if it works this time. Thanks.
---------- Post added at 05:22 AM ---------- Previous post was at 04:51 AM ----------
Installed and loaded like a charm. Great work man. Umm one thing I wanted to ask. Is the themes fixed? I went to the themes folder and tried to switch theme and it just sticks with the original. Any ideas on this?
Oh yea I even rebooted after changing themes still no change. Thanks.
Downloaded the updated one and booted right in. Going to give it a shot, will report back if i run into any issues.
Stormaggedon,
Nice work on the rom!! It's the first MIUI rom where I had Wifi Calling somewhat worked (it worked until I rebooted). I've Tried many MIUI roms for my G2X and they've all had Wifi Calling not work.
Intially after I first installed it yesterday it gave me the "Invalid Sim Card" error. Powered off my phone with "Wifi" turned OFF, removed Sim card and reinserted it powered it back on. As I was turning on Wifi I get that little pop-up message about Wifi Calling and I opened the Wifi Calling App and it said ACTIVE then it connected. I was happy!! I used it to make a few calls and It was perfect.
I thought maybe I can make a BackUp of my phone at it's current state. I powered my phone off and Booted into CWM recovery to make a back up and when I rebooted my phone my Wifi Calling is not working anymore I get the Invalid Sim Card error. I still like the work you did so I'm sticking with it for now and maybe I can fiddle with it to get Wifi Calling working again.
BTW when you hit the Power button and hold it to get the different Reboot options. When I select Recovery it just does a normal Reboot. I had to power off my Phone and manually go into Recovery. Can you look into that. THANKS. Keep up the Good Work!!!
FYI SIM Card Has this number TM9177 on the side with the Gold connector. Hope that helps.
@gfam4 I've had that with about 8 flashes of different miui roms, its not build specific just something that happens.
Sent from my LG-P999 using xda premium
mt3g said:
@gfam4 I've had that with about 8 flashes of different miui roms, its not build specific just something that happens.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
I got a new simcard last week and it's a newer version. I've tried every MIUI rom for our beloved G2X and wifi calling hasn't worked once except for this ROM. And if this Rom is a Port from the O2X like all these other MIUI roms floating around then maybe I got lucky or maybe this newer Simcard (TM9177) works.
I read somewhere that some folks with the older Simcard got Wifi Calling to work on Older Builds of MIUI but the newer cards didn't work. I had one of those newer ones for about 3 months. Until last week I decided to see If can get one of the older Simcards. Since T-mo don't issue them anymore they gave me the newest one available TM9177. I'm gonna try Suilimagic's MIUI build it's older and see if I can get Wifi Calling to work on it.
It's worth a try for anyone to pop in a newer TM9177 simcard and see if it works for them too.
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]
Welcome, everyone- this is the place to ask a question about the CNA Jellybean Rom- Port for our Infuse and more importantly hopefully have that question answered.
You may also discuss issues you are having such as can't download, which g apps do I use, getting a FC on xyz ap, and so on.
A few general Q & A's you may find helpful:
Q: What is CNA ? Any screenshot and more info?
A: Code Name Android info here: http://codenameandroid.com
Q: Where can I download this?
A: Info is in the OP, or you can go here: http://goo.im/devs/Th3Bill/CNA/Infuse
Q: After flashing or using for extended periods my phone seems a bit slow- what to do to make it faster?
A: The test build for this port ( and MIUI v4) was done on my phone since Th3Bill (OP) does not have an Infuse. (Think about that for a minute, no Infuse and to date has brought us 2 roms to enjoy )
Four things I have done that work for me to make the phone faster: 1. Update Superuser ( if applicable.) 2. Choose a static (still) wallpaper rather than a live wallpaper. 3. In developer settings, change animation /transition to "off" or "0". 4.Use the app of your choice to clean up the phone, I use Cachemate.
One other tip for better battery life - this rom will let you download and use CM 10 themes. Using one that has darker backgrounds throughout uses less battery than themes using a lot of light colors.
OK - it's all yours !! I will help as best I can, Th3Bill has a link to this page and will be checking in as often as he can - you will find he is involved and supportive and there will be updates as new things are pushed to source. Regards.
Thanks for the start of the Q&A. Let me be the first then...
I am coming from Scott's CM10, do I just wipe, wipe, wipe and reflash or do I need to Heimdall (maybe with ICS) back first then flash the CNA ROM?
Which GAPPS do you recommend?
psal217050 said:
Thanks for the start of the Q&A. Let me be the first then...
I am coming from Scott's CM10, do I just wipe, wipe, wipe and reflash or do I need to Heimdall (maybe with ICS) back first then flash the CNA ROM?
Which GAPPS do you recommend?
Click to expand...
Click to collapse
You are correct, should be able to wipe x3 and flash - one person also "fixed Permissions" to clear a FC issue.
Edit; I used the 7/26/2012 g apps, you might need to get the gallery2.apk
Here is what I used for gapps. Works just fine. v3
http://www.jokersax.com/developer-pages/jokersax/cm10-gapps/
Wiped/factory reset a couple of times, wipe cache, wipe Dalvik, another factory reset, flashed CNA ROM, flashed jellygapps v3, fixed permissions, rebooted, rebooted again and have an X, then
USB Mass Storage Toggle
App info: http://forum.xda-developers.com/showthread.php?t=1389375.
Usage: Tap on the Droid to switch UMS mode.
Tapped Droid but I cannot connect to this PC (work PC). I have to wait to I get home. Or suggestions are welcomed.
psal217050 said:
Wiped/factory reset a couple of times, wipe cache, wipe Dalvik, another factory reset, flashed CNA ROM, flashed jellygapps v3, fixed permissions, rebooted, rebooted again and have an X, then
USB Mass Storage Toggle
App info: http://forum.xda-developers.com/showthread.php?t=1389375.
Usage: Tap on the Droid to switch UMS mode.
Tapped Droid but I cannot connect to this PC (work PC). I have to wait to I get home. Or suggestions are welcomed.
Click to expand...
Click to collapse
Guessing your work PC does'nt have phone drivers - I have been using that USB Mass Storage Toggle for some time, including on this build.
That's correct. So no big deal, another hour and I will be home and hopefully up and running once I connect there. I will post again with the results.
good Q&A
Pony Express said:
Guessing your work PC does'nt have phone drivers - I have been using that USB Mass Storage Toggle for some time, including on this build.
Click to expand...
Click to collapse
Okay, I am home, USB is connected, tapped the Droid, it says UMS is currently enabled. I downloaded the app from the link...
For the devices listed above, the App works like a charm.
•Latest stable version (1.1.4): Download APK (you'll probably want this one!)
Now what? Reboot and flash it?
psal217050 said:
Okay, I am home, USB is connected, tapped the Droid, it says UMS is currently enabled. I downloaded the app from the link...
For the devices listed above, the App works like a charm.
•Latest stable version (1.1.4): Download APK (you'll probably want this one!)
Now what? Reboot and flash it?
Click to expand...
Click to collapse
Ok.. Bill did not have that included in my test build... he mentioned he was going to add it, sorry for the extra step.
Yes, reboot and flash and let me know how it goes. :fingers-crossed:
Pony Express said:
Guessing your work PC does'nt have phone drivers - I have been using that USB Mass Storage Toggle for some time, including on this build.
Click to expand...
Click to collapse
Pony Express said:
Ok.. Bill did not have that included in my test build... he mentioned he was going to add it, sorry for the extra step.
Yes, reboot and flash and let me know how it goes. :fingers-crossed:
Click to expand...
Click to collapse
Also tried it with the other file found on the thread (USB mass storage)...neither work.
Finding Update package...
Opening update package...
Installing update...
Installation aborted.
The pix of Droid laying down, check open and a red triangle with exclamation in it showing up.
Log says:
Installation aborted.
I:Can't partition unsafe device: /dev/block/mmcblk0p1
I:Can't format unknow volume: /external_sd
I:Can't partition unsafe device: /dev/block/mmcblk1p1
I suppose the best route would be to start over. There should be no problem coming from Scott's excellent build.
Having said that, try installing a CM9 rom, let it settle in for 5 -10 minutes and reboot, wipes, flash and see if it will boot. Go back later and get the g apps. This is what worked for me. I can tell you that during the install, phone will cut off before making it back to the "reboot system now" screen, however it will restart and take you there so just hit power button to reboot. This rom does take 2-3 times as long to boot for the first time as opposed to other roms.
I'm not so sure you want to flash since they are .apk's
Sent from my SGH-I997 using xda app-developers app
---------- Post added at 04:45 PM ---------- Previous post was at 04:44 PM ----------
Woops, I misunderstood the problem.
Sent from my SGH-I997 using xda app-developers app
Pony Express said:
I suppose the best route would be to start over. There should be no problem coming from Scott's excellent build.
Having said that, try installing a CM9 rom, let it settle in for 5 -10 minutes and reboot, wipes, flash and see if it will boot. Go back later and get the g apps. This is what worked for me. I can tell you that during the install, phone will cut off before making it back to the "reboot system now" screen, however it will restart and take you there so just hit power button to reboot. This rom does take 2-3 times as long to boot for the first time as opposed to other roms.
Click to expand...
Click to collapse
SD card in or out?
Pony Express said:
Ok.. Bill did not have that included in my test build... he mentioned he was going to add it, sorry for the extra step.
Yes, reboot and flash and let me know how it goes. :fingers-crossed:
Click to expand...
Click to collapse
Bill did include the USB Mass Storage Toggle in the build. It should be there when you flash the rom. It was there when I flashed and it works. No additional d/l's were necessary.
Also, I didn't have any of the restarts you mentioned. I had a black screen for about 30 seconds when it went to the new CWM and then a black screen for about 30 more seconds when it rebooted to the Nexus X.
I did think I had problems because it stayed on the Nexus X screen for about 5 minutes before it booted up to the lock screen.
Edit: Also it booted itself to the Nexus 7 screen without asking after installing the rom package. Had to go back in and add the gapps.
psal217050 said:
SD card in or out?
Click to expand...
Click to collapse
I always leave my SD card in... no problems for me so far.
dparrothead1 said:
Bill did include the USB Mass Storage Toggle in the build. It should be there when you flash the rom. It was there when I flashed and it works. No additional d/l's were necessary.
Also, I didn't have any of the restarts you mentioned. I had a black screen for about 30 seconds when it went to the new CWM and then a black screen for about 30 more seconds when it rebooted to the Nexus X.
I did think I had problems because it stayed on the Nexus X screen for about 5 minutes before it booted up to the lock screen.
Click to expand...
Click to collapse
Thanks, man. That is exactly the way the install should go.
Pony Express said:
I always leave my SD card in... no problems for me so far.
Click to expand...
Click to collapse
+1 for leaving the SD card in....never take mine out when flashing.
is 720 recording fixed, or is it still recording a bit choppy?
SMiGGs said:
is 720 recording fixed, or is it still recording a bit choppy?
Click to expand...
Click to collapse
It is still a little choppy.
Have fun, and format /system before flashing!
added camera app, fm radio, media_codecs.xml (fixes sound probs)
http://www.mediafire.com/file/rm3t3813wwxaewd/cm-10-20120826-UNOFFICIAL-sholes.zip
bootloops? ts problems?
did you format system?
try safe kernel (stockish ram/sgx/dsp timings)
http://www.mediafire.com/file/0kci9mvja4b9ssn/jb_safe_kernel.zip
or safer kernel (doesn't reprogram core clock at boot, exact stock timings)
http://www.mediafire.com/?do6yfe1c79v7xj7
or safest (same as safer with cpu max at 800mhz instead of 1000)
http://www.mediafire.com/file/926lgj8qu2a8l8s/jb_safest_kernel.zip
still no go?
try ics build here:
http://forum.xda-developers.com/showpost.php?p=29471613&postcount=1855
with 160mhz kernel
then wipe everything and try this build again, or enjoy ics :]
if you get stuck without touchscreen don't sbf back to stock
try safe kernel and ics build, if you still have troubles pm me
Gapps: http://www.mediafire.com/file/6gm3mm7iyi775n6/gapps-jb-20120726-minimal-datainstall.zip
broken: lots? please test
greets and credit: nadlabak, quarx2k, tpruvot, mbm, everybody at #motomagic, et cetera
kfazz said:
Have fun!
Build: http://www.mediafire.com/file/elk7kvw2hyu28ij/cm-10-20120824-UNOFFICIAL-sholes.zip
Gapps: none yet
broken: lots? please test
greets and credit: nadlabak, quarx2k, tpruvot, mbm, everybody at #motomagic, et cetera
Click to expand...
Click to collapse
Downloading
since this is CM10 based would regular cm10 gapps work? Thanks
Edit: It doesn't seem to boot. It gets stuck on the android screen.
about 3m freee in system, so regular jb gapps wont work unless modified to use /data. ics gapps work.
if you have bootloop:
adb shelll and
rm /system/lib/hw/gps.sholes.so
or just delete it from the zip before flashing
kfazz said:
about 3m freee in system, so regular jb gapps wont work unless modified to use /data. ics gapps work.
if you have bootloop:
adb shelll and
rm /system/lib/hw/gps.sholes.so
or just delete it from the zip before flashing
Click to expand...
Click to collapse
Installd ics gapps.
So, got rid of bootloop using adb to remove gps. Boots up fine after that.
CPU overclock settings can not be changed in settings. Works fine in setcpu.
No camera app included.
EDIT: Phone was plugged into usb port on computer entire time, and I noticed that the battery was not charging. Flashed back to my daily driver for now and phone is charging again. Not sure if this is common to anyone else or just a bug for me.
this is filthy! so fast. i used http://forum.xda-developers.com/showpost.php?p=30325746&postcount=1977 nightwing's .zip to get market over adb. wireless also works. mp3's through music load up like it's going to play, but then flashes a screen where song progress is complete and goes back to the artist list, but media server found all my songs. m4a's say file not supported. bluetooth paired with my keyboard and worked. voice dialer worked to open apps and i got a few beeps out of it at the end of commands so some sound is working. mine's not activated though so i can't test radios. donations on the way. thanks for all the hard work.
peeyourownpants said:
this is filthy! so fast. i used http://forum.xda-developers.com/showpost.php?p=30325746&postcount=1977 nightwing's .zip to get market over adb. wireless also works. mp3's through music load up like it's going to play, but then flashes a screen where song progress is complete and goes back to the artist list, but media server found all my songs. m4a's say file not supported. bluetooth paired with my keyboard and worked. voice dialer worked to open apps and i got a few beeps out of it at the end of commands so some sound is working. mine's not activated though so i can't test radios. donations on the way. thanks for all the hard work.
Click to expand...
Click to collapse
I can confirm 3G and calling works.
also, is there a way to get google now on this?
db2u said:
Installd ics gapps.
So, got rid of bootloop using adb to remove gps. Boots up fine after that.
CPU overclock settings can not be changed in settings. Works fine in setcpu.
No camera app included.
EDIT: Phone was plugged into usb port on computer entire time, and I noticed that the battery was not charging. Flashed back to my daily driver for now and phone is charging again. Not sure if this is common to anyone else or just a bug for me.
Click to expand...
Click to collapse
Might flash back to test some more once my battery gets up to a decent level
Can't get it to boot, using CWR 3 from Rom Manager
jyeley5 said:
Can't get it to boot, using CWR 3 from Rom Manager
Click to expand...
Click to collapse
Originally Posted by kfazz
if you have bootloop:
adb shelll and
rm /system/lib/hw/gps.sholes.so
jyeley5 said:
Can't get it to boot, using CWR 3 from Rom Manager
Click to expand...
Click to collapse
db2u said:
Originally Posted by kfazz
if you have bootloop:
adb shelll and
rm /system/lib/hw/gps.sholes.so
Click to expand...
Click to collapse
I have 3 loops at the "M" screen each time before it moves on to the android screen and finishes the boot even with gps.sholes.so removed
Sent from my Galaxy Nexus using Tapatalk 2
Finally got it booting, thanks for the help!
kfazz: Awesome work!!! What's the current status of FM radio though? I tried the FMRadio.apk from the Defy and it FC'd as soon as I plugged in my headphones
peeyourownpants said:
I have 3 loops at the "M" screen each time before it moves on to the android screen and finishes the boot even with gps.sholes.so removed
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I used to get that on CM7.1 I think it was a bad flash, It went away when I flashes Steeldroid, and I am definitely not getting it on this build
mediafire virus
After using link at top of page to download from media fire using Windows explorer I got a message saying virus detected on my computer and the page looks exactly like Microsoft security essentials I clicked no and computer crashed!!! This makes 2 times I have gotten virus from media fire last time I was able to restore to an earlier backup this time computer wouldn't let me boot into recovery or anything after much trouble I got it to boot into safe mode only because I have recovery disks that came with PC but have not been able to repair it complelty yet because if I try to restore it ends with an error about system contains some file ( idont remember name) so if I can't figure it out I guess I will backup important files and do a complete restore from factory disks ( last resort ) . Just a warning . If anybody has any answers and or ways to prevent this please PM me. Hopefully this won't happen to anyone else
Sorry for highjacking thread I know this is off subject but don't want anyone else to become a victim!!
Link worked fine when downloaded from phone but I have no way to modify zip or use adb to make JB boot
Sorry to kfazz for this post I know its not his fault I found many people with same problem with a Google search
Keep up the great work kfazz you are the best!!
peeyourownpants said:
I have 3 loops at the "M" screen each time before it moves on to the android screen and finishes the boot even with gps.sholes.so removed
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Similar problems, but mine's randomly deciding to boot up or not. Sometimes it doesn't boot at all, other times it boots on the first try.
However since the Camera, Wifi, and other Jelly Bean goodness works, I can't help but to thank you on this release, Good luck on further development!
EDIT: And now it won't even boot, sometimes it just gets stuck at a blank screen. Bummer.
denwaotoko said:
Similar problems, but mine's randomly deciding to boot up or not. Sometimes it doesn't boot at all, other times it boots on the first try.
However since the Camera, Wifi, and other Jelly Bean goodness works, I can't help but to thank you on this release, Good luck on further development!
Click to expand...
Click to collapse
i cant get the new build to boot i removed the gps.sholes file and im just bootlooping at m logo
wolf45801 said:
i cant get the new build to boot i removed the gps.sholes file and im just bootlooping at m logo
Click to expand...
Click to collapse
Which one, the one with fm radio and camera? I was able to get the first build to boot fine after removing gps.sholes
ASAM123 said:
Which one, the one with fm radio and camera? I was able to get the first build to boot fine after removing gps.sholes
Click to expand...
Click to collapse
i couldn't get the newest to boot either, just loops at the M.
i poked into the .zip and the gps file is gps.goldfish.so, not sure if that's relevant...
ASAM123 said:
Which one, the one with fm radio and camera? I was able to get the first build to boot fine after removing gps.sholes
Click to expand...
Click to collapse
i finally got it working i downloaded the new one but for some reason mediafire didnt download the full rom so had to redownload
I can't get it to boot up. I end up with red M bootloops with both the 8/24 and 8/26 builds. I wiped everything between flashes. Any ideas?
Flashed over 7/12 ics build seems as good as ics was don't think I will be going back to ics. Gallery opens but never shows any pics fm radio is nice only plays in mono other than that everything else I have tested is working correctly great work as usual
Thanks to all who are making this possible
Sent from my Droid using xda app-developers app
Hey, so as stated in the title, I have recently flashed Cyanogenmod7. Initially, version 7.2.0 and then the nightly build released on 10/7/12. I can no longer receive mobile data. I realize this is a very common problem and have searched through multiple forum posts here and elsewhere online. I also flashed a new kernel in an attempt to fix it (not sure of the name, found here: http://forum.xda-developers.com/showthread.php?t=1073626).
Mobile data will appear (and work) for the first 10-15 seconds after startup if wifi is disabled but then vanishes afterwards. I have tried changing the mobile network settings and apn settings in a number of ways but no method ever works (most of the ones found online appear to be at least a year old so perhaps I just need more modern entries). Any help would be greatly appreciated.
viveksmother said:
Hey, so as stated in the title, I have recently flashed Cyanogenmod7. Initially, version 7.2.0 and then the nightly build released on 10/7/12. I can no longer receive mobile data. I realize this is a very common problem and have searched through multiple forum posts here and elsewhere online. I also flashed a new kernel in an attempt to fix it (not sure of the name, found here: http://forum.xda-developers.com/showthread.php?t=1073626).
Mobile data will appear (and work) for the first 10-15 seconds after startup if wifi is disabled but then vanishes afterwards. I have tried changing the mobile network settings and apn settings in a number of ways but no method ever works (most of the ones found online appear to be at least a year old so perhaps I just need more modern entries). Any help would be greatly appreciated.
Click to expand...
Click to collapse
The CM team has yet to fix this, and I doubt it ever will be fixed. It's present on all AOSP based ROMS. I guess if they set the modem to reset on bootup, it could fix it, but I have no idea how to do that.
FatalityBoyZahy said:
The CM team has yet to fix this, and I doubt it ever will be fixed. It's present on all AOSP based ROMS. I guess if they set the modem to reset on bootup, it could fix it, but I have no idea how to do that.
Click to expand...
Click to collapse
So, to get my data back should I just reflash stock?
Have you tried hard resets? Holding power and volume up until the phone reboots?
buru898 said:
Have you tried hard resets? Holding power and volume up until the phone reboots?
Click to expand...
Click to collapse
Yeah, I've tried that. Still nothing.
I am using cm7 no problem with data whatsoever you shoud try wiping cache and dalvik cache and after that fix permissions and if u wanna install a custom kernel thats what i do when i flash a rom and works fine
Sent from my LG-P999 using xda app-developers app
ted619 said:
I am using cm7 no problem with data whatsoever you shoud try wiping cache and dalvik cache and after that fix permissions and if u wanna install a custom kernel thats what i do when i flash a rom and works fine
Sent from my LG-P999 using xda app-developers app
Click to expand...
Click to collapse
I've also tried wiping the cache and dalvik cache with no effect. I have also installed a custom kernel with no effect. I am not entirely sure what you mean by fixing permissions.
Edit: searched and figured it out. Tried fixing permissions in combination with the other two options. Still no effect.
Sorry to bump an old topic but I accidentally reflashed Cyanogen (pressed wrong zip in recovery) and now it's working so if anyone else has this problem, try doing a factory reset and then reflashing old data.
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.)