Related
Hello people,
I was looking through the nightly builds on download.cyanogenmod.com
I saw a fresh build for TF101 dated for 2/27.
Check it out. I will flash it and see how it is.
Someone also needs to create an Official CM9 Nightly page in Dev section.
So who wants to be the Guinea pig? I'm already running that KANG that was posted up earlier this weekend. I may try it after I charge up.
yea...guinea pig here....goes through boot animation and then system ui and trebuchet (the launcher) fc...i would say stay away until some official announcement is made
Yeah. It doesn't even boot up probably. :-(... going back to stock
Sent from my Galaxy Nexus using XDA App
You have to start somewhere.
Now at least we have an official CM9 branch, which means someone is working on it
brzgw said:
Hello people,
I was looking through the nightly builds on download.cyanogenmod.com
I saw a fresh build for TF101 dated for 2/27.
Check it out. I will flash it and see how it is.
Someone also needs to create an Official CM9 Nightly page in Dev section.
Click to expand...
Click to collapse
ehm where from?
Edit: http://download.cyanogenmod.com/?device=tf101
Found IT ^_^
I got launcher force closes when i had an overclocked kernel with a stock rom. Gonna check this out a little later.
Sent from my Transformer TF101 using Tapatalk
I'm surprised that this news seems to be not generating much buzz here. Not knocking any of the other devs, because most of them do amazing work, but CM is the bee's knees. When those nightlies get semi-mature, I'll be running them and never look back. They've never done me wrong before. Any device I've ever had that was supported, was the best ROM available for my needs. YMMV, of course.
I think when its own thread is created youll see the buzz, cm rocks lol
Sent from my R800i using xda premium
I tried flashing it and got the same fc, the system ui and launcher. I tried it again but formatted system this time. Got the same results but was able to see the clock and tablet reboot options.
Guess it's not ready yet
shadrach47 said:
I tried flashing it and got the same fc, the system ui and launcher. I tried it again but formatted system this time. Got the same results but was able to see the clock and tablet reboot options.
Guess it's not ready yet
Click to expand...
Click to collapse
Yep, same here, even with wipe dalvik and fix permissions, FC´s :S
Let us wait for a new update....
Alas, I ran across this on get.cm also. Got excited and then had the FC issues like everyone else. At least it is a step in the right direction.
Don´t know if its related,
lost my wifi hability after trying this, anyone else?
it just won´t turn on :S
Was just about to try flashing it until I saw how many people were unsuccessful. Oh well, guess I'll wait until an official release.
ferreinf said:
Don´t know if its related,
lost my wifi hability after trying this, anyone else?
it just won´t turn on :S
Click to expand...
Click to collapse
Not sure if it's related or not but my wifi on a Kanged version of CM9 is acting weird, disconnecting and saying out of range.
I tried this one first but it could just be the ROM I'm on.
shadrach47 said:
Not sure if it's related or not but my wifi on a Kanged version of CM9 is acting weird, disconnecting and saying out of range.
I tried this one first but it could just be the ROM I'm on.
Click to expand...
Click to collapse
Ok got it to work again, had to use Super Wipe Lite from http://forum.xda-developers.com/showthread.php?t=1245892
after running the script flashed latest revolver and got wifi backup....
Same here, will try your suggestion below.
Edit: Had to run the wipe zip, reflash and boot into current rom and the restore a backup to get it working again. PITA But it works.
ferreinf said:
Don´t know if its related,
lost my wifi hability after trying this, anyone else?
it just won´t turn on :S
Click to expand...
Click to collapse
CM rocks
lollazzo said:
CM rocks
Click to expand...
Click to collapse
i would like to see MIUI V4 on tab, as it will be easier to port than 2.x was ^_^
New official CM9 nightly on get.cm. It boots!!! Gonna test it and report back in a bit.
EDIT1: Wifi works and was able to log into my Google account. Currently restoring my Titanium Backup and will test a bit more after that. Also, camera makes the tablet reboot on first launch, but works after that. Odd. More info to come.
EDIT2: Face unlock is there, but doesn't recognize my face, so I can't test it out. It couldn't recognize my face on my Nexus S 4G either. Maybe my face is just derped up. Anyway, there is nothing that I could tell that is broken. Even the MicroSD mounted with no issue. I don't have a keyboard dock to test it out, otherwise I would. Games and videos both work fine.
Okay!
Could I just get some sort of final solution, not only me, but the many others on xda that are suffering from the same problem as me. Why am I not getting notifications!? I've tried almost every kernel on here, from Franco to Air kernel and no luck! I've tried using the PNF app, no luck there! Is there just one solution!?
I restored a nandroid from when I fresh rooted my nexus. Is this a kernel issue or a ROM issue ?
Sent from my Nexus 4 using Tapatalk 4 Beta
This is an issue Google needs to fix in the upcoming android release. I believe someone in the android development forum section is trying to fix it so you could try to find and visit the thread if you need more info or can provide help...
Sent from my Nexus 4
+1
I've got to unlock my phone for the notifications to show up. Defeats the purpose of having push notifications
Sent from my Nexus⁴ running CM10.1
Have you tried any of those fixes
http://forum.xda-developers.com/showthread.php?t=2272140
http://forum.xda-developers.com/showthread.php?t=2300873
http://forum.xda-developers.com/showthread.php?t=2072930
http://forum.xda-developers.com/showthread.php?t=2102986
It may work for you, just make sure and be careful to choose which one. I myself haven't tried any of them (keeping stock for sometime)
I've been using a +motley kernel found on his thread that someone modified with newer prima drivers. It has worked fine for me for months now.
Hi everyone.
First of all, i apologize if there's an answer out there i'm looking but i cant find it anywhere of the hundreds of threads containing thousands of posts.
I bought a cracked Nexus 4 on ebay and i already fixed the screen by replacing a new one and everything is working now.
The phone was already rooted with Mako's Android L beta4 i believe and to be honest i didnt really liked it.
I know it is on its early stages and the official one from google is still far from the next month of its release and im in no rush to get it and experience until it gets more stabilized so i would rather use Cyanogenmod 11.
So i did a full wipe/factory reset, wipe partition cache, wipe dalvik cache and installed with a nightly CM 11 from 20140907.
Everything works perfectly and cant find anything thats causing problems except one thing.
When i make a phone call, the screen turns off as if i pressed the lock screen button which i didn't but the call is still ongoing and i have to press to unlock button to turn on the screen and unlock, and when i'm on the call at the dialer i cant hang up by pressing the red hang up button, neither pressing the numbers or anything. Nothing works, the dialer is frozed and the only way i can hang it up is by going on the home screen and going to notifications and hang it up from there.
I never encountered this problem before on cyanogenmod and i believe its not from it but from the installation of makos android L b4 itself from its kernel that its not allowing me to make the phone calls. That's just my opinion. Anyone has any idea of whats causing the problem?
Is there a solution? Do i have to do a fresh clean install from the beginning maybe like to stock and from there to cyanogenmod?
Please help me out guys, im loving the Nexus 4, came from the Galaxy S2 i9100M and i had no problem rooting it at all and its still with CM 11.
Thank you all for taking the time to read this, and any ideas are welcome.
ilum90 said:
Hi everyone.
First of all, i apologize if there's an answer out there i'm looking but i cant find it anywhere of the hundreds of threads containing thousands of posts.
I bought a cracked Nexus 4 on ebay and i already fixed the screen by replacing a new one and everything is working now.
The phone was already rooted with Mako's Android L beta4 i believe and to be honest i didnt really liked it.
I know it is on its early stages and the official one from google is still far from the next month of its release and im in no rush to get it and experience until it gets more stabilized so i would rather use Cyanogenmod 11.
So i did a full wipe/factory reset, wipe partition cache, wipe dalvik cache and installed with a nightly CM 11 from 20140907.
Everything works perfectly and cant find anything thats causing problems except one thing.
When i make a phone call, the screen turns off as if i pressed the lock screen button which i didn't but the call is still ongoing and i have to press to unlock button to turn on the screen and unlock, and when i'm on the call at the dialer i cant hang up by pressing the red hang up button, neither pressing the numbers or anything. Nothing works, the dialer is frozed and the only way i can hang it up is by going on the home screen and going to notifications and hang it up from there.
I never encountered this problem before on cyanogenmod and i believe its not from it but from the installation of makos android L b4 itself from its kernel that its not allowing me to make the phone calls. That's just my opinion. Anyone has any idea of whats causing the problem?
Is there a solution? Do i have to do a fresh clean install from the beginning maybe like to stock and from there to cyanogenmod?
Please help me out guys, im loving the Nexus 4, came from the Galaxy S2 i9100M and i had no problem rooting it at all and its still with CM 11.
Thank you all for taking the time to read this, and any ideas are welcome.
Click to expand...
Click to collapse
Try flashing other roms... Stock I would recommend and then test for that issue if not good or else then flash AOSP romwith good custom kernel(ak , hellscore)
Rohit02 said:
Try flashing other roms... Stock I would recommend and then test for that issue if not good or else then flash AOSP romwith good custom kernel(ak , hellscore)
Click to expand...
Click to collapse
Is it possible to use hellscore kernel wit CM rom?
Sorry for the noobish questions but i havent mastered when it comes to rooting and all.
I never installed any rom besides CM.
ilum90 said:
Is it possible to use hellscore kernel wit CM rom?
Sorry for the noobish questions but i havent mastered when it comes to rooting and all.
I never installed any rom besides CM.
Click to expand...
Click to collapse
yes hellscore has cm version too..
I would recommend you to flash aosp rom -any.
Rohit02 said:
yes hellscore has cm version too..
I would recommend you to flash aosp rom -any.
Click to expand...
Click to collapse
At first, i installed another rom like paranoid 4.45 20140729 and it didnt work, it got worse.
When i would make a call, the screen would turn off and couldnt get to back on and it does but not even for a sec so it kept remaining wit a screen off but the call was still going.
The next step i tried AOSP build 12 rom, with same kernel and it also didnt work. Same as before when i had CM 11.
I just installed CM 11 rom with hellscore b55 CM anykernel and it does the same thing.
My only next step based on your opinion is trying AOSP rom with hellscore kernel (not the CM version).
Is there anything else i can try if the aosp wit hellscore kernel doesnt work?
could you indicate me where to get the stock kit kat because i see versions of them and im not sure if their stock or not.
is it also possible to use stock with hellscore kernel?
Much appreciate for all the help you have given me so far.
Same problem with simple AOSP with hellscore b55 anykernel.
Any other ideas?
try this fix :
http://forum.xda-developers.com/nexus-4/help/proximity-sensor-fix-screen-replacement-t2657176
RolF2 said:
try this fix :
http://forum.xda-developers.com/nexus-4/help/proximity-sensor-fix-screen-replacement-t2657176
Click to expand...
Click to collapse
I can't believe it! After all this time, blaming on the software so hard and for the last resort I actually did dissembled my N4 to check the sensors and everything but did nothing. But dude, you solved the mystery! Everything is working perfectly now. I can't appreciate how thankful I am. Many thanks
[Q&A] [L5][E610/E612/E617][ROM][KTU84P][4.4.4][BETA 9.5] Unofficial CyanogenMod 11 B
Q&A for [L5][E610/E612/E617][ROM][KTU84P][4.4.4][BETA 9.5] Unofficial CyanogenMod 11 Build
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 [L5][E610/E612/E617][ROM][KTU84P][4.4.4][BETA 9.5] Unofficial CyanogenMod 11 Build. 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!
bluetooth
bluetooth streaming doesn't work
Disable LPA.
Mount system as read/write
Edit /system/etc/init.lge.target.sh
Search for lpa and set it to false. Reboot
OC Kernel
Sorry for bad english.
What is the best oc kernel for beta 9.5? possibly without battery drain
Thank you
Fix 3d bug ?
Android L on LG-E610
Thanks for your work. I use this for 1 year. Will you work android l on lg e610
sorry for my bad english
raul338 said:
Disable LPA.
Mount system as read/write
Edit /system/etc/init.lge.target.sh
Search for lpa and set it to false. Reboot
Click to expand...
Click to collapse
i changed tis but before this i removed bluetooth.apk of /system/app/ and puted another bluetooth.apk reboot and later bluetooth doesn't turn on. i tried to put the original apk but it doesn't works
sorry for my bad english xD
I dont know what to tell you. Try reflash the rom
LGE612(f), CWM v6.0.5.0
Been using for three days now, works awesome on SKernel (RC3) and no battery drain issues so far ( I've only charged it twice in three days and it's still on 70%). My usage is mediocre, surfing videos on YouTube, using Whatsapp, less calling/sms, etc. Overall the rom is smooth (61-900mhz, smartassV2, noop) no problems yet. Though I don't know if this is a bug or app issue, when I try to change my profile pic on Whatsapp the image turns into super low quality one(blurred/pixelated) and I noticed that this is also happening on stock rom. It was not happening until a week ago or so, any suggestions?
Problems with games
PecanCM In 3d games look so to speak where the reflection should go or things just black shadows as pictures , as I fix or kernel should I use ?[/I][/I]
Contacts in SIM
Is there any way to fix the problem with the SIM? Cause when I try to export from SIM to phone it says that's there is no contacts in the SIM
Thanks
Hi
Let me ask , its that working on LG 615f or not ? thanks
raul338 said:
I dont know what to tell you. Try reflash the rom
Click to expand...
Click to collapse
I reflashed the ROM again but the problem persists
Anyone experiencing trouble with the wifi connection? I've got 2 e610's here running this rom and the wifi gets very unstable and slow.
Changed from isp today so it isn't the router.
nico445 said:
Anyone experiencing trouble with the wifi connection? I've got 2 e610's here running this rom and the wifi gets very unstable and slow.
Changed from isp today so it isn't the router.
Click to expand...
Click to collapse
Change mac address in /system/etc/firmware/wlan/volans/ WCN1314_qcom_cfg.ini
But first Mount system as rw then edit the file and reboot
Cm has a preloaded wifi mac address and its not rigth that both devices has the same address
Enviado desde mi LG-E610 mediante Tapatalk
Broken Caller ID - Rogers
With the latest update, I loose my ability of Caller ID. it said unknown number when receiving income calls. The last versions worked perfect.
P.S Rogers is my cell provider.
-Y.G.
Radio and quickmemo
I need the radio from the stock rom but i cant install it.. also the quickmemo would be nice. Do you guys know how to recover this apps in this rom?
eduardov said:
I need the radio from the stock rom but i cant install it.. also the quickmemo would be nice. Do you guys know how to recover this apps in this rom?
Click to expand...
Click to collapse
No FM radio in CM, just deal with it, or go back to stock I don't remember quickmemo app, but I think apk can be pulled out from backup and installed on CM. If you really need this, I can try to look for this, because I've got cwm backup of stock rom.
Running latest CM11 beta 9.5 in my E610 and I'm experiencing strange freezes from time to time. Screen goes white and phone locks up, when booting the touchscreen doesn't work anymore.
Restoring system from a backup makes everything work again. What logs (and where are they) might help to figure out what's causing these lockups?
Cheers
Webster666 said:
No FM radio in CM, just deal with it, or go back to stock I don't remember quickmemo app, but I think apk can be pulled out from backup and installed on CM. If you really need this, I can try to look for this, because I've got cwm backup of stock rom.
Click to expand...
Click to collapse
nothing to do with the ***king radio?? ok either way.... It would be great have the quickmemo for the cm11 :fingers-crossed::fingers-crossed:
Hopefully this is the correct forum, if not please let me know.
I have tried a couple custom stock XT1575 ROMs. Everything installs great except when my phone is called, the dialer
won't open. I hear my phone ring or vibrate depending on what it is using, just nothing comes up to allow me to answer
it. The latest custom stock ROM I installed today is moto_x_pure_edition_custom_stock_x1575_mphs24.107-58-1_v1-odexed.
Has this happened to anyone else, is it a known problem with the custom stock ROMs? Any help is appreciated. I can't
use the phone so it's just sitting in a corner.
Have you tried puretrue rom . I have flashed 3 roms 2 custom stock Rom and one nexus rom.But never faced this issue . Maybe clean install will help you.
azzammalik said:
Have you tried puretrue rom . I have flashed 3 roms 2 custom stock Rom and one nexus rom.But never faced this issue . Maybe clean install will help you.
Click to expand...
Click to collapse
Every time I've installed the ROM, everything was wiped first, including the install I did earlier today.
I've tried a few other ROMs from here, didn't quite like them (not sure if the one you mentioned is one I tried) so wanted to use the custom default Motorola ROM which I liked. They are rooted and have super user. If you know the link to that ROM you mentioned, I don't mind looking into it. Thanks
Go to Settings > Apps > Gear icon > Default Apps > Select 'Telephone' for Phone
Can't believe this is still a thing! This is an old *ss small issue which has been discussed over and over again!
Now with this Help thread open I hope people will learn!
ban.codrut said:
Can't believe this is still a thing! This is an old *ss small issue which has been discussed over and over again!
Now with this Help thread open I hope people will learn!
Click to expand...
Click to collapse
Yes, I understand it's been around a while. I've searched for answers and all the suggestions have not made a difference for me. I have also searched a little on here using different terms but could not find anything either. If you know the answer, can you assist? I understand you may have seen this a few times but not everyone has, like me. I just want to know the fix, is that so bad?
davidrocher said:
Go to Settings > Apps > Gear icon > Default Apps > Select 'Telephone' for Phone
Click to expand...
Click to collapse
I've already attempted that, didn't help. Tried a new dialer app, didn't make a difference either. Made sure it was the default and that notifications were on for the app also. Thanks
michont said:
Yes, I understand it's been around a while. I've searched for answers and all the suggestions have not made a difference for me. I have also searched a little on here using different terms but could not find anything either. If you know the answer, can you assist? I understand you may have seen this a few times but not everyone has, like me. I just want to know the fix, is that so bad?
Click to expand...
Click to collapse
Your described issue seems just the usual "no default phone app selected" , which solution is to just set one. If something else is going on I can't help, I've never encountered other root issues to this (not by experience not by reading). Sorry!
But we could go through this and try troubleshooting.
You are using a custom stock so probably already got root permission.
1) Install logcat or matlog
2) start recording and call your phone right away using a second phone while leaving the screen on
(try upping the screen time to 5 minutes let's say, this way there is no loginfo we are not interested in there beside the call intent)
3) After that, hangup and stop recording the log then share a link to the file here (file ! Don't paste in pls)
Let's hope there is a debug warning or error which will tell us what's actually going on!
On the other side of thing, you do have a XT1575 right ? Or you are using XT1575 Ron on XT1572 ? Not a biggie but quit relevant for modem file!
In the morning I'll give it a look, now I'm heading to bed (2AM here)
michont said:
Every time I've installed the ROM, everything was wiped first, including the install I did earlier today.
I've tried a few other ROMs from here, didn't quite like them (not sure if the one you mentioned is one I tried) so wanted to use the custom default Motorola ROM which I liked. They are rooted and have super user. If you know the link to that ROM you mentioned, I don't mind looking into it. Thanks
Click to expand...
Click to collapse
Hope you have already solved this problem. But if you are still facing same issue then this is perfect rom if you want to stay close to stock.
https://forum.xda-developers.com/moto-x-style/development/rom-trupurex-fast-smooth-t3237155
ban.codrut said:
Your described issue seems just the usual "no default phone app selected" , which solution is to just set one. If something else is going on I can't help, I've never encountered other root issues to this (not by experience not by reading). Sorry!
But we could go through this and try troubleshooting.
You are using a custom stock so probably already got root permission.
1) Install logcat or matlog
2) start recording and call your phone right away using a second phone while leaving the screen on
(try upping the screen time to 5 minutes let's say, this way there is no loginfo we are not interested in there beside the call intent)
3) After that, hangup and stop recording the log then share a link to the file here (file ! Don't paste in pls)
Let's hope there is a debug warning or error which will tell us what's actually going on!
On the other side of thing, you do have a XT1575 right ? Or you are using XT1575 Ron on XT1572 ? Not a biggie but quit relevant for modem file!
In the morning I'll give it a look, now I'm heading to bed (2AM here)
Click to expand...
Click to collapse
Thanks, just got home from work myself. I am using the XT1575. The default phone app is chosen. I'll see what I can
do about the logging suggestions you mentioned. I may not get to that today as I have a few things to do before
heading into work.
azzammalik said:
Hope you have already solved this problem. But if you are still facing same issue then this is perfect rom if you want to stay close to stock.
https://forum.xda-developers.com/moto-x-style/development/rom-trupurex-fast-smooth-t3237155
Click to expand...
Click to collapse
Thank you, I'll download now.
Thanks for the assist all of you. I decided to install the TruPureXMM-2.9 ROM and so far I'm liking it. It has a few quirks but the dialer works
from the get go which is the main thing. Those ROMs from the other Moto style installs must have something inherently wrong designed
in them not to work right from the start.