My personal i927r seems to be having issues with RB 4.2.2. I am about ready to wipe the thing out and start over. I tried going back to 1/24/13 4.2.1 but it would not get past the boot screen with colors.
Issues are: Graphic glitches when reading/browsing/gaming, also lockup/freezing sometimes when graphic glitches happen, sometimes at random. My G/F's i927r doesn't have those issues, just needs it's EFS restored about once a week (I use galaxsim). So what should I do? What does it take to do a fresh install? I wipe caches before and after flashing roms. I use the most recent 1/20/2013 Gapps for it too from thegreatergood. I am using SDSwap 1.0 as instructed by thegreatergood in my last thread. (I still don't have enough posts to post for help in the dev forum).
Should I wipe the whole thing and try a fresh install? 4.2.2 RB works so well on the G/F's phone...but not on mine.
Well I wiped the rom, the caches and data in TWRP, and re-installed the most recent Rootbox 4.2.2 and Gapps 1/20/2013 and SDSwap 1.0. So far seems to be more stable. I have noticed with this ROM that the battery timer is random...my phone could be unplugged for a couple hours and yet it will say it's only been on battery for 30 minutes. Bizzare. But beyond that I will report back if my issues arise again.
That's really strange. I've hopped in and out of Rootbox a few times and haven't encountered anything like the issues you're having. I'm not using SDSwap, maybe that's where the problem is?
My only issue now is that my music skips in aux/BT/loudspeaker, hoping that it'll be fixed next update. I assume it's from the tinkering trying to get bluetooth audio to work on phone calls.
Kursah said:
My personal i927r seems to be having issues with RB 4.2.2. I am about ready to wipe the thing out and start over. I tried going back to 1/24/13 4.2.1 but it would not get past the boot screen with colors.
Issues are: Graphic glitches when reading/browsing/gaming, also lockup/freezing sometimes when graphic glitches happen, sometimes at random. My G/F's i927r doesn't have those issues, just needs it's EFS restored about once a week (I use galaxsim). So what should I do? What does it take to do a fresh install? I wipe caches before and after flashing roms. I use the most recent 1/20/2013 Gapps for it too from thegreatergood. I am using SDSwap 1.0 as instructed by thegreatergood in my last thread. (I still don't have enough posts to post for help in the dev forum).
Should I wipe the whole thing and try a fresh install? 4.2.2 RB works so well on the G/F's phone...but not on mine.
Click to expand...
Click to collapse
I was having similar issues with the latest.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Rooted Samsung SGH-i927 Captivate Glide running @ndroid ICS 4.0.4 LiteRom 0.9.0 & CWM 6.0.1.2 using xda-dev app.
I'm not playing music from my phone (I have a Sansa Clip Zip with Rockbox for that), so I cannot comment there. I can however say, that booting into recover TWRP, clearing caches, clearing data, clearing rom then installing the 2/16/2013 Rootbox, 1/20/2013 GApps, and the SDSwap 1.0 (from the AOSP thread) and now everything is working great! No lockups or freezes. Something was bugged and wasn't getting overwritten.
If that didn't work I was going to wipe all memory and try that...thankfully everything is good to go now. So if you have any issues similar, wipe the caches, data and rom and then try installing. I usually just wiped the caches and installed the new version, which may be my mistake in the first place. I will post back if I find any issues...haven't quite hit the 24hr mark yet.
It seems far what I have heard on rootbox support thread that rootbox also has random reboot issues. So its not just our build of it.
Sent from my SGH-i927 using xda premium
jevan24 said:
It seems far what I have heard on rootbox support thread that rootbox also has random reboot issues. So its not just our build of it.
Sent from my SGH-i927 using xda premium
Click to expand...
Click to collapse
Ya I have read that as well. I will say after doing what I stated above with what I would consider a clean install, I haven't had a single issue aside from a random camera app lockup. No restarts, no graphical glitches, no freezing, everything else has been just about perfect! I am glad the stock android keyboard works and that so far everything else I do on this phone is smooth and fast and pretty damn stable.
Anyone have any force closes trying to set pattern lock screen? Or is it just me. It seems like I have heard this somewhere but can not find it now.
Sent from my SGH-i927 using xda premium
having issues as mentioned in the OP..
graphic glitches/
during movement of 1 screen to another (tab browising), screen gets struck..
games are slow..
having problems with few apps not working (Think they need upgradation)
some shortcuts not working..(long press in scroll down menu - Data selection)
sometimes FC's in settings..
No problem in gallery/photo browsing
my phone:
- random reboots
- often reboots when alarm start (one vibrate then reboot)
- veryyyy looooooong waking up
- swapSD destroyed my 32gb sandisk microsd (but on 4.2.1 version) so watch out with that.
no graphic glitches for me.
i will probably back to official ics because of that waking up, its really annoying
timon12 said:
my phone:
- random reboots
- often reboots when alarm start (one vibrate then reboot)
- veryyyy looooooong waking up
- swapSD destroyed my 32gb sandisk microsd (but on 4.2.1 version) so watch out with that.
no graphic glitches for me.
i will probably back to official ics because of that waking up, its really annoying
Click to expand...
Click to collapse
I haven't had any problems since I did a total clean install. Reboot to TW recover. Chear cache/dalvik, wipe rom, clear data + cache, Install new ROM, 1/20/2013 Gapps, SDSwap 1.0 (from aosp thread), wipe cache/dalvik again, reboot and voila, good to go! Verified on both my phone and my g/f's phone. Worth a shot for you guys out there having issues. You won't lose pics or contacts or provider info (at least I didn't lose my straight talk info), but you will lose login info, wifi info, app saves, etc. Well worth it for a stable and snappy phone. Cheers!
Kursah said:
I ......You won't lose pics or contacts or provider info (at least I didn't lose my straight talk info), but you will lose login info, wifi info, app saves, etc. Well worth it for a stable and snappy phone. Cheers!
Click to expand...
Click to collapse
Titanium backup will save your bookmarks, wifi access points, call logs and any data settings... I have mine scheduled to backup every 3 days to my external SD .. hmm.. I guess I should also set it up to backup to google drive on a regular basis... Things we ALL should be doing!
camera problems
apart from the ocasional reboots wich I can live with I saw 2 issues
I develop Android apps, so these kind of affect me directly:
* I can not use the camera programmatically
when I use the following code I can not get out of the camera app
Intent intent = new Intent(MediaStore.ACTION_IMAGE_CAPTURE);
intent.putExtra(MediaStore.EXTRA_OUTPUT, uri);
startActivityForResult(intent, TAKE_PHOTO_ACTION);
* The Android data backup function is complettly random. This is completly random accross phones and versions, but here also .
I could not get it to work correctly. It just keeps restoring some old backup, not the latest changes. I think data backup does not even get triggered for my app with the normal 'adb shell bmgr run'
You can contact me directly if you need more details.
I use a samsung galaxy s3 gt-i9300
Has anybody else had issues getting GPS to lock? I've been using Gpsconf, waze, google maps etc. all with no luck, even following this thread here : http://forum.xda-developers.com/showthread.php?t=2141812&page=2 ... no dice...
if I can't get GPS going I have to stop using this rom.
I had juice defender installed, and with it installed my phone went into sleep and wouldn't wake up at all ... had to hold power until phone rebooted... this is day1 of using it, so far not looking very promising.
This was my question from the Rootbox thread:
Hmmm.... I tried installing this twice yesterday, and both times my network came up as "Unknown". My carrier and phone number were both listed, but I got an "unknown" network, I couldn't change network type under Phone Information, and and I receive no signal. I did not have this issue with CM10.
Click to expand...
Click to collapse
Related
Hey all,
I have an HTC Evo 4G with Sprint which I flashed to CM7 (CyanogenMod-7.0.3.1-Supersonic) and I am having GPS problems. I have tried every fix I have found on the internet and none of them worked.
If I open Google Navigation, the "Waiting for Location" box pops up and never goes away. I have tried the following:
1. Complete nandroid backup of my CM7 setup.
2. Wiped cache, dalvik, system, all user data.
3. Flashed a rooted stock Sense ROM (I used the stock gingerbread USC version)
4. Used MSL reader app to obtain MSL. (free market app)
5. Opened the Sense dialer and did ##GPSCLRX# - Entered MSL - Rebooted as prompted
6. Booted back into Sense ROM. Opened the Google Maps app. Allowed it to lock on to my location, this took a few seconds. Exited Maps app.
7. Rebooted into recovery. Restored the nandroid backup I made of my CM7 setup.
8. Booted into CM7. Tested Maps app and it locked on to my exact location after a few seconds. Went for a short drive and tested the navigation app which also worked fine.
Click to expand...
Click to collapse
(from forum.cyanogenmod .com/topic/16062-gps-cm7-desire-us-cellular/)
and this one, the first one on Google: forum.cyanogenmod. com/topic/17411-evo-gps-fix/ several times, as well as other fixes (including that one with GPS Status, resetting GPS data, etc) which I can't locate again.
Can anybody help me get GPS working? I really love CM7 and would also love not to have to switch to another ROM just because I can't get my GPS to work.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you actually read ANY of the CM7 threads, there are A LOT of people with this issue. Some people can fix it by doing the gpsclrx trick, others can't. IT'S A BUG WITH CM7, IF YOU DON'T LIKE IT, USE ANOTHER ROM.
And PLEASE post this question in the CM7 thread!!!! There is NO NEED to make a new thread for something that has ALREADY BEEN ASKED a hundred times.
I am in the same boat as you are. I was using Fresh for a long time, but lately I have really been enjoying some of the features that CM7 has. Some people have been saying they are having good luck with the recent nightlies, but I have yet to try them.
Good luck to you, and if GPS is truly a deal breaker, I recommend trying out Fresh EVO.
No GPS on reboot for any Gingerbread Roms.
I'm having, what sounds like, the same issue. For the last 7 months I've been running Fresh Evo 3.5.0.1. Nice rom, but it hasn't aged well (started to lag significantly). Anyways, I've recently been looking around for a good gingerbread ROM. Here are my findings/troubles:
*All gingerbread ROMs give me GPS issues on reboot.
That is to say, after I initially flash the ROM, whether it be CM7 7.0.3.1, Deck's 1.0, MIUI 1.6.3, or the stock 2.3.3 ROMs, GPS does not work. In the case of the AOSP ROMs, the GPS icon in the status bar flickers and then disappears. GPS works after the initial boot after flashing, but upon subsequent reboots stops working.
*For reference, I running the latest radio combo 2.15.00.05.02*
* The problem is not present in the backup I have of Stock 2.1 ROM.
* The problem is not present in the backup of Fresh 3.5.0.1.
* I have tried the ##GPSCLRX# fix from a Sense ROM. It does not work.
* I have tried the GPS Status reset fix. It does not work.
* I have tried flashing restoring a sense backup, flashing the radio combo again, updating the PRL, rebooting, updating profile, rebooting, then flashing a gingerbread ROM. This did not work.
It would seem my phone has a big problem with gingerbread. I'd be very interested to know if anyone else has encountered this, or even resolved this issue. I'm tempted to do the OTA update to see if perhaps it's a custom ROM/Radio problem.
Maybe it is a radio problem and not a gingerbread problem. Does anyone know if it is safe to flash back to 2.15.00.11.19? I'd think because GPS works in 2.1 and 2.2 ROMS that the issue must be with gingerbread and not the radio.
Any help would be greatly appreciated. Gingerbread is tasty.
Will look into newly creates gps.conf for sticking on reboot
Uncle Jimmy says hello
You can try this leaked gps driver:
http://forum.xda-developers.com/showpost.php?p=13284558&postcount=9138
This is not a flashable zip you have to extract the file.
1. Nandriod Backup
2. Reboot, turn off gps, replace old file in /system/lib/hw/
3. Reboot recovery, wipe cache and dalvik
4. Reboot, turn back on GPS ***OUTSIDE***
5. Report back.
I'll copy everything over in just a little bit. Do you think the driver will only be compatible with MIUI?
EDIT: I should mention that at the moment I'm flashing a fresh version of Fresh 3.5.0.1 to see if the problem persists in all ROMs. Previously I had restored Stock 2.1 and Fresh 3.5.0.1 and the restored ROM had no GPS issues.
EDIT 2: Just confirmed GPS issue is only with Gingerbread ROMs. Brand new install of Fresh 3.5.0.1 picks up GPS signal after reboot.
GreenTea420 said:
I'll copy everything over in just a little bit. Do you think the driver will only be compatible with MIUI?
EDIT: I should mention that at the moment I'm flashing a fresh version of Fresh 3.5.0.1 to see if the problem persists in all ROMs. Previously I had restored Stock 2.1 and Fresh 3.5.0.1 and the restored ROM had no GPS issues.
Click to expand...
Click to collapse
I got the link from a CM7 thread so it will work with that.
[SOLVED] No GPS on reboot for any Gingerbread Roms.
I am pleased to announce, pending a little more testing, that the GPS issue has been fixed! Thanks goes out to JusticeAA for posting the solution.
I have successfully flashed MIUI 1.6.3 and Deck's 1.0 and have no GPS issues upon reboot. Satellites lock on quick!
Barring some more tests, namely testing the duration of the GPS lock, I believe we have found a permanent fix. This fix should also work on CM7 as Deck's is based off of it, although my guess is it will work on all Gingerbread ROMs.
I would like to add a little more detail to JusticeAA's directions. I had some minor difficulty deleting "gps.supersonic.so," the GPS driver, from the on board memory. In order to view the file, I used ES File Explorer. At first, it would not let me delete the file because of insufficient permissions. This was solved by going to menu>settings>root options>root explorer>Choosing your ROM>Mount file system. Then you can delete the file.
Again, thank you very much. Gingerbread is goooood.
GreenTea420 said:
I am pleased to announce, pending a little more testing, that the GPS issue has been fixed! Thanks goes out to JusticeAA for posting the solution.
I have successfully flashed MIUI 1.6.3 and Deck's 1.0 and have no GPS issues upon reboot. Satellites lock on quick!
Barring some more tests, namely testing the duration of the GPS lock, I believe we have found a permanent fix. This fix should also work on CM7 as Deck's is based off of it, although my guess is it will work on all Gingerbread ROMs.
I would like to add a little more detail to JusticeAA's directions. I had some minor difficulty deleting "gps.supersonic.so," the GPS driver, from the on board memory. In order to view the file, I used ES File Explorer. At first, it would not let me delete the file because of insufficient permissions. This was solved by going to menu>settings>root options>root explorer>Choosing your ROM>Mount file system. Then you can delete the file.
Again, thank you very much. Gingerbread is goooood.
Click to expand...
Click to collapse
Any chance of getting a little more detail still yet? I'm not sure exactly how to replace the file.
kforcum said:
Any chance of getting a little more detail still yet? I'm not sure exactly how to replace the file.
Click to expand...
Click to collapse
I also recommend ES File Explorer since it is free and allows up to mount the file system.
1. Copy the new driver file to you SD Card
2. Use ES File Explorer, in settings enable root explorer and choose CM ROM, then mount the file system. It will ask for SU permission and you must allow it.
3. Navigate to /system/lib/hw/ and delete gps.supersonic.so
4. Copy the one from your sd card to that same location
5. Proceed to step 3 from previous post
Forgive my absence. I spent yesterday travelling to New York, so I got to spend a good deal of time testing out the GPS. Keep in mind that I'm running Deck's 1.0 with Tiamat 4.0.4 and the GPS app I was used was Google Navigation.
Phone found GPS satellites fast and consistently. Approximately 15 different tries.
When I had the screen on and the Navigation app open, GPS maintained signal. If I turned off the screen but kept the app on, i.e., using only voice navigation, the app would periodically close. Every thirty minutes or so the app would need to be turned on again even though I did not turn it off. Not sure if this is a problem with Deck's specfically or the new driver. Considering it is not a big problem, I'm only going to keep an eye on it. Perhaps it will be fixed in the future.
Permanent GPS fix here:
http://forum.xda-developers.com/showpost.php?p=14534313&postcount=2478
and you do not need to flash a sense rom.
JusticeAA said:
You can try this leaked gps driver:
http://forum.xda-developers.com/showpost.php?p=13284558&postcount=9138
This is not a flashable zip you have to extract the file.
1. Nandriod Backup
2. Reboot, turn off gps, replace old file in /system/lib/hw/
3. Reboot recovery, wipe cache and dalvik
4. Reboot, turn back on GPS ***OUTSIDE***
5. Report back.
Click to expand...
Click to collapse
Any chance we can get a flashable zip of this? Is that possible? Sorry I'm not programming savvy or I would do it myself. I am on CM7 Nightlies and it is a pain to have to go through this every time I flash a new nightly. Thanks!
Edit: One posted in another thread by Galandy. Here
sitlet said:
If you actually read ANY of the CM7 threads, there are A LOT of people with this issue. Some people can fix it by doing the gpsclrx trick, others can't. IT'S A BUG WITH CM7, IF YOU DON'T LIKE IT, USE ANOTHER ROM.
And PLEASE post this question in the CM7 thread!!!! There is NO NEED to make a new thread for something that has ALREADY BEEN ASKED a hundred times.
Click to expand...
Click to collapse
BLAH................................
aaanadie said:
Permanent GPS fix here:
http://forum.xda-developers.com/showpost.php?p=14534313&postcount=2478
and you do not need to flash a sense rom.
Click to expand...
Click to collapse
Worked for me, even inside. I get a lock in 2-3 seconds if that.
Hello
I have a serious problem , the last 8 days no matter what ROM I install a have the same issue . When I make calls or accept calls the speaker phone is activating automatically on every call , I can change to headphone after the call starts but it starts with speaker phone, I am doing full wipe 1.5 , tried to wipe everything else from recovery but nothing, also Car Home starts every time when rebooting the phone in every ROM and in MIUI it starts every 20 minutes , any help please
This problem started for the first time when i installed MIUI from MrGarak (i am just reporting when the problem started)
Thank you
ClockworkMod has had problems in the past with wiping. Try flashing 4EXT Recovery (see my signature), then wiping everything, and reflashing.
Sent from my Desire HD using Tapatalk
lambomanx1 said:
ClockworkMod has had problems in the past with wiping. Try flashing 4EXT Recovery (see my signature), then wiping everything, and reflashing.
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
can i wipe all partitions (dangerous) or not , what does it wipes
Edit: i installed your recovery but still the same problem , also wiped everything but no luck
I would recommend starting everything from scratch. Back up everything with Titanium Backup (and your texts with your preferred backup program) and wipe everything; data, cache, system. Of course, this won't wipe your SD card
Sent from my Desire HD using Tapatalk
Also having this problem, car home keeps popping up too. I've not found a way around it yet. I've been using mike1986's SuperWipe script to wipe. Tried leedroid, cm7 and android revolution
Sent from my Desire HD using XDA App
mnbrennan said:
Also having this problem, car home keeps popping up too. I've not found a way around it yet. I've been using mike1986's SuperWipe script to wipe. Tried leedroid, cm7 and android revolution
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
Yeah man , car home only starts when rebooting the phone , but speaker phone in every call, i did formatted sd card and did every wipe that recovery has but nothing this might be a virus or something, i've tried mikes superwipe too but nothing
4EXT Recovery and try wiping in that
Sent from my Desire HD using Tapatalk
lambomanx1 said:
4EXT Recovery and try wiping in that
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
Tried that i edited my reply to you but same problem again !
Anyone help me please is there any other wipe tool or something else I still have my problem
Sent from my Desire HD using XDA App
Dialer problem
Hi, I've got this issue too.
At the begin, the problem appeared all the time.
To fix this temporarily, I've unplugged my sim card while my phone is running and plug it immediately after android proposed me to reboot the phone.
So, I've reboot my phone, and now the problem appeared only when I plug my phone to my car kit. When I reboot my phone the problem disappeared.
I think that the problem come from dialer because when the problem appeared, my dialer is different. Look at this picture :
The first one is when there is no problem
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The second one is when there is problem
I think the problem come with Pyramid dialer integration.
Have you got the same dialer then I ?
I had that Phone yes but my problem is different no matter what rom i install or everything that i do still the problem is the same , Car Home starts the first when i boot my phone and every time i reboot it. The phone thinks that i am in Car Mode so it enables the Speaker automatically on every call , this must be broken , tried to clean up the mini usb port even headphone port , no luck at all i am under warranty i will send my phone tomorrow , but thank you very much for the help thanks
I remember in the past that phoneweaver show my phone in car mode all the time. To fix this, I have plugged my phone in my HTC car kit and unplug it. If you know someone with an HTC car kit, you can try it. Hope it can solve your issue.
HELP !!!
i'm having same problem it's not solved even i flashed many roms.when i call someone its always on loud speaker.its a very harassment to me.i've done everything i can.now i'm out of ideas. can anyone help me to solve this?Any help is greatly appreciated.thank you.
possibility to turn off the speaker for good??
I've been having this problem for quite a while now... no amount of cleaning helps!!! Any way to turn off the speaker via software so that this annoying thing stops??
try this
From what I've read this happens because of a defect or oxidation of one pin in the micro usb port...
Well this is not a real fix its just a workaround.
1- install this app from the market: DockNothing
(this will prevent screen from turning on and will stop apps from restarting because of the car mode)
2- Restart the phone and check if car mode doesn't pop up. This only fixes the screen problem... The Loudspeaker will still be on every time you make/receive a call.
3- Download AudioManager: open the app and scroll down to Phone Call Volume and scroll it to 0. This will almost cancel the effects of the loudspeaker. (well its probably a little louder than without loudspeaker on)
let me know if this works for you guys
SOLVED!!!
I had this problem and turns out it was indeed the USB port.
Changed the charging cable quite a few times.. found one that a LITTLE smaller than the original and it worked wonders!! Everything was beautiful again..
This has happened to me twice ( first time 8 months ago second time today) but its because of the 4 and 5 pin in the USB input short circuiting because of dust. So to fix turn off phone get a pin and get all the dust out then it should be sweet.
Sent from my Desire HD using XDA App
Hello,
The problem is my bluetooth will not turn on at all, i slide the toggle to activate it and it stays grey for a few seconds and just turns straghit back off.
I've been a bit if a flashaholic the past weeks and have never noticed the problem untill now, im using the pheonix rom but the problem still occured in Omega v10.
Roms ive flashed recently;
MIUI India
Omegav10
Pheonix(current)
All roms flashed had been done so with a full wipe, im at a loss to what the problem is and considering going back to stock rom to see if that will fix the problem.
Im also using ext2sd mod.
International note 2 n7100, sorry for any typos im in work atm and posting on my break.
Thanks
Yep stock rom is way to go
Sent from my GT-N7100 using xda app-developers app
Well flashed stock rom via odin, as soon as the phone booted back up i was greeted with constant errors of apps crashing, the phone would freeze and the only way to get it back on is to do a battery pull. Bluetooth is also still not working.
I'm at a loss at what the problem could be...
Studix said:
Well flashed stock rom via odin, as soon as the phone booted back up i was greeted with constant errors of apps crashing, the phone would freeze and the only way to get it back on is to do a battery pull. Bluetooth is also still not working.
I'm at a loss at what the problem could be...
Click to expand...
Click to collapse
Answer the following questions sequentially:-
1.What ROM were you on when you found out the bluetooth problem?Stock or Custom?
2.Did you install a custom kernel?
3.What ROM are you on now?
4.What is happening when you click the bleutooth icon from the notification drop down bar?Is it giving an error or just simply refusing to turn on?
1.Custom - Omegav10.
2.Note2core Ext
3.Back to stock, "N7100XXALIJ_N7100O2UALI4_O2U"
4.When i click the bluetooth icon, it goes a darker green like its trying to turn on for a few seconds then back to the off state.
Studix said:
1.Custom - Omegav10.
2.Note2core Ext
3.Back to stock, "N7100XXALIJ_N7100O2UALI4_O2U"
4.When i click the bluetooth icon, it goes a darker green like its trying to turn on for a few seconds then back to the off state.
Click to expand...
Click to collapse
Do this.
1.Flash Omega again this time select Full Wipe option.(do take previous backups before hand and if you havent made an efs backup earlier,choose "Backup efs" in aroma installer)
2.After a good full wipe check again w/o installing any custom kernel.
Im on Omega v10 too and no problems here. One more question, did the problem start when you flashed v10 ? Was your bluetooth working fine before that
?
Doing so now buddy, yeah it started when i flashed v10. I came from MIUI india.
edit//
This is probably unrelated, but recently when i flash a new rom and boot up. perfomance is very choppy/random crashes untill i flash the note2core ext kernel.
Studix said:
Doing so now buddy, yeah it started when i flashed v10. I came from MIUI india.
edit//
This is probably unrelated, but recently when i flash a new rom and boot up. perfomance is very choppy/random crashes untill i flash the note2core ext kernel.
Click to expand...
Click to collapse
That's superstition
Do a Full Wipe before installing a new firmware and you wont have any problems or grave performance issues.
I'll be going off to sleep now.
After flashing v10, if your problem is still not fixed, download this kernel:-http://forum.xda-developers.com/attachment.php?attachmentid=1634178&d=1357854682
and flash via CWM. And see if the problem is solved.
IF it starts working, do hit thanx.
If it does not, ill think of something else tommorow,
Good luck
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Any luck?
Nah no luck at all buddy, I'm running out of ideas as to what it could be. Thanks for the help
Edit//
Just to clarify, I flashed pers/redpill kernels last night to check if the problem would resolve, but I ran into another problem where when the phone would go into sleep mode it won't wake up,
The only kernel that keeps my phone stable is note2core ex. Can this be due to the 1800 clock speeds on note2core? Arghhh this is driving me insane
Clear data and cache and dalvik cache.
Flash stock rom.
Root.
Triangle away.
Flash stock rom.
If the problem persist then take phone to service center
Sent from my GT-N7100 using xda app-developers app
Studix said:
Nah no luck at all buddy, I'm running out of ideas as to what it could be. Thanks for the help
Edit//
Just to clarify, I flashed pers/redpill kernels last night to check if the problem would resolve, but I ran into another problem where when the phone would go into sleep mode it won't wake up,
The only kernel that keeps my phone stable is note2core ex. Can this be due to the 1800 clock speeds on note2core? Arghhh this is driving me insane
Click to expand...
Click to collapse
Sorry
I dont have any idea.
One more thing you can try before giving to Service centre is do a Factory Reset from CWM.
Maybe that would solve.
Hi,
Have you followed this link http://forum.xda-developers.com/showpost.php?p=32273406&postcount=5&nocache=1 yet ?
I had the same problem as you then I followed the link.
My phone is back to normal now.
Hope you can fix your phone too.
Wow exactly the same problem i have and on same roms and kernel and yep also only seems stable on note2core now, i also flashed back to custom and still nothing i have noticed in settings it says bluetooth adress unavailable, is it possible the bluetooth drivers have been wiped ? Any help with this would be great or if you managed to solve the issue , maybe not relevant but my usb also does not work as mass storage or with kies but will connect to odin .
I am having the same problem. I installed a custom rom that messed my phone up big time. I went back to stock and everything works, except for bluetooth. I have gone everywhere I can think of to find a solution to this problem to no avail.
bluetooth and mass storage not working after flash
Hi...guys...I have same problem in my note 2 n7100
And its..if I install stock firmware still not working
But now I installed omega v18 and custom kernel note2core...only this rom and kernel is makeing my device little better but not solve all problem ...so if anyone get solution of this problem so please replay so I can fix it....thanks
Studix said:
1.Custom - Omegav10.
2.Note2core Ext
3.Back to stock, "N7100XXALIJ_N7100O2UALI4_O2U"
4.When i click the bluetooth icon, it goes a darker green like its trying to turn on for a few seconds then back to the off state.
Click to expand...
Click to collapse
..
Hi,,,,friend i have same problem, help me if you solved.....thanks
Hello,
I have been watching and since reading u on this section of the XDA Forums since the start of december 2012 when i got my Xperia S. Excellent phone but after a while the stock ICS did start to annoy me with it's frequent hang ups and it's inability to open up simple programs at times.
So i decided to flash a kernal after updating to .45 ICS stock, specifically the Sspeed V8 kernal. Again it was good and even up until yesterday before i flashed the CM 10.1 it was doing it's job.
I decided to go one step further and i unlocked the bootloader and i firstly installed CWM 6.x.x.x, then backed up my data, wiped cache partition, wiped the dalvik cache then i wiped the phone data, Then i flashed the CM 10.1.zip it installed successfully. It loaded up with out any glitches or hitches.
I then flashed the Gapps.zip V.xxxx2012 for 10.1/4.2.2 it to flashed successfully.
I have been so far impressed how smooth and lag free it is and such a big difference,
i have encountred 3 bugs, mostly the "(insert app name) unexpectedly closed" bug, in this order.
Camera - when turning on the HDR feature of the camera and then trying to take a picture it crashes with the above bug error msg. the first time this happened i tried to open the app again but it would not open and repeatedly the above error kept on appearing. I rebooted the phone and the app starts up with out any problems, BUT again when turning on the HDR feature it will crash again to home screen but i can be started again and used, just with out the HDR feature turned on, the rest of it works fine (i dont use the HDR feature anyways.
Messages - this crashed with the same bug above after some mid-light usage after about 12 hours or so, i simply rebooted the phone and it solved it.
so far no other bugs have been encountered and it is still running smooth.
i wanted to to ask this is a known issue the bugs above?
also my second question is, will a multi-tasking window mod be available or possible for the CM 10.1 like on the samsung phones?
thanks i will try and update this thread with new bugs and fixes.
I apologize in advance if this issue has been covered and corrected but i have looked and been looking for a fix for a long time and can't find one.
Ok, a little history on this issue. I've had the Sprint sgs3 since 2012 and it's been awesome right up until FW 4.4. My issues started when i updated to a stock rooted 4.4 by Cnexus which worked awesome. However, when I began flashing other 4.4 roms and even 5.+ roms upon restoring the stock 4.4 I got endless errors until i rebooted into recovery to factory reset. Then everything went back to normal but i had to reinstall everything.
Fast forward to April 2015. I got a replacement sgs3 after unfortunate screen damage. I rooted it right away and installed philz touch recovery instead of clockworkmod just to try something new. Everything went smoothly and i thought using a different recovery i wouldn't have the endless error issue. Unfortunately I STILL have the issue of endless errors when recovering into my Stock 4.4 rom.
Also the timestamps are WAAAAY off. I'm getting my roms with timestamps from 1970
Any help, or at least an explanation of why this keeps happening , would be immensely appreciated.
alex_camacho said:
I apologize in advance if this issue has been covered and corrected but i have looked and been looking for a fix for a long time and can't find one.
Ok, a little history on this issue. I've had the Sprint sgs3 since 2012 and it's been awesome right up until FW 4.4. My issues started when i updated to a stock rooted 4.4 by Cnexus which worked awesome. However, when I began flashing other 4.4 roms and even 5.+ roms upon restoring the stock 4.4 I got endless errors until i rebooted into recovery to factory reset. Then everything went back to normal but i had to reinstall everything.
Fast forward to April 2015. I got a replacement sgs3 after unfortunate screen damage. I rooted it right away and installed philz touch recovery instead of clockworkmod just to try something new. Everything went smoothly and i thought using a different recovery i wouldn't have the endless error issue. Unfortunately I STILL have the issue of endless errors when recovering into my Stock 4.4 rom.
Also the timestamps are WAAAAY off. I'm getting my roms with timestamps from 1970
Any help, or at least an explanation of why this keeps happening , would be immensely appreciated.
Click to expand...
Click to collapse
Wipe your internal SD when going from Lollipop back to KitKat. The time stamp is normal, you have to turn on the Time Daemon in Philz Settings.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Excellent, thank you. I'm gonna give it a try. However just be clear this doesn't only happen from lollypop roms. This happens from what I call "side grading" switching between 4.4 roms. Oddly however it doesn't happen if I go from ANY other rom to stock 4.3; only stock 4.4 roms.
alex_camacho said:
Excellent, thank you. I'm gonna give it a try. However just be clear this doesn't only happen from lollypop roms. This happens from what I call "side grading" switching between 4.4 roms. Oddly however it doesn't happen if I go from ANY other rom to stock 4.3; only stock 4.4 roms.
Click to expand...
Click to collapse
What you call side grading is a horrible practice and most likely the root of your problems. Wipe data when switching ROMs, if you're gonna do something, do it right... You'll spend more time fixing stuff than it would have to just do a clean install.
Clarification on "side grading"
I understand how flashing roms works. By "side grading" I mean switching roms without upgrading or downgrading ex. Stock 4.4 to custom TW4.4 or even AOSP 4.4.
I wipe EVERYTHING at least 3 times before flashing a new rom or restoring a previous rom.
But thank you for your input every response is helpful.
I just want to figure out why stock TW4.4 is the ONLY rom I restore that does this hot mess.
alex_camacho said:
I understand how flashing roms works. By "side grading" I mean switching roms without upgrading or downgrading ex. Stock 4.4 to custom TW4.4 or even AOSP 4.4.
I wipe EVERYTHING at least 3 times before flashing a new rom or restoring a previous rom.
But thank you for your input every response is helpful.
I just want to figure out why stock TW4.4 is the ONLY rom I restore that does this hot mess.
Click to expand...
Click to collapse
What version of Philz are you using?
Philz touch 6.48.4-d2lte. Latest if I'm not mistaken. I've used clockworkmod, And team win
I've tried so many different ways. Going from rom manager and got the weird timestamp and endless errors. But when I do back up directly from the recovery I get correct timestamp but I still get endless errors. I believe it's a TW4.4 issue cause I don't have these issues with any other rom even custom TW4.4 rom I'm on right now Wicked s5 doesn't give me the issues.
Ok. So I found recently that everything worked relatively well between 4.4 roms. The moment I updated to lollipop and tried to restore to my stock backup, all hell broke loose. No matter how many times i wipe, or install a 4.4 rom and try to restore to stock from a custom 4.4 rom it just simply will not restore my stock rom correctly anymore. I think the only way to get and keep a working stock 4.4 backup is to odin a new stock 4.4FW stay away from lollipop all together.
I've tried everything including several different recoveries all with the same outcome.
I would appreciate some feed back to see if anyone else has or is having this same issue.
and if you've managed to fix the issue.