Database Develop

[Q] Camera error after GB update

Hi
I've upgraded to 2.3.3 and my camera doesnt work anymore. The screen comes black for a few seconds and then the message "Camera error. Cannot connect to camera" appears. The flashlight is also doesnt work. I have some MoDaCo firmware HTC Sense before, as I remember...
Help me to fix it, please.
Thanks

Flash newer radio.

Jack_R1 said:
Flash newer radio.
Click to expand...
Click to collapse
Could you tell me how to do it, pls? What is the last version of radio? How to check it?

Settings / About / Baseband
If the version is 4.06 / 5.08 / 5.12 (the version is in the middle of the long string there) - then there's some other problem in the system. If the version is 4.02 or 4.04 - then you need to go to Developers forum, open any Gingerbread ROM thread, and see the instructions for flashing Radio. Or look at my signature.

Jack_R1 said:
Settings / About / Baseband
If the version is 4.06 / 5.08 / 5.12 (the version is in the middle of the long string there) - then there's some other problem in the system. If the version is 4.02 or 4.04 - then you need to go to Developers forum, open any Gingerbread ROM thread, and see the instructions for flashing Radio. Or look at my signature.
Click to expand...
Click to collapse
The Baseband Version is 32.41.00.32U_5.08.00.04
What I'm thinking is could it be the problem because my Nexus had non original firmware before the GB update, and maybe I didnt make some important thing which blocking my camera now? Maybe I need to re-flash the radio with some original image? I'm totally NOOB in all these things...

Your radio is 5.08 - which means it's updated and the problem is elsewhere.
If you didn't upgrade to Gingerbread from a clean FRG83G build, but from some other build - you'll need to reflash the ROM. You can do it if you have unlocked bootloader. Read Wiki, it has the guide for installing custom ROMs - execute it, and use Gingerbread stock build from one of the threads in Development forum.

Jack_R1 said:
Your radio is 5.08 - which means it's updated and the problem is elsewhere.
If you didn't upgrade to Gingerbread from a clean FRG83G build, but from some other build - you'll need to reflash the ROM. You can do it if you have unlocked bootloader. Read Wiki, it has the guide for installing custom ROMs - execute it, and use Gingerbread stock build from one of the threads in Development forum.
Click to expand...
Click to collapse
Thanks for your advices. Just upgraded the radio to 5.12 via fastboot. The camera still not work Will try to flash to original state...

ok, i've tried to rollback to original FRG83, se-flashed boot, recovery, but no luck - camera didnt started. Hovewer, i tried the flashlight torch and it started to work (it didn't like a camera before), so I'm sure now the camera issue is the software now - not a hardware.
Does anybody have some advices?

P0MkA said:
ok, i've tried to rollback to original FRG83, se-flashed boot, recovery, but no luck - camera didnt started. Hovewer, i tried the flashlight torch and it started to work (it didn't like a camera before), so I'm sure now the camera issue is the software now - not a hardware.
Does anybody have some advices?
Click to expand...
Click to collapse
How did you flash frg83? via passimg or you flashed rooted rom from dev section? If you didn't use passimg method you should try wiping everything (cache, dalvik, factory reset) from the recovery.
BTW, if you have custom recovery you should be able to restore nandroid backup (which I assume you did;P ) and see if there is this problem too.
Cheers!

k_myk said:
How did you flash frg83? via passimg or you flashed rooted rom from dev section? If you didn't use passimg method you should try wiping everything (cache, dalvik, factory reset) from the recovery.
BTW, if you have custom recovery you should be able to restore nandroid backup (which I assume you did;P ) and see if there is this problem too.
Cheers!
Click to expand...
Click to collapse
i've flashed frg83 using fastboot. And updated to 2.3.3 via recovery (RA-passion-v2.2.1). And yes, I wiped everything using the recovery. Unfortunately, I do not know what is nandroid backup, so I didnt do it
Hope there is a way to get my camera back to work... Could you tell me what to do, step by step, to make my Nexus fully functional with the 2.3.3 firmware, please!

P0MkA said:
i've flashed frg83 using fastboot. And updated to 2.3.3 via recovery (RA-passion-v2.2.1). And yes, I wiped everything using the recovery. Unfortunately, I do not know what is nandroid backup, so I didnt do it
Hope there is a way to get my camera back to work... Could you tell me what to do, step by step, to make my Nexus fully functional with the 2.3.3 firmware, please!
Click to expand...
Click to collapse
I'd love to, but unfortunately I don't know what causes this problem at the moment I think it wouldn't hurt to try loging what is going on when you open camera.apk. Try adb logcat from your pc or install "alogcat" from market, start camera app and paste here the log file.
Lesson for future always do nandroid backup You can do this from recovery, it will do phone's memory image Then you can always revert back to what you had before flashing new rom

k_myk said:
I'd love to, but unfortunately I don't know what causes this problem at the moment I think it wouldn't hurt to try loging what is going on when you open camera.apk. Try adb logcat from your pc or install "alogcat" from market, start camera app and paste here the log file.
Lesson for future always do nandroid backup You can do this from recovery, it will do phone's memory image Then you can always revert back to what you had before flashing new rom
Click to expand...
Click to collapse
Yeah... backuping is a cool thing.... It is just my first experience with the Android phone... Maybe will find some kind of solution for this...

Well... Problem stays... However I've found few interesting things. As I've mentioned above, after the 2.3.3 update the camera and flashlight doesnt work enymore. But I've installed Z-DeviceTest and found that after the reboot this app (which provides the hardware test) sees the camera and flashlight! But, unfirtunately, doesnt able to test it. Moreover, if to start some torchlight widget directly after the reboot, the flashlight works!!! But it is not after the camera start... So, maybe someone will find this information useful.

@Pomka
have you found the Satu Solution yet ?
mmm. i guess you borrow from somebody the nandroid back up and restore it...
then u will know whether it is a hardware issue or Software Issue.
Logic ?

sevensaints said:
@Pomka
have you found the Satu Solution yet ?
mmm. i guess you borrow from somebody the nandroid back up and restore it...
then u will know whether it is a hardware issue or Software Issue.
Logic ?
Click to expand...
Click to collapse
Stupid actually. Its stay the same, not working....
found the solution!
http://forum.xda-developers.com/showthread.php?t=717870&highlight=frf91
You have go go back to stock ROM.....then camera Happy Trigger Finger!
yeah...
1. Go back to stock through HBOOT
2. Flash back ur fav ROM - mine-MIUI AU
pls click thanks

Stability problem

Hello, I'm using Semaphore + CM10 JB for few weeks (installed with your support).
However I have a problem. The stability. My phone likes to resets byself, even few times per day. It happens irregularly. What's interesting, sometimes phone resets to the CWM. Sometimes resets and backs to work, sometimes totally offs the phone (and i need to pull out the battery) or freeze on cyanogenmod start screen (but not on normal start, only when resets)
Sometimes it happens when i'm using the phone, sometimes not. He likes to do that when i'm sleeping (for example, goes to the CWM and discharge the battery by whole night on full bright).
And much smaller, but maybe important issue: when the phone starts, shows the message Warning! A problem was detected with your device. Your device IMEI number is invalid. And invalid IMEI number could cause network issues including the inability to call emergency numbers.
Firstly I installed CM10, i had the problems with the network, but after @xsenman's help (reinstall with older ROM before flashing CM10) everything works correctly and i can see IMEI too. I made an EFS backup in that old ROM, should i use that? This message doesn't intrude me, but i'm just thinking if this could be connected with reseting problems. My SGS works really nice, but that one issue is really annoying.

100 views and really no one can help?
Come on, i feel so lonely

I'd recommend flashing a clean GB stock, restoring your IMEI, flashing CM9 twice and then flashing CM10 ROMs (if you want them lol). Always be sure that you wipe your phone after installs.
Sent from my Gameboy Color

thanks for your answer. However, maybe it's not a ROM problem? Maybe some application makes an issue. Is there any log where i can check that?

That IMEI stuff definitely isn't app-caused. I can only repeat my statement above. Don't worry about data, you can backup everything using Titanium Backup and SMS Backup+.
Btw: What ROM are you on?
Best regards
Sent from my Gameboy Color

True, IMEI not, but it's not a real issue for me. Actually, i'm absolutely satisfied of my i9000 (maybe flashlight absence, but it's hardware). Everything works fine, but reseting problem makes me nervous when I use the phone as car dvr or for endomondo ect.
I use Cyanogenmod 10, one of october's nightly versions.

So basically you don't want to change anything but you want us to help you? Sorry, that's not the way a community works.

You didn't understand me. My problem is phone reseting. I want to find the reason of the issue. Because without it, i can install new software and still have the same problem.

przemek211 said:
You didn't understand me. My problem is phone reseting. I want to find the reason of the issue. Because without it, i can install new software and still have the same problem.
Click to expand...
Click to collapse
Since when has this problem occurred? I doubt an app makes a phone reset itself.
Edit: I looked around your post history and you seem to have posted in the semaphore thread. Maybe something is wrong with the kernel?
Sent from my GT-I9000

Thanks for your answer. It's hard to say because I've flash a ROM and out of hand I installed the applications. It's the worst type of problems, because it doesn't happen instantly or regularly. Actually since i wrote the topic, i didn't see the problem, however i saw two-three times the attention about IMEI, so i think, the phone resets, but not seen.
/// amerkiller: you are using i9000 too, could you recommend me any other ROM? Probably I will need to install a ROM and wait, two-three days and check if the ROM makes any issues.
/// maybe, but how can i check it? It looks like work nice, my question in Semaphore's thread was about the features

I use Remics-JB, you can try it out if you want a Samsung touchwiz feel, and apps from the S3.
Slimbean if you want a minimalist ROM.
Hopefully, the problem will disappear.
Powodzenia
Edit: regarding the kernel, you can flash Devil and see if the problem persists.
Sent from my GT-I9000

So I will try Devil + Slimbean, thank you
amerkiller1995 said:
Powodzenia
Click to expand...
Click to collapse
Poles everywhere?
pozdrawiam

BlueFlame4 said:
I'd recommend flashing a clean GB stock, restoring your IMEI, flashing CM9 twice and then flashing CM10 ROMs (if you want them lol). Always be sure that you wipe your phone after installs.
Sent from my Gameboy Color
Click to expand...
Click to collapse
Ok, so i want to reflash my i9000. So - i have JVU's gingerbread ROM, is that correct stock ROM? Should i make the WIPE here? I'm not sure about restoring IMEI. Should i do that in GB's temporary ROM or (as I think) later in JB's? Of course, earlier I need to backup the efs folder with IMEI so i think i should do that in GB's and restore it in CM10 (or in Slimbean which I want to test). And one more doubt. You said flashing CM9 twice. Why is that? And how can I do that if i'm installing the ROM in CWM?

przemek211 said:
Ok, so i want to reflash my i9000. So - i have JVU's gingerbread ROM, is that correct stock ROM? Should i make the WIPE here? I'm not sure about restoring IMEI. Should i do that in GB's temporary ROM or (as I think) later in JB's? Of course, earlier I need to backup the efs folder with IMEI so i think i should do that in GB's and restore it in CM10 (or in Slimbean which I want to test). And one more doubt. You said flashing CM9 twice. Why is that? And how can I do that if i'm installing the ROM in CWM?
Click to expand...
Click to collapse
You can find tutorials about flashing to stock.
http://forum.xda-developers.com/showthread.php?t=1102881
Flashing the stock ROM will recover your IMEI number if you currently don't have it and will wipe your personal files. Backup your IMEI while you're on GB and if you lose it, then restore it. Fyi I never lost my IMEI, it's not common. You should flash JB / cm10 twice, ICS/cm9 should be okay after one flash. Remember to wipe if the instructions say so.
When you'll attempt to flash cm10 in recovery, you'll get a warning about partition change. You'll have to chose to flash second time, this time it should work and the phone will reboot into a bootloop. Pull out the battery and enter recovery and flash cm10 again. This time it well install and reboot successfully.
Sent from my GT-I9000

It's everything working nicely? Asking out of curiosity.
Sent from my GT-I9000

Hi, thanks for your interest
Two days ago I made a re-flash Stock > CWM > CM9 (twice) > CM10
Attention about IMEI doesn't longer appear
I've installed apps. The phone has resets for a one time when I was using some app. It is not a big problem for me if SGS makes that from time to time (maybe some apps are not adapted to the JB very well). However today I used him to record my drive (dailyroads voyager) and when i tried to stop the recording, he doesn't backs to life (just I needed to pull the battery out) and video file was corrupted. But when I was getting back to home it worked correctly. I have no idea why that's happen.

przemek211 said:
Hi, thanks for your interest
Two days ago I made a re-flash Stock > CWM > CM9 (twice) > CM10
Attention about IMEI doesn't longer appear
I've installed apps. The phone has resets for a one time when I was using some app. It is not a big problem for me if SGS makes that from time to time (maybe some apps are not adapted to the JB very well). However today I used him to record my drive (dailyroads voyager) and when i tried to stop the recording, he doesn't backs to life (just I needed to pull the battery out) and video file was corrupted. But when I was getting back to home it worked correctly. I have no idea why that's happen.
Click to expand...
Click to collapse
Restarts shouldn't happen that was some unusual circumstance. The video problem is weird, post here if it happens again, lets hope its just bad luck.

Ok, I'll look on it.
I have one other question and maybe you will know.
Call recording. There are two options for use this feature. Simple MIC recording apps and 'two-way call recording' which is much better, however it needs kernel with handle of it. I didn't find anyone for SGS, so I want to use MIC recording. There are many apps in Google Play. However any of them makes 0kB files of record on JB's CM10. When I was using gingerbread it didn't worked too however files were good, but the second side of call didn't hear me.

przemek211 said:
Ok, I'll look on it.
I have one other question and maybe you will know.
Call recording. There are two options for use this feature. Simple MIC recording apps and 'two-way call recording' which is much better, however it needs kernel with handle of it. I didn't find anyone for SGS, so I want to use MIC recording. There are many apps in Google Play. However any of them makes 0kB files of record on JB's CM10. When I was using gingerbread it didn't worked too however files were good, but the second side of call didn't hear me.
Click to expand...
Click to collapse
In regards to two way recording, i don't think it's solved...
http://forum.xda-developers.com/showthread.php?t=863074&page=38
I never needed that feature, so i won't be much help, try different apps and remember some apps are on XDA, not only the play store.
Sent from my GT-I9000

I saw that, but it is only for Froyo, when i installed it into gingerbread i needed to re-flash my SGS
I tried a lot of apps, however it looks like being locked (if worked they made 0kB files)

[Q] Anyone else with this problem?

after flashing CM10 my soft keys (the ones at the bottom) just won't work . They work pefectly inside CWM..
In another ROM, CM7 modded by boype, they work pretty good (still not as good as in CWM).
Is there anyone with the same problem??
If you don't have this problem, can you please let me know what ROM+Kernel you're using? then I can verify if this is a software or hardware issue. :good:

Darkwatch321 said:
after flashing CM10 my soft keys (the ones at the bottom) just won't work . They work pefectly inside CWM..
In another ROM, CM7 modded by boype, they work pretty good (still not as good as in CWM).
Is there anyone with the same problem??
If you don't have this problem, can you please let me know what ROM+Kernel you're using? then I can verify if this is a software or hardware issue. :good:
Click to expand...
Click to collapse
Try once again flashing CM10, don't forget to make full wipe (3 wipes)
No one has this problem

sekhar13515 said:
Try once again flashing CM10, don't forget to make full wipe (3 wipes)
No one has this problem
Click to expand...
Click to collapse
I get an error saying: Sd ext not recognized or something during Dalvik-wipe. Although my sd-card is working :/ I reflashed cm7 boypes and it's working. Then, I reflashed CM10 and it's not working. So, I downloaded the LG tool to get back to stock rom and guess what, it's not working... So, reflash of cm7 from boypes and they're working again..
Is this a kernel issue in combination with my firmware version or something?? (V20n currently)
Thx

Darkwatch321 said:
I get an error saying: Sd ext not recognized or something during Dalvik-wipe. Although my sd-card is working :/ I reflashed cm7 boypes and it's working. Then, I reflashed CM10 and it's not working. So, I downloaded the LG tool to get back to stock rom and guess what, it's not working... So, reflash of cm7 from boypes and they're working again..
Is this a kernel issue in combination with my firmware version or something?? (V20n currently)
Thx
Click to expand...
Click to collapse
Check md5 hashes of GAPPS and CM10 zip.
When you say not working. No lights? No response? More spesifics please.
Sent from my LG-P970

xonar_ said:
Check md5 hashes of GAPPS and CM10 zip.
When you say not working. No lights? No response? More spesifics please.
Sent from my LG-P970
Click to expand...
Click to collapse
Sorry for the inconvenience.
So, i flashed CM10 and the lights were on for about 5 seconds, I could not touch them (so no response it is), and then they went off. The only option is to reflash cm7, because i can't use the softkeys.
Can som1 give me some simple steps for:
- Returning to stock
- flashing the correct firmware using Smartflash (i'm from the Netherlands, i guess thats V20n ; Open Europe?)
- Make sure that the Clear Dalvik-cache option is fully working, (sd-ext error)
- Make CM10 work :/
So, just want to know what steps you guys did in order to make all things work correctly

[Q] (NEED HELP) Phone restart itself into recovery after installing ICS/JB ROM's

Hi Seniors,
This became like a mystery for me..please help me to solve it.
Issue is like this if I install any custom or stock Gingerbread ROMS by phone works like a butter, no issue at all I can say.
But when I install any ICS or JellyBean ROM's it starts creating pain in my neck.
If I am using my phone it never restarts itself but when I lock my phone screen and keep it my pocket M finding that my phone is restarting into recovery mode itself.
Now here comes the strange part...If I play music using any music player and lock my screen it works fine,its not restarting itself ...but once I stop that music player and lock my handset screen in idle mode it goes to recovery in few secs
This only happens if I upgrade to ICS or JellyBean ROM's
One more issue...my wifi works fine If am having GingerBread install on my phone but when I install ICS/JB I cant even start it.
Have tried a lot to get it fixed....but
.....Even I want to taste ICS/JB Rom's like u guys...Please Help Your Rookie.
Thanks & Regards
D.J XactiX
Proud owner of Samsung Galaxy S i9000
----------------------------------------------------------------------------------------ANDROID ROCKS---------------------------------------------------------------------------------------------

Which ICS Rom did you try, and what guide did you use to follow?
The more detail you give the better we all can help you

EwOkie said:
Which ICS Rom did you try, and what guide did you use to follow?
The more detail you give the better we all can help you
Click to expand...
Click to collapse
Hey EwOkie,
Thanks for your courtesy mate...really appreciate it,
So here we go,
I had stock GB 2.3.6 ROM installed on my phone ;ie GT-I9000_XEU_I9000XXJW4_I9000OXAJW4_I9000XXJW4.zip,
after that I rooted my phone using CF-Root-XX_OXA_JW4-v4.4-CWM3RFS,
then I did factory reset,wipe cache and dalvik cashe and installed GamerzRom v11.0 which is a GB ROM,
so far no issue...wifi is working fine,phone is not at all giving me any auto restart issue...its was working like a charm,
then I found ICS_F4k_MOD_v4.0.4_I9000_r3.zip which is an ICS ROM,
I did factory reset,wipe cache and dalvik cache,the I installed ICS_F4k_MOD_v4.0.4_I9000_r3.zip using CWM Recovery console,
it was booted fine to home screen...later on I tried connecting my phone using my wifi router I found that WiFi was not switching on at all,
I locked my phone using lock button then after few secs I am finding my phone is restarting itself in recovery mode,
restarted my back to normal and again the same issue,
I ignored it,
Then I downloaded C-RoM Mix v7 Latest 4.2.1.zip in which had a wifi bug fix,
I did factory reset,wipe cache and dalvik cache,
I flashed it using clockworkmod recovery and had eactly that same issue which I had on ICS ROM,
for WIFI issue I tried flashing wififix.zip and found no resolution,
my phone went into boot loop of Samsung Logo,
then I flashed it back to original stock rom GB 2.3.6 and my phone started working like the way it should be.
This is the whole story
I moved from GB to ICS and then to JB.
Seriously brother I have no idea why its causing this weird issue...this is why I am looking for help from AndroidXperts on XDA site
Kindly help me to sort it out.
Thanks & Regards
D.J XactiX

Ok first up thanks for the info....
When doing a complete wipe before installing another rom make sure you wipe all 4 :
Data / Factory Reset
Cache Partition
Dalvik Cache
Battery Stats
Unless the Developer for the Rom States otherwise.
I know that there are a few ICS Roms that have a lot of bugs please check Info on them before Downloading
Should tell you whats working and whats notto save hassle
As I really only use GB Roms (my own preference)
Might help to try different Modems for your Romas this can help signal/network strength, where do you stay?
Yeah flashing back to 2.3.6 will work all the time as its basically stock.
No matter what Custom Rom I try I always flash JVU 2.3.6 then Root it > then the Custom Rom I want
I never just overwrite it with another Rom...
Hopefully someone with the same Rom as yourself may help as I dont want to give wrong info ....
Or Ask on the Rom site the issue your having with it
If you do need my help ... just ask

EwOkie said:
Ok first up thanks for the info....
When doing a complete wipe before installing another rom make sure you wipe all 4 :
Data / Factory Reset
Cache Partition
Dalvik Cache
Battery Stats
Unless the Developer for the Rom States otherwise.
I know that there are a few ICS Roms that have a lot of bugs please check Info on them before Downloading
Should tell you whats working and whats notto save hassle
As I really only use GB Roms (my own preference)
Might help to try different Modems for your Romas this can help signal/network strength, where do you stay?
Yeah flashing back to 2.3.6 will work all the time as its basically stock.
No matter what Custom Rom I try I always flash JVU 2.3.6 then Root it > then the Custom Rom I want
I never just overwrite it with another Rom...
Hopefully someone with the same Rom as yourself may help as I dont want to give wrong info ....
Or Ask on the Rom site the issue your having with it
If you do need my help ... just ask
Click to expand...
Click to collapse
Hi EwOkie,
Thanks for sharing your experience.
I am followed everything what u just mentioned in ur reply allready...but no go
Me & my GF we both have i9000 and I have followed same installation process on both the phones...her phones works like a charm but mine is like an incomplete soul.
One more thing mate,I really dont understand this ......can you tell me what difference it makes to have JVU 2.3.6 or some other version...how exactly its works....u know what I mean to say.

No idea why we use 2.3.6 JVU with CF Root (Kernel for Recovery) we just do ,, suppose its the best to start with before flashing a Custom Rom
So your partners phone works ok and yours doesnt.. did you try using the PIT File and re-partition?
Check my signature at bottom its a HOW TO Guide incase you get lost
As I says I dont have a lot of experience with ICS or JB Roms as the ones i flashed in the past werent as stable and had some bugs in them
Thats why i stuck with GB Roms

plz help me
today i install a custom rom lollipop in sony xperia c3 dual
but now my phone refused to start even same issue recovery mode... now my phone completely death.. when i try to start it red +green blink but fast mode work easily .. & when i connect my phone to charger it restart it self again & again ... its show only sony logo and its restart again ..plz help me

spen issue on note n7000

Hello folks, I post this thread after months of research and 2 kernel flashing:
I'm having an issue with the S-pen of my galaxy note n7000: it doesn't work, but I noticed the following :
- It works perfectly after a reboot for a moment, but when I turn the screen off and then when I turn it on a moment after : no response.
- the bug started after I updated my phone from GB to ICS. Now I flashed it to JB 4.2.2 and the problem still continue.
Here's the specs (as it's written on my phone) :
Band Version : n7000XXLT3
Core Version : 3.0.31 [email protected] #1
CM Version : 10.1-20130508-Asylum-n7000
Build Number : cm_n7000-userdebug 4.2.2 JDQ39E
eng.chasmodo.20130508.06 5158 test-keys
Could somebody could give a tip on how to fix it ? I found numerous threads about "hovering spen" not working but that's not my problem. Neither a screen detection issue (well, I don't think so.)
I would really apreciate if somebody could help me with Gnote who is not a Gnote anymore
Thanks a lot for the responses !!!

elsaphnite said:
Hello folks, I post this thread after months of research and 2 kernel flashing:
I'm having an issue with the S-pen of my galaxy note n7000: it doesn't work, but I noticed the following :
- It works perfectly after a reboot for a moment, but when I turn the screen off and then when I turn it on a moment after : no response.
- the bug started after I updated my phone from GB to ICS. Now I flashed it to JB 4.2.2 and the problem still continue.
Here's the specs (as it's written on my phone) :
Band Version : n7000XXLT3
Core Version : 3.0.31 [email protected] #1
CM Version : 10.1-20130508-Asylum-n7000
Build Number : cm_n7000-userdebug 4.2.2 JDQ39E
eng.chasmodo.20130508.06 5158 test-keys
Could somebody could give a tip on how to fix it ? I found numerous threads about "hovering spen" not working but that's not my problem. Neither a screen detection issue (well, I don't think so.)
I would really apreciate if somebody could help me with Gnote who is not a Gnote anymore
Thanks a lot for the responses !!!
Click to expand...
Click to collapse
have you tried the official stock 4.1.2 rom?

I would say even before answering above question, have you done a factory reset? (Be on a safe kernel of course)
Sent from my GT-N7000 using Tapatalk 2

yes, when Jellybean went out, I updated my phone hoping it would ok but no amelioration
and when I installed the last rom, I changed also the kernel and following the installation instructions, I did a full wipe and a dalvik cache. It is comparable to a factory reset ?
The only tips I figured out is that it could be a process or an application running on startup that would block the spen, but I'm a noob at it. Could somebody confirm or not ?

elsaphnite said:
yes, when Jellybean went out, I updated my phone hoping it would ok but no amelioration
and when I installed the last rom, I changed also the kernel and following the installation instructions, I did a full wipe and a dalvik cache. It is comparable to a factory reset ?
The only tips I figured out is that it could be a process or an application running on startup that would block the spen, but I'm a noob at it. Could somebody confirm or not ?
Click to expand...
Click to collapse
i suggest you download latest firmware from sammobile.com and flash using pc odin...

Mayank Chandwani said:
i suggest you download latest firmware from sammobile.com and flash using pc odin...
Click to expand...
Click to collapse
This advise is not going to help as it wont wipe the proper partitions. Dont follow that advise.
-----
Here is what you should Do. If this doesn't work, you 100% have damaged hardware and it is not a software problem.
1. Download latest philz kernel and latest prerooted and deodexed jellybean LT5 ROM in flashable zip format. Any ROM of your choice will do. Just make sure its a flashable zip or you will be stuck with no ROM and forced to flash a tar via PC Odin.
2. Flash philz from your external SD card if you don't have a stock recovery or using Mobile odin.
3. Reboot to philz touch recovery
4. Do a nandroid backup just in case
5. Wipe data system dalvik cache preload and .androidsecure
6. Flash the LT5 zip
7. Reboot to system and test spen
If it doesn't work after that it IS your hardware or the pen itself.

asf58967 said:
This advise is not going to help as it wont wipe the proper partitions. Dont follow that advise.
-----
Here is what you should Do. If this doesn't work, you 100% have damaged hardware and it is not a software problem.
1. Download latest philz kernel and latest prerooted and deodexed jellybean LT5 ROM in flashable zip format. Any ROM of your choice will do. Just make sure its a flashable zip or you will be stuck with no ROM and forced to flash a tar via PC Odin.
2. Flash philz from your external SD card if you don't have a stock recovery or using Mobile odin.
3. Reboot to philz touch recovery
4. Do a nandroid backup just in case
5. Wipe data system dalvik cache preload and .androidsecure
6. Flash the LT5 zip
7. Reboot to system and test spen
If it doesn't work after that it IS your hardware or the pen itself.
Click to expand...
Click to collapse
You really seem to be sure of you, cowboy!! OK I will try it as soon as I finished this message an d I'll tell you about it.
Thanks !

The theory is pretty simple... If you wipe out all traces of the past firmware, and the problem persists with new firmware, it is the hardware causing the issue.
Sent from my Samsung Galaxy SV using Tapatalk 3

asf58967 said:
The theory is pretty simple... If you wipe out all traces of the past firmware, and the problem persists with new firmware, it is the hardware causing the issue.
Sent from my Samsung Galaxy SV using Tapatalk 3
Click to expand...
Click to collapse
I agree to the principle : putting the cleanest installation, it's ok for me.:good:
now, I found those data:
http://forum.xda-developers.com/showthread.php?t=2274152&highlight=lt5
http://d-h.st/users/philz_touch/?fld_id=16061#files (PhilZ-cwm6-v5.03.0)
Could somebody tell me if they're effectively compatible and if it's OK to flash those without risk ?
I can't wait to see my Spen running again !

Hi!
I have exactly the same problem. I'm on a CM 12.1 and when I install it, after the first boot, Spen is working for a couple of seconds (10-20) and then suddenly stops (I presume there is something in the software that disable it). Then I reinstall CM 12.1 and same story again - it works for 10-20 seconds and then stops. Spen is working ONLY on the first run (not after every reboot).
Can it be the problem related to the kernel version?

georgekg said:
Hi!
I have exactly the same problem. I'm on a CM 12.1 and when I install it, after the first boot, Spen is working for a couple of seconds (10-20) and then suddenly stops (I presume there is something in the software that disable it). Then I reinstall CM 12.1 and same story again - it works for 10-20 seconds and then stops. Spen is working ONLY on the first run (not after every reboot).
Can it be the problem related to the kernel version?
Click to expand...
Click to collapse
When you say it stops working, does it mean it will give not response at all? I have tried spen on cm12. 1 and cm13 night owl and works on both.

Unfortunately yes - no response at all. It works fine for just about 10 or 20 seconds and then stops. I thought that it may be a hardware problem (maybe capacitors were empty), but in that case Spen will not work at all. And it works only when I do a factory reset or reinstall ROM. Weird...
Yes I red many posts where users said that Spen is working with night owl ROMs but I have this problem. And still didn't found any solution.

georgekg said:
Unfortunately yes - no response at all. It works fine for just about 10 or 20 seconds and then stops. I thought that it may be a hardware problem (maybe capacitors were empty), but in that case Spen will not work at all. And it works only when I do a factory reset or reinstall ROM. Weird...
Yes I red many posts where users said that Spen is working with night owl ROMs but I have this problem. And still didn't found any solution.
Click to expand...
Click to collapse
Did you ever find out was happened with your spen?
Yesterday I noticed this problem on my note. I thought it could be the latest kernel i've had flashed, so I flashed another one. I rebooted, tested my spen and everything was good, so I forget about it. But today my spen is not working at all. I wiped my phone and reinstalled the same rom and it worked at first, but then stopped working forever (I flashed a kitkat rom, then a touchwiz, and it never worked again). I don't know anyone else with this phone so I cannot test if it is the spen :/

Unfotunately not. I stopped thinking about it. I tought to buy new Spen from AliExpress (not expencive solution) and try it...