Database Users

gen2 and reflash to cyanogenmod 7,0 ??

so, ive did the upgrade to gen2, and installed 7.0.3 cyanogenmod..
BUT the resets when i charge it, is annoying and i belive that wasnt an issue at 7.0.0? or was it??
can i reflash it back to the 7.0 now? or what about the 7.0.2? is that any better??
also- my phone is gettin slow... i really dont know why..
got like 4 giga available space at sd, and all apps are moved to sd..

Use the latest nightly (N100) and full wipe and flash.
The bug is fixed in later releases after stable.

oki. i will dl and flash it now..
is there gonna be a new cyanogenmod stable flash soon?
ps- many thanks!!
also--- what IS nightly builds anyway?
are they all different or are they finished roms?, but lets say 99 has the reset error and the 100 is the one that fixes it..
is the 87 or whatever build pre100 not as good as the latest 100 in today case?

Not that I know of.
They're usually experimental, but for the Blade they're probably as stable as Froyo ROM's.
They're like all the latest changes the CM team have made to the ROM.
Possibly, however N100 could have another bug instead (although this is not the case).
Refer to this for more info: http://wiki.modaco.com/index.php/ZTE_Blade_CyanogenMod

a new bug.. i like having an gps, so i use Sygic, and when i turn on Sygig, it makes the phone reboots..
so ill guess... hmm.. reset when charging or having a gps...??
any fix for this one?
EDIT...
just started up a compassapp that uses gps as well, found my location, went back in and started Sygic and starts up fine and no reboot..
lol... some things are random..

CM7 should reboot once when using GPS and then be fine.

many thanks!!
all good today..

Please unpin this thread.

UPDATE: 7.1 "stable" is OK but personally I prefer nightlies.
They are not stable! In fact RC1 boot loops! Please flash the latest nightly and google apps going forward!
Nightlies available here:
http://download.cyanogenmod.com/?type=nightly&device=speedy
Change log and link to nightlies here as well:
http://cm-nightlies.appspot.com/?device=speedy
Gapps here:
http://goo-inside.me/gapps/gapps-gb-20110828-signed.zip
http://goo-inside.me/gapps/gapps-gb-20110828-newtalk-signed.zip
1) Copy zips to sd card
2) Backup with ti backup
3) Flash latest clockwork recovery through rom manager
4) Reboot into clockwork recover and run backup from clockwork recovery (aka nandroid)
5) mount usb storage in clockwork recovery and copy ti backups and clockwork recovery backup to your computer. Also copy any other important files on the sdcard (Especially pictures in the DCIM folder).
6) Copy nightly and gapps zips file to phone's sdcard
7) Wipe cache, wipe dalvik cache (under advanced), wipe battery stats
8) Install zips from sd card in this order:
a) CM_Speedyxxx.zip
b) googleapps 828-signed.zip
c) newtalk.zip
9) Reboot phone and wait 10 minutes phone should be in cm7 and working.
10) verify you can open market.
11) If you have problems try starting back at step 7 in clockwork and wipe data/factory reset
Questions/problems should be posted here:
http://forum.xda-developers.com/showthread.php?t=1001578
Optimal settings for CM7 on Sprint here (work in progress):
http://forum.xda-developers.com/showthread.php?t=1262313
These builds may be marked as Rc1 and stable but they are way old and NOT stable.
Before you ask, as of right now the nightlies are the most stable version of CM7 being release right now.

bump.
Please sticky this.

I agree with these not being stable, and the nightlies are far more stable. But you might want to revise the bootlooping on RC1 statement. It can be stopped from bootlooping by flash it, full wipe while its flashed, flashing gaps, and then it will work fine. I haven't tried another kernel after doing that though.

linuxman008 said:
I agree with these not being stable, and the nightlies are far more stable. But you might want to revise the bootlooping on RC1 statement. It can be stopped from bootlooping by flash it, full wipe while its flashed, flashing gaps, and then it will work fine. I haven't tried another kernel after doing that though.
Click to expand...
Click to collapse
Pointless. Just like flashing RC1.

VICODAN said:
Pointless. Just like flashing RC1.
Click to expand...
Click to collapse
Eh, I use mikshift anyway, but when It came out, it was the only rom I had on my sd card, and I needed to make a phone call, so I was forced to make it work. That method saved my life, or at least made it so I could get a ride home, other than that, I wouldn't use it.
In fact, the only reason I would consider the "stables" would be so that I can not have to pay so that I can get updates (with the only paid roms for the shift being the nightlies, I think there is no reason to buy full rom manager)

You don't have to pay for the nightlies, don't know if you are aware of the mirror for the nightlies, but no pay there. Only have to pay if you want to download thru rom manager. Just thought i'd point thay out
Sent from my PG06100 using Tapatalk

linuxman008 said:
In fact, the only reason I would consider the "stables" would be so that I can not have to pay so that I can get updates (with the only paid roms for the shift being the nightlies, I think there is no reason to buy full rom manager)
Click to expand...
Click to collapse
perhaps you missed this thread
http://forum.xda-developers.com/showthread.php?t=1001578
....
cm7 never charges for anything - even with all the crazy amounts of bandwidth they use...

Just to confirm, it's preferable to flash the nightly rather than CyanogenMod 7 for the HTC Evo Shift 4G :: V7.1.0 (9 Oct 2011) just posted?

sdk234 said:
Just to confirm, it's preferable to flash the nightly rather than CyanogenMod 7 for the HTC Evo Shift 4G :: V7.1.0 (9 Oct 2011) just posted?
Click to expand...
Click to collapse
Yes, I'd still rather flash a nightly.
I'm 100% sure 7.1.0 Oct 9 2011 has bugs. Maybe not the bootloop 7.1 RC1 had but nightlies usually have newer features and more bugfixes than any milestone release.

VICODAN said:
Yes, I'd still rather flash a nightly.
I'm 100% sure 7.1.0 Oct 9 2011 has bugs. Maybe not the bootloop 7.1 RC1 had but nightlies usually have newer features and more bugfixes than any milestone release.
Click to expand...
Click to collapse
You're 100% sure CM7.1 has bugs? Have you used 7.1?

I'm using update-cm-7.1.0-Speedy-signed.zip, released 10/9, without issue. OC'd to 1.5 gHz, using ScaryKernel 3.

jesusice said:
You're 100% sure CM7.1 has bugs? Have you used 7.1?
Click to expand...
Click to collapse
Keyboard shortcuts.
Bug.

VICODAN said:
Keyboard shortcuts.
Bug.
Click to expand...
Click to collapse
So, you HAVE used CM7.1? Can you elaborate more as to what the bug is?
This thread was needed when our last RC was months old but it's now outdated and no longer needed. It should be unsticked. CM7.1 is rock solid.

jesusice said:
So, you HAVE used CM7.1? Can you elaborate more as to what the bug is?
This thread was needed when our last RC was months old but it's now outdated and no longer needed. It should be unsticked. CM7.1 is rock solid.
Click to expand...
Click to collapse
You remember that bug when you opened the keyboard and pressed e and it opened email? The one that was only fixable on a reboot?
I have not flashed it. Why would I? How is it different than a nightly? It's a nightly build that's labeled "stable".

VICODAN said:
I'm 100% sure 7.1.0 Oct 9 2011 has bugs. Maybe not the bootloop 7.1 RC1 had but nightlies usually have newer features and more bugfixes than any milestone release.
Click to expand...
Click to collapse
VICODAN said:
You remember that bug when you opened
I have not flashed it. Why would I? How is it different than a nightly? It's a nightly build that's labeled "stable".
Click to expand...
Click to collapse
If you haven't flashed it then you should avoid advising others not to flash it. And I have had that weird KB issue before but not in the last month or more, so I wouldn't assume a bug that you once had is still present in a ROM that you haven't flashed yet. And if it's no different than a nightly build, what's the point of telling people not to flash it but to instead flash a nightly? People should flash CM7.1 if they want to have official support. Bug reports on nightlies are laughed at.
Again, this PSA is outdated and unneeded now.

jesusice said:
If you haven't flashed it then you should avoid advising others not to flash it. And I have had that weird KB issue before but not in the last month or more, so I wouldn't assume a bug that you once had is still present in a ROM that you haven't flashed yet. And if it's no different than a nightly build, what's the point of telling people not to flash it but to instead flash a nightly? People should flash CM7.1 if they want to have official support. Bug reports on nightlies are laughed at.
Again, this PSA is outdated and unneeded now.
Click to expand...
Click to collapse
Changed the thread title, updated OP.

VICODAN said:
Changed the thread title, updated OP.
Click to expand...
Click to collapse
Works for me

The only bugs that I've noticed are with Music Folder Player Free and a one time bug with the camera.
Music Folder Player Free - With the screen on songs play fine until I go to scroll through a folder/list of songs or if the screen is rotated. It starts to stutter and skip while I'm interacting within the program. With the screen off music will randomly stutter and skip and get worse as the song plays. Stock Android music player doesn't have this issue.
Camera - I tried to take a picture today and my phone seemed to lockup; none of the capacitive buttons would work and a menu pop-up didn't go away. When I pulled my phone back out of my pocket the screen was completely garbled and grainy. Had to pull the battery, but afterward everything was fine again.

Philpot85 said:
The only bugs that I've noticed are with Music Folder Player Free and a one time bug with the camera.
Music Folder Player Free - With the screen on songs play fine until I go to scroll through a folder/list of songs or if the screen is rotated. It starts to stutter and skip while I'm interacting within the program. With the screen off music will randomly stutter and skip and get worse as the song plays. Stock Android music player doesn't have this issue.
Camera - I tried to take a picture today and my phone seemed to lockup; none of the capacitive buttons would work and a menu pop-up didn't go away. When I pulled my phone back out of my pocket the screen was completely garbled and grainy. Had to pull the battery, but afterward everything was fine again.
Click to expand...
Click to collapse
You could always try a nightly?

Why is the latest 7.1.0 stable for Speedy not posted on Cyanogen Mirror Network? I grabbed it elsewhere not long after it came out, but seems weird that it still does not show up there.

CM7 Kang Request

To anyone who builds their own CM7 kangs, could you please share a recent build?
Thanks in advance!
Edit: well that was fast, the CM team just released CM7.2 RC1!
http://www.cyanogenmod.com/blog/cyanogenmod-7-2-0-rc1-is-upon-us
http://get.cm/?device=speedy
Edit 2: RC1 is still the latest build, and it just bootloops.

If you're looking for a more recent ICS rom, i'd recommend Deck's pre-beta 4. Using it right now and it is the most stable ICS build yet.

MrLinky said:
If you're looking for a more recent ICS rom, i'd recommend Deck's pre-beta 4. Using it right now and it is the most stable ICS build yet.
Click to expand...
Click to collapse
The op asked about cm7 builds, not ICS.
c00ller said:
To anyone who builds their own CM7 kangs, could you please share a recent build?
Thanks in advance!
Click to expand...
Click to collapse
Check ROM Manager, I believe Sparks has a few cm7 kangs.. you could also check out UKE, its on ROM Manager and SDX.
Sent from my HTC Evo Shift using Tapatalk

crump84 said:
Check ROM Manager, I believe Sparks has a few cm7 kangs.. you could also check out UKE, its on ROM Manager and SDX.
Click to expand...
Click to collapse
Thank you, but the last I checked his kangs had some customizations that I did not want... I don't remember what they were, and if he hasn't uploaded a new one since then they would be a bit dated now anyway (e.g. missing some T9 dialer fixes done in late Feb)

Nevermind! CM7.2 RC1 is now available
http://get.cm/?device=speedy

c00ller said:
Nevermind! CM7.2 RC1 is now available
http://get.cm/?device=speedy
Click to expand...
Click to collapse
Cool let us know how it goes, I'm curious if it's stable or not. Also what customizations were you refering to in my rom builds?

I haven't had any luck with 7.2 RC1 yet.
I tried installing it over nightly #255 (cache/dalvik cache wipe) and after a full reset and it hard booted right after it got to the lock screen. I restored my nandroid (need the phone for work) but will try to download/install it again tonight and see what happens.

ratdog07067 said:
I haven't had any luck with 7.2 RC1 yet.
I tried installing it over nightly #255 (cache/dalvik cache wipe) and after a full reset and it hard booted right after it got to the lock screen. I restored my nandroid (need the phone for work) but will try to download/install it again tonight and see what happens.
Click to expand...
Click to collapse
Same result here, rebooting a few seconds after startup.

ratdog07067 said:
I haven't had any luck with 7.2 RC1 yet.
I tried installing it over nightly #255 (cache/dalvik cache wipe) and after a full reset and it hard booted right after it got to the lock screen. I restored my nandroid (need the phone for work) but will try to download/install it again tonight and see what happens.
Click to expand...
Click to collapse
nativ73 said:
Same result here, rebooting a few seconds after startup.
Click to expand...
Click to collapse
*waits for sparksco to act surprised*

ratdog07067 said:
I haven't had any luck with 7.2 RC1 yet.
I tried installing it over nightly #255 (cache/dalvik cache wipe) and after a full reset and it hard booted right after it got to the lock screen. I restored my nandroid (need the phone for work) but will try to download/install it again tonight and see what happens.
Click to expand...
Click to collapse
nativ73 said:
Same result here, rebooting a few seconds after startup.
Click to expand...
Click to collapse
Upon boot up, skip the sign-in, then wait for the reboot. Upon the next boot up, pull down the notification bar and turn off GPS. After this the reboot should stop.

ratdog07067 said:
I haven't had any luck with 7.2 RC1 yet.
I tried installing it over nightly #255 (cache/dalvik cache wipe) and after a full reset and it hard booted right after it got to the lock screen. I restored my nandroid (need the phone for work) but will try to download/install it again tonight and see what happens.
Click to expand...
Click to collapse
nativ73 said:
Same result here, rebooting a few seconds after startup.
Click to expand...
Click to collapse
Try flashing one of the kernels from HERE and hopefully that fixes it. That's the only thing I can think of this being a kernel issue.
cloverdale said:
Upon boot up, skip the sign-in, then wait for the reboot. Upon the next boot up, pull down the notification bar and turn off GPS. After this the reboot should stop.
Click to expand...
Click to collapse
Try a different kernel that should fix the reboot issues with GPS.

sparksco said:
Try flashing one of the kernels from HERE and hopefully that fixes it. That's the only thing I can think of this being a kernel issue.
So audio is confirmed working? I won't have time to flash this until later today..
Click to expand...
Click to collapse
Audio is working fine, but do not flash if you need GPS. It turns out that yes, you can prevent a reboot by quickly turning it off, you can immediately turn it back on, avoiding a reboot, and you can even get a lock on the GPS, but it will reboot again shortly thereafter.
I am going to try another kernel and report back later.
Edit: After flashing your port of "Pershoot/LordLockaN Kernel V14", the reboot issue has been fixed. I am working in my basement, and so cannot check to see if the GPS locks, but all else is well.
Edit2: Though your kernel ports fix the GPS reboot, they take away all audio.

cloverdale said:
Audio is working fine, but do not flash if you need GPS. It turns out that yes, you can prevent a reboot by quickly turning it off, you can immediately turn it back on, avoiding a reboot, and you can even get a lock on the GPS, but it will reboot again shortly thereafter.
I am going to try another kernel and report back later.
Edit: After flashing your port of "Pershoot/LordLockaN Kernel V14", the reboot issue has been fixed. I am working in my basement, and so cannot check to see if the GPS locks, but all else is well.
Edit2: Though your kernel ports fix the GPS reboot, they take away all audio.
Click to expand...
Click to collapse
I thought this might be the case with the audio in the rom and kernel. I need to work on a new kernel that will include some of the new audio changes that work with the rom.

sparksco said:
Also what customizations were you refering to in my rom builds?
Click to expand...
Click to collapse
Minor stuff like this and when I checked your site it had the fonts switched to roboto or something.
Anyway, now that we all confirmed that CM's 7.2 RC1 release is garbage, how can we go about letting them know so 100s/1000s of users don't go downloading and flashing something that doesn't work?
What really bothers me is the fact that the CM team stated "CM7.2 is more than ready for everybody to enjoy ", and I read that they have been doing a lot of offline testing of RC1 when clearly no one there tested this particular build. Does the Evo Shift 4G even have an official maintainer anymore (toastcfh)?

c00ller said:
Minor stuff like this and when I checked your site it had the fonts switched to roboto or something.
Anyway, now that we all confirmed that CM's 7.2 RC1 release is garbage, how can we go about letting them know so 100s/1000s of users don't go downloading and flashing something that doesn't work?
What really bothers me is the fact that the CM team stated "CM7.2 is more than ready for everybody to enjoy ", and I read that they have been doing a lot of offline testing of RC1 when clearly no one there tested this particular build. Does the Evo Shift 4G even have an official maintainer anymore (toastcfh)?
Click to expand...
Click to collapse
I'm not sure what minor stuff your talking about with my kanged build. I posted the flashable stock fonts. Anyways I don't know what CM is doing nor do I really care anymore. The reboot issue with GPS has been a issue with their kernels for quite sometime now but since I never use their stock kerenls I've never had that issue. I won't be building kanged CM builds anymore since I have own repo source.

Requesting once again, if anyone is making their own (working) builds from CM source.

This is based on cm7 but different in many ways.
http://www.gitorious.org/teamandroid/android/blobs/gingerbread-release/README.mkdn.
Follow my cm7 compiling guide but use these commands instead, then
$ ./Speedy.sh
There's already a build on rom manager along with Dread 7us and one_love_420's roms.

Battery...

Hello,
After I installed ICS (JB or Stock) a had the problem, that the tab took about 80mA - 190mA from the Battery.
I'm monitoring the Battery from my HC 3.2 Overcome, and there the drain was about 20 - 30mA. So I'm not
happy with this Situation.
Then i tried the CM9 experimental from pershoot. And there i have the same low drain from about 20-30mA.
Now i want to know, why in Stock ICS the drain is 3-4 times higher than in CM9?
Can anyybody give me a hint about it.
I've tried it with a clean install, where i really only installed the battery monitor....
cya
stiff

it seems like a kernel issue on stock ics , it keeps searching for signal even if airplane mode is on !
what i did is i installed the stock ROM then i installed a1 kernel over the stock one ..
it seems like the problem is fixed for me

Hi,
thx for your answer, but i already installed aa's kernel.
i tried from 1.59 til 1.7.
now i've 1.64 but no luck....
stiff

Try to fixed by:
stiffmeister75 said:
Hi,
thx for your answer, but i already installed aa's kernel.
i tried from 1.59 til 1.7.
now i've 1.64 but no luck....
stiff
Click to expand...
Click to collapse
I think you use Stock Rom "XXLQ8" - italian ics??!!
If the answer is yes, the problem happens with me with this rom even with A! kernel.
I fix it by these steps:
1- Backup all your data....
2- Downlaod "JellyBeanRom ICS v6" from here: http://forum.xda-developers.com/showthread.php?t=1813651&highlight=battery
3- Make a full wipe.
4- Falsh the "JellyBeanRom ICS v6" as Thread steps.
5- After the tab restart and finshing falshng rom, go to bootloader and make "Wipe Battery State"
6- I hope everthing is fine now.
Or try to flash another stock Rom ver with "Full Wipe Data & system"
This is my personal experience with this issue, and this is the solution that saved me

In CPU spy you will notice that the tab doesn't go to deep sleep for long periods on ics. If you have betterbatterystats installed you will notice that this is caused by a kernel wakelock 'l2_hsic'.
I reverted back to hc3.2 overcome because I couldn't find a fix for the wakelock. But ever since calling was enabled on ics I flashed back for this mod.
I am on stock rooted Italian 4.0.4 and only installed A1 yesterday and have had mixed results so far. If it continues I will probably try V6.
Sent from my GT-I9300 using xda premium

@dana
i've tried all "battery drain" fixes that are here reported.
Also clean installs and so on.
I think that sxi200 is right,
because i had also the wakelock "l2_hsic"
but i don't know what causes this wakelock btw. how to remove it.
cya
stiff
edit:
This log is from pershoot's cm9 01092012 , mobiledata and sync is on:
2012/09/17|02:02:18|-20mA|93%|4083mV|20.9ºC|.0|0
2012/09/17|02:07:18|-17mA|93%|4070mV|20.9ºC|.0|0
2012/09/17|02:12:18|-16mA|93%|4087mV|20.9ºC|.0|0
2012/09/17|02:17:18|-20mA|93%|4089mV|20.9ºC|.0|0
2012/09/17|02:22:18|-15mA|93%|4087mV|20.9ºC|.0|0
2012/09/17|02:27:18|-17mA|93%|4083mV|20.9ºC|.0|0
2012/09/17|02:32:18|-20mA|93%|4087mV|20.9ºC|.0|0
2012/09/17|02:37:18|-17mA|93%|4085mV|20.9ºC|.0|0
2012/09/17|02:42:18|-17mA|93%|4088mV|20.9ºC|.0|0
2012/09/17|02:47:18|-19mA|93%|4087mV|20.9ºC|.0|0
2012/09/17|02:52:18|-19mA|93%|4086mV|20.9ºC|.0|0
2012/09/17|02:57:18|-18mA|93%|4088mV|20.9ºC|.0|0
2012/09/17|03:02:18|-19mA|93%|4084mV|20.9ºC|.0|0
Click to expand...
Click to collapse
This log is from stock ics XWLP5 in aeroplane mode:
2012/09/18|02:06:31|-201mA|78%|3954mV|23.5ºC|.0|0
2012/09/18|02:16:31|-201mA|77%|3952mV|23.7ºC|.0|0
2012/09/18|02:26:31|-202mA|76%|3947mV|23.9ºC|.0|0
2012/09/18|02:36:31|-212mA|76%|3945mV|23.9ºC|.0|0
2012/09/18|02:46:31|-225mA|75%|3942mV|24.0ºC|.0|0
2012/09/18|02:56:31|-223mA|75%|3941mV|24.1ºC|.0|0
2012/09/18|03:06:31|-208mA|74%|3937mV|24.2ºC|.0|0
Click to expand...
Click to collapse
i think that's very strange....

Well maybe there is light at the end of the tunnel. I flashed Toldo's JellyBeanRom ICS V6 XWLP5 which has A1 kernal and haven't had the l2_hsic wakelock since.
I flashed straight over stock ICS without wiping and haven't had a singe problem. Tab now sleeps like a baby. Will keep my eyes on it to make sure.
Sent from my GT-P7500 using xda premium

georgesadam said:
it seems like a kernel issue on stock ics , it keeps searching for signal even if airplane mode is on !
what i did is i installed the stock ROM then i installed a1 kernel over the stock one ..
it seems like the problem is fixed for me
Click to expand...
Click to collapse
I can confirm. I had the same problem and A1 solved it.

hi,
can anyone of you log with Battery Monitor Widget the mA your tab needs,
like my log posted before?
Many thx, because i don't know what i should do with that damn batterydrain....
stiff

havrosh said:
I can confirm. I had the same problem and A1 solved it.
Click to expand...
Click to collapse
Same here.
Flashed ital. ics over p7501 stock hc. Performance was quite nice, huge step foreward but battery drain went up to a couple of percentages per hour in the wannabe sleep mode. I took a look at it with cpu spy and the result was nearly no deep sleep! Even if my tab wasn't in use for the whole night ( only wifi turned on ) the cpu frequency stayed at 216 MHz. This results in a non usable tab for me because i wasn't able to use it a whole day at university without recharging!!
Yesterday evening I flashed A1's 1.7 Kernel over stock ital. ics and woooohooooo more than 6 hours of deep sleep last night (even though more than I had...) and battery only goes down 2 percent within this time.
From today I can tell that deep sleep works perfect until now for the periods of non usage.
BTW: A1 Kernel also solved my problem with flickering HDMI output on my TV!! Thats amazing but I'm going to post this in the seperate thread as well now.
Maybe someone could do me a favour and quote this in the official A1 thread in the developers section because due to the "10 posts rule" I am not allowed to do so..:crying:

Mako Android L B4 causing problems?

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