Database Info

Something wrong with my phone.

OK so it seems my phone has an issue with any rom other than stock as I have tried them all and I have 3 things that happen: a. Phone will reboot on its on or b. The screen will go black with the buttons lit up. Or c. It will freeze on me. This is any rom other than bone stock. Any one know what could be the cause of this?
Sent from my Nexus S using Tapatalk

okay , your phone looks like hard to use.
what version/model is it ? is it possible you flashed GSM ROM to 4G Nexus S ? or 4G ROM to GSM ?
okay , your operator is AT&T , forget it ... it wouldn't be 4G
orginal MIUI and orginal CM7 , all the same ?

I haven't tried any miui roms but every rom I have tried has been for 9020s. I have tried bugles beast, NSCollab, oxygen, we scream for ice cream (which I fully expect to have issues but could not resist trying) , blanddroid, and nexusMV all with the same issue. I even tried several different kernels to see if that would make a difference but it didn't
Sent from my Nexus S using Tapatalk

There's a low chance your cpu can't take any voltages/frequencies outside stock kernel range. Because that black display/lit buttons thingy happens to me if I go too low on voltages or freq.

What are the stock voltage rages? So I can try that theory out?
Sent from my Nexus S using Tapatalk

Nexus has model of 9020S ??
i only heard about 9020A,F,T and 9023
default MIUI doesn't over/underclock or UV

To further update today I have been running a stock 2.3.7 rom made by drew garen that has been running well with no reboots, freezes or anything but again it is stock with the exception of being rooted and 2.3.7 instead 2.3.4 like my stock rom and the only reason I am running it instead of my actual stock one is for google wallet.
Sent from my Nexus S using Tapatalk

The s was ploral it is an a version
Sent from my Nexus S using Tapatalk

djwyman said:
To further update today I have been running a stock 2.3.7 rom made by drew garen that has been running well with no reboots, freezes or anything but again it is stock with the exception of being rooted and 2.3.7 instead 2.3.4 like my stock rom and the only reason I am running it instead of my actual stock one is for google wallet.
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
.............i thought stock ROM highest version is 2.3.6 ...

qtwrk said:
.............i thought stock ROM highest version is 2.3.6 ...
Click to expand...
Click to collapse
Nah, NS4G is running 2.3.7 as it includes the required NFC chip update to run Google wallet.

OK so even with that rom it has been acting stupid though not as bad then I went to my stock rom and again the same thing so I think I am just going to unroot and take it to best buy because I am pretty sure it is not supposed to have this much trouble
Sent from my Nexus S using Tapatalk

Well I am completely stock and unrooted now and so far no problems so my question would now be did I just have a bad root or something? Should I retry rooting now that its back to original or should I take it to best buy and try to get them to replace it? I really like playing with rooted phones and trying different roms and stuff but it is kinda impractical when my phone won't handle it...that's why I am wondering if I had done something wrong maybe?
Sent from my Nexus S using Tapatalk

I have the NS4G but I've never had those issues on any ROM

Well after being unrooted since yesterday I am now no longer getting any freezes, black screens, or reboots. My question now is, did I possibly do something wrong in the root process that might have caused this problem?
Sent from my Nexus S using Tapatalk

Did you try re-rooting it?

nathanson666 said:
Did you try re-rooting it?
Click to expand...
Click to collapse
I did just now using different more up to date rooting kit files then the ones I used before. I am going to stick with the stock rom for the rest of the day just rooted and see if the problem happens and then if it doesn't do like this then I may try running a custom rom and if this does not work I will unroot it again and throw the phone against a brick repeatedly so best buy will take the thing back as I tried taking it back today and i couldn't come up with a good enough reason for them too take it back it seems.

OK update time. Running stock rooted after unrooting and rooting (using a different root kit this time) I am having no issues what so ever and I even tried taxing the CPU by running app after app ran some heavy games and things of that nature with no restarts or freezes, however I tried NSCollab for a little while and it did act up though not as bad as before so I have gone back to stock rooted and everything is fine for now. I may try some other rom later but for now I am happy just to be rooted with no issues with the stock rom. I might try a less modded rom like buggles beast or oxygen net go round though other than not having the notification Widgets and reboot/recovery option when pressing the power button stock rooted does everything I want it too.
Sent from my Nexus S using Tapatalk

djwyman said:
OK update time. Running stock rooted after unrooting and rooting (using a different root kit this time) I am having no issues what so ever and I even tried taxing the CPU by running app after app ran some heavy games and things of that nature with no restarts or freezes, however I tried NSCollab for a little while and it did act up though not as bad as before so I have gone back to stock rooted and everything is fine for now. I may try some other rom later but for now I am happy just to be rooted with no issues with the stock rom. I might try a less modded rom like buggles beast or oxygen net go round though other than not having the notification Widgets and reboot/recovery option when pressing the power button stock rooted does everything I want it too.
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
I think that problem could be kernel. Have you tried any customer kernels? Previously I had freeze issues and this so called 'morning coma', kernel fixed all those problems

while that could be the issue with that rom I think I have discovered my real problem could be something to do with titanium backup, either the program its self or one of my backed up apps. this morning on my stock rom it rebooted twice so I got to thinking and decided to do a wipe but instead of restoring my apps from titanium back up I just used the market website to send all of my apps to my phone and so far that seems to have fixed the issue. the only apps i did not re-install was amazon appstore (and a few games from there) rom manager, and titanium backup so I am assuming my problem is contained in one of those apps if I am no longer having the problem.

With titanium do you you just back up apps and app data? Or system data too?
Sent from my Nexus S using XDA Premium App

[Q] AOSP Roms Cannot Connect to Camera

Sorry if this has been posted somewhere else, but after flashing AOKP Build 3 my camera keeps giving me the error "cannot connect to camera." I have tried clearing data on the gallery app, rebooting the phone, and nothing works.
I researched some and tried some fixes I found but none had any effect.
I then reflashed to stock to see if stock Touchwiz would work and it works with no issues. Wiped all data, reformatted my SD card, removed my SD card and cannot seem to find the culprit. I also flashed CM nightly to see if it was an AOKP issue with my phone, but had same issue
For whatever reason I cannot flash any AOSP rom without having FC on my camera. Any help would be appreciated. Again, sorry if it has been posted somewhere I haven't found, but I've looked for a few days and didn't locate anything that worked.

Did you try fixing permissions?

Zalithian said:
Did you try fixing permissions?
Click to expand...
Click to collapse
Do that and also format cache and dalvik.

shinjielric said:
Do that and also format cache and dalvik.
Click to expand...
Click to collapse
Did all of those and still no change in outcome.

MistarJones said:
Did all of those and still no change in outcome.
Click to expand...
Click to collapse
What version of CWM are you using? I've heard some versions don't play nice with AOSP.
EDIT: I'm assuming you're using CWM.

You happen to try a different camera from the play store? My quess is it wouldnt work either as its probaly a kernel issue?
Sent from my SCH-I535 using xda app-developers app

shinjielric said:
What version of CWM are you using? I've heard some versions don't play nice with AOSP.
EDIT: I'm assuming you're using CWM.
Click to expand...
Click to collapse
I am using las test, CWM touch. Could try with non touch after work.

x714x said:
You happen to try a different camera from the play store? My quess is it wouldnt work either as its probaly a kernel issue?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Yeah I tried with several camera alternatives and all said couldn't connect to camera as well. :/

this happened to me randomly yesterday on CM10 M1, I'm on leankernal and using twrp. I had just flashed the aosp camera mod earlier so I thought it was that. I just restored a backup I made the other day and it was all good since. I guess its a good reason to make routine backups on aosp

DertyDOH said:
this happened to me randomly yesterday on CM10 M1, I'm on leankernal and using twrp. I had just flashed the aosp camera mod earlier so I thought it was that. I just restored a backup I made the other day and it was all good since. I guess its a good reason to make routine backups on aosp
Click to expand...
Click to collapse
I tried that and any backup still having camera FC issues.

Originally Posted by shinjielric
What version of CWM are you using? I've heard some versions don't play nice with AOSP.
EDIT: I'm assuming you're using CWM.
Click to expand...
Click to collapse
I am using las test, CWM touch. Could try with non touch after work.
Click to expand...
Click to collapse
I'm using cwm touch v6.0.1.2 and its working good for me.
Sent from my SCH-I535 using xda premium

I've had the same issue and reflashed multiple times and tried all the above.
My Galaxy III SCH-I535 operates on Android 4.1.2 aokp_d2vzw_jb_milestone_1
Kernel is 3.0.48-cynagenmod-faux123-vzw...
I love this ROM. I'm not sure how it randomly a day or two into operation just quit the camera operation completely. This would be a real miracle solved

MistarJones said:
Sorry if this has been posted somewhere else, but after flashing AOKP Build 3 my camera keeps giving me the error "cannot connect to camera." I have tried clearing data on the gallery app, rebooting the phone, and nothing works.
I researched some and tried some fixes I found but none had any effect.
I then reflashed to stock to see if stock Touchwiz would work and it works with no issues. Wiped all data, reformatted my SD card, removed my SD card and cannot seem to find the culprit. I also flashed CM nightly to see if it was an AOKP issue with my phone, but had same issue
For whatever reason I cannot flash any AOSP rom without having FC on my camera. Any help would be appreciated. Again, sorry if it has been posted somewhere I haven't found, but I've looked for a few days and didn't locate anything that worked.
Click to expand...
Click to collapse
Did you ever get this resolved? I'm having the exact same issue and would love to get it fixed.

re fix
bandit2443 said:
Did you ever get this resolved? I'm having the exact same issue and would love to get it fixed.
Click to expand...
Click to collapse
I wasn't able to get it to fix. I came to the conclusion that it was a hardware issue. For whatever reason it works on touchwiz but wouldn't work on aosp ROMs. I got a warranty replacement and it solved the issue. Wasn't able to find a software fix.

MistarJones said:
I wasn't able to get it to fix. I came to the conclusion that it was a hardware issue. For whatever reason it works on touchwiz but wouldn't work on aosp ROMs. I got a warranty replacement and it solved the issue. Wasn't able to find a software fix.
Click to expand...
Click to collapse
Oh wow... that's an idea i hadn't thought of. Samsung replaced it under warranty? What did you tell them was wrong with it?

Camera Can't Connect & Firmware
shinjielric said:
I'm using cwm touch v6.0.1.2 and its working good for me.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
I am having the "cannot connect" issue on CM10. I posted about it here: http://forum.xda-developers.com/showthread.php?t=2152348
The camera works fine in stock, but on CM10 no-go. According to this post its a firmware issue: http://forum.xda-developers.com/showthread.php?t=2006128
only problem is to fix I need to figure out what camera firmware I have so I can flash a new one - but I cannot determine what firmware i535 has? Anyone?

Based on another thread, seems like I might be able to copy the bins from the cameradata folder on stock where the camera works. No need to flash or anything.
http://forum.cyanogenmod.org/index.php?/topic/66022-Can't-Connect-To-Camera
Sent from my SCH-I535 using xda app-developers app

App not compatible -> fix build.prop?

Hi guys,
there is an app in the play-store which i would like to have on my nexus5 (click)
But it says that the app and my n5 are not compatible.
I'm wondering why because my n5 runs cm11 and the app was available for my galaxy s2 which also runs cm11.
So i modified the build.prop on my n5 and set the ro.product.device=gt-i9100.
But still i am not able to intall the app on my n5.
Do you have any advice how i could get the app?
I also was not able to find the apk using google :crying:
Thanks for your help!

leAndroid91 said:
Hi guys,
there is an app in the play-store which i would like to have on my nexus5 (click)
But it says that the app and my n5 are not compatible.
I'm wondering why because my n5 runs cm11 and the app was available for my galaxy s2 which also runs cm11.
So i modified the build.prop on my n5 and set the ro.product.device=gt-i9100.
But still i am not able to intall the app on my n5.
Do you have any advice how i could get the app?
I also was not able to find the apk using google :crying:
Thanks for your help!
Click to expand...
Click to collapse
i don't think the playstore is looking for your device model - more likely for your sdk level/ screenresolution or something like that ^^ (so manipulationg build.prop like you did doesn't provide you anything

that app was updated last in jan 2013. way before the n5 release, way before android 4.4 or 4.3 or 4.2. i think you would have to wait until they at least update the app to support the android version that youre running. email and ask the developer.

So i am curious about what would happen if i replace my build.prop with one from a stock s2. I mean the app was running on my s2 cm11 so i guess the android os doesn't matter. But i'm wondering what else could be a reason. I can't believe the screen resolution is causing my issue.
And one last question: i can't break anything by replacing my build.prop temporarily can i?
Gesendet von meinem Nexus 5 mit Tapatalk

leAndroid91 said:
So i am curious about what would happen if i replace my build.prop with one from a stock s2. I mean the app was running on my s2 cm11 so i guess the android os doesn't matter. But i'm wondering what else could be a reason. I can't believe the screen resolution is causing my issue.
And one last question: i can't break anything by replacing my build.prop temporarily can i?
Gesendet von meinem Nexus 5 mit Tapatalk
Click to expand...
Click to collapse
You'll brick your phone, or at least make it very non-functional. Have fun with that

leAndroid91 said:
So i am curious about what would happen if i replace my build.prop with one from a stock s2. I mean the app was running on my s2 cm11 so i guess the android os doesn't matter. But i'm wondering what else could be a reason. I can't believe the screen resolution is causing my issue.
And one last question: i can't break anything by replacing my build.prop temporarily can i?
Gesendet von meinem Nexus 5 mit Tapatalk
Click to expand...
Click to collapse
you just wont boot and will have to reflash your rom or the factory img. you wont brick it, unless you dont know how to fix it. when not just edit your build.prop manually with a root file explorer?

I did modify my build.prop using root explorer but gt-i9100 as device and 4.3 as os weren't working. So i guess i will try a few more settings. But the play store didn't detect my n5 with modified build.prop so i'm wondering if this workaround is working at all.
Gesendet von meinem Nexus 5 mit Tapatalk

[Q] camera not working on samsung tab p3110

Hi, i'm new to rooting. just managed to root my old samsung tab 2 7.0 GT-P3110 using CM-11 nightly.
after successful rooting it, i found there isn't any camera app on my tablet and several tries on downloading one, didn't work at all.
i have tried installing some camera zip and camera apk but it still didn't work.
anyone can you please help me and guide me on how can i get my camera back on my tablet??
very much appreciated.
thank you

newrootie said:
Hi, i'm new to rooting. just managed to root my old samsung tab 2 7.0 GT-P3110 using CM-11 nightly.
after successful rooting it, i found there isn't any camera app on my tablet and several tries on downloading one, didn't work at all.
i have tried installing some camera zip and camera apk but it still didn't work.
anyone can you please help me and guide me on how can i get my camera back on my tablet??
very much appreciated.
thank you
Click to expand...
Click to collapse
you should have "focal" as your camera app, but you can also just flash a stock ROM that has root so everything is back to its familiar setup and apps.
Sent from my SGH-T999 using Tapatalk

Hi guys, i have exactly the same problem. I have a 3110 and i decided to move from cm 10.1.3 to cm11. I performed the data wipe/factory reset with the latest version of twrp, installed the rom, installed the gapps package and everything seems to work fine except for the camera. There is no app at the drawer, i can not install google camera from the playstore, and the apps that i installed either in apk or zip form do not work. Some crash, camera zoom fx doesnt have the option to take picture and some other apps throw an error message about "can not find the hardware camera" and staff like this. Can someone help me plz?
tokenpoke said:
you should have "focal" as your camera app, but you can also just flash a stock ROM that has root so everything is back to its familiar setup and apps.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
i installed it and it also doesnt work. It reports that it can not connect to the hardware camera and then it crashes.

katsika said:
Hi guys, i have exactly the same problem. I have a 3110 and i decided to move from cm 10.1.3 to cm11. I performed the data wipe/factory reset with the latest version of twrp, installed the rom, installed the gapps package and everything seems to work fine except for the camera. There is no app at the drawer, i can not install google camera from the playstore, and the apps that i installed either in apk or zip form do not work. Some crash, camera zoom fx doesnt have the option to take picture and some other apps throw an error message about "can not find the hardware camera" and staff like this. Can someone help me plz?
i installed it and it also doesnt work. It reports that it can not connect to the hardware camera and then it crashes.
Click to expand...
Click to collapse
then it must be an issue in the ROM itself.
either a bad download or an bug in the system.
inquire in the specific rom thread to address the problem and if you have time Google "log cat android" and make a log when you try to open the app.
Sent from my SGH-T999 using Tapatalk

@tokenpoke its indeed a bug in the system, camera is broken at cm 11atm, you need to apply a fix. The solution can be found here http://forum.xda-developers.com/showpost.php?p=53381666&postcount=2909 , thnx goes to @webdroidmt for pointing that out.

katsika said:
@tokenpoke its indeed a bug in the system, camera is broken at cm 11atm, you need to apply a fix. The solution can be found here http://forum.xda-developers.com/showpost.php?p=53381666&postcount=2909 , thnx goes to @webdroidmt for pointing that out.
Click to expand...
Click to collapse
thanks.
it no longer helps me since I traded my tab for a chromebook (I buy devices to play with them and trade friends when I get bored) but I'll pass it along to the new owner
Sent from my SGH-T999 using Tapatalk

tokenpoke said:
you should have "focal" as your camera app, but you can also just flash a stock ROM that has root so everything is back to its familiar setup and apps.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Thank you bro, will try to use a different ROM to test it out again.
i have tried the thread stated in this forum where i also found many having such issues, but the remedy just didn't work out for me.
I guess i will have to re-root it again.
thank you once again:angel:

newrootie said:
Thank you bro, will try to use a different ROM to test it out again.
i have tried the thread stated in this forum where i also found many having such issues, but the remedy just didn't work out for me.
I guess i will have to re-root it again.
thank you once again:angel:
Click to expand...
Click to collapse
no need to reroot if you've installed a custom recovery.
most ROMs are already rooted and there is an option when booting your system from recovery that injects root into nonrooted roms
Sent from my SGH-T999 using Tapatalk

Weird Apk Install Problem

I can't click on the Install button when trying to install an APK. The screen acknowledges the touch, but the button doesn't do anything. But when I rotate the phone to Landscape, it works fine.
Youtube video link: https://www.youtube.com/watch?v=U9xHA3f7-_c
(For some reason the forum doesn't want to embed this video)
Anyone have any ideas? Let me know.
Stock CM11S and Root.

It's a bug. Happens to me using Mahdi rom as well. Most likely cm related. Just stick to the workaround for now, would probably help if you made a post on jira.cyanogenmod.org so cm can look into it.
Sent from my One A0001 using Tapatalk