As the title states. Those using the newest roms do your phones ring as should? Been using and always going back to Baked 6 because every newer rom I try the phone frequently does not ring. To name a few, I tried Hellybean, Slim, Carbon, Baked 8. I have tried every solution that I can find in these forums. I depend on my phone for work so it has to be reliable. Does it not bother others that the phone does not ring as should or does yours work?
I'm on Helly Bean and it rings every time... although I don't get phone calls very often at all, so maybe if I did it would miss a few. This is a common issue unfortunately and I've yet to hear of an easy solution.
Not Ringing Either
My phone doesn't ring either. Hasn't through out the whole time I've been using HellyBean. I've been searching the forums and thus far haven't found a fix. If anybody has the fix thread can you post it here, thank you. Looks like I'll have to look into another rom as suggested in the start post.
it;s probably a ROM that doesn;t get any attention but i have been using JellyBro and the ringing and notifications work fine.
Look here for a fix
http://forum.xda-developers.com/showthread.php?p=42185823
louiehummv said:
Ugh, not again. Well... for what its worth, I found a way to stop losing em.
First, a little background... I discovered that the "media store" app will index ur phone's media after every reboot (as expected), but hangs before committing its findings from the temporary "wal" file to the "internal.db" database (where all ur media locations are stored). Then, when attempting to access the database while configuring ur ringtones/sounds, the media store app craps out and drops it findings altogether. Basically, the wal file disappears and the database file size decreases. So, all we have to do is force the wall file to commit before the media store drops it. Afterwards, the media store app doesn't appear to have a problem maintaining the database... even after rebooting. Definitely a bug with the app; see for urself by observing internal.db in /data/data/com.android.providers.media/databases.
Now, the workaround (ull hafta reassign all ur ringtones/sounds after this... not like they worked anyway)...
1 - Delete the contents of the folder /data/data/com.android.providers.media/databases.
2 - Reboot and wait ~5 min after startup to let the media store reindex all ur media. DO NOT configure any app's ringtones/sounds just yet.
3 - In terminal, enter the following commands. You should see "x | y | z" after the checkpoint command... where x is 0 (database is ok), y is the number of modified pages, and z is the number of pages successfully committed to the database. y and z should be equal and much greater than 0. If the result is not as described, the database is probably screwed up and u were too late. Go back to step 1 and repeat.
$ su
# cd /data/data/com.android.providers.media/databases
# sqlite3 internal.db
> pragma wal_checkpoint(FULL);
> .exit
# exit
$ exit
4 - Trust the workaround and start configuring ur ringtones/sounds now... or reboot again and ensure the media store database stays fixed. I recommend the latter.
5 - 3 sir!
Sent from my SCH-I535 using my wit and brilliance
Click to expand...
Click to collapse
hhp_211 said:
Look here for a fix
Click to expand...
Click to collapse
Can't find "/data/data/com.android.providers.media/databases"
Edit: Found
Hello,
I also suffered this issue, i think the rom you flashed was to blame.
This issue has been long discussed in our Chinese fascinate forum.
I strongly recommend you flash the lastest cm10.
自由自我
hhp_211 said:
Look here for a fix
http://forum.xda-developers.com/showthread.php?p=42185823
Click to expand...
Click to collapse
Tried the workaround. Ringtones lasted longer, but stopped after a couple hours. Tried on latest Helly. Curious which roms it's working for others on.
dukeoid said:
Tried the workaround. Ringtones lasted longer, but stopped after a couple hours. Tried on latest Helly. Curious which roms it's working for others on.
Click to expand...
Click to collapse
well i'm currently on Slim 04/09 build -
previous Slim 3/17;; ParanoidAndroid March Builds;; Baked Bean, 6/7/8;;; HellyBean;;; AOKP PUB;;;
that gets me back all the way to the beginning of the year
I have had working ringtones on ALL of these as my daily use phone...
on my test phone I cant test ringtones cause [ its not activated] but notification tones for things like hangouts, twitter, gmail, etc have ALL worked without fail on every build I've loaded,,, [ which is virtually ""ALL"" the others at one point or another]
but kind of like that work around is saying I always wait after a clean/data wipe about 10 minutes [before setting ringtones] while figuring out my other settings, adding apps and what not, usually give at least 1 more reboot and wait again another 10 minutes then set ringtones,,, but I also have my 2 personal use ones [ringtone = pyxis ,,&,, Notification = cyanping] stored in a file on my sd card [a couple ROMs have not had these and I don't really care to use anything else right now] and always making sure to choose media player/server as the default app if I've wiped media storage settings data,,, [that way I can add them back into the appropriate folders if needed]
I did have this issue way back about August/September of last year running on AOKP builds, but I remember odin to stock, then THS 1/2 build then flashing to an older glitched build before the original partition changes or the later partition changes, and probably flashing new aokp,,, wiping data, etc and I got mine fixed...butt... it could have gone back to me waiting out those initial scanning times plus reboots ~ before ~ setting ringtones/data,,,
then again,,, some peoples fascinates have just given them major issues with this and they have rarely seemed to fix the problem,,, so it could be hardware tolerances and those are just really off on some setting somewhere...???
Good Luck
I really dont feel it is a ROM issue...maybe an Android issue, like the voicemail notification prompt problems [because we dont have LTE and that is coded into jb software now, so the fascinate freaks out when it cant find lte settings...]
.
---------- Post added at 05:48 PM ---------- Previous post was at 05:38 PM ----------
you could try ,,, now that it borked on you,,, clearing out the android.providers.media / data , boot into recovery, wipe dalvik and cache partition, and reboot then wait out the time, reboot and again wait out time,,, then set ringtones,,, and try...don't know what else to say...
Thanks for the suggestions. Will try them.
Related
Hi everyone. It's been two days since the process com.google.process.gapps has started crashing, "stopping unexpectedly" whenever i use the browser on my tab.
Reading the error report, it seems (not 100% sure about that) this is somehow related to the bookmarks sync with Chrome, but i can't find a way to disable this.
Has anyone exprerienced the same issue? Any known solution? Thanks
Go to settings > accounts and sync, click on your account then uncheck everything, then manually sync everything one by one to see what is causing the error.
Then go to manage apps and clear the cache of all the problem apps and re-sync them once you're done. It might take a few tries but it should take care of that error.
I'll try that as soon as possible, thanks!
browser sync was causing this for me
I believe that bookmarks sync no long works with galaxy tab. Google changed something on their end that should have worked fine(it still works on the xoom, transformer, etc.) but since samsung changed a bunch of stuff for no apparent reason, it is now broken. samsung is so stupid sometimes..
So you're basically suggesting that bookmarks sync should stay off to avoid problems like that?
well I don't really know. I never used bookmark sync in the first place. I'm just going by what is said in this article.
http://www.zdnet.com/blog/perlow/br...gle-or-the-oems/17840?tag=mantle_skin;content
It turns out that at some point Google started making some changes to the backend systems that handle Google’s user account data. There’s nothing wrong with them doing this; it happens all the time. In fact, no other Android 3.1 tablets had any issues at all with the changes, and their bookmark sync continued to work without a blip on the radar.
Not Samsung, however... I did some digging around the internet, and it’s become somewhat well-known amongst Android developers that Samsung actually modifies core source code in the Android operating system that handles communicating with Google’s backend data services.
Click to expand...
Click to collapse
Well, that's a pity. I had just started to think it was a useful tool to keep track of unread web pages between work, home and outside...
Let's hope Samsung somehow fixes that.
PS: disabling bookmarks sync actually stops the process from crashing, I think I've solved (if we could really say so...) the issue. Thanks to all!
Thanks, disabling auto sync for browser has stopped the error. Samsung developers need to fix this - I can't auto sync my gmail
What am I missing here?
Ok be prepared, this post may be rather long winded however I will try my best to prevent that. I have a Tmobile G2x I purchased on launch date. Ive not attempted to Root, change roms, or anything of the sort. (as much as I always wanted to, I always felt that my skills were not good enough to attempt these ideas no matter how easy they may seem. I just did not want to be the cause of screwing up my phone that I paid dearly for)
So I have a friend who claims to be the master (of disaster so it turns out) of rooting androids and such. He stops by my house just to hang out and eventualy convinces me to let him root my phone and install CM7. Within a few minutes the phone was rooted (super1click) and was running CM7 release candidate. (I really dont know what all these things truly are but I drilled him for answers once he jacked up my phone and left me with a half-bricked phone) So he installed Rom manager and convinced me to upgrade to the premium version via marketplace so I did. He was then showing me how easy it was to flash new roms at the touch of a few buttons. He put on some other rom which looked like CM7 but claimed to have extra tweaks. It worked fine. A few minutes later he put on some Faux Rom which gave a boot up screen like my old Nexus One did. (Multicolored X) It seemed to work fine as well. Then he said lets check out the nightly CM7 Rom so he put it on. (however I dont think it ever actually put CM7 back on.-still on Faux?) Thats when things got crazy.
Now I get the com.google.process.gapps force close message all the time. He tried to fix it for 4 hours and finally gave up. Here is what I know he/we tried: After searching the internet for hours we tried everyone elses ideas. Clearing calenders cashes, un syncing, etc. We did about 40 factory resets. We have tried to install my backup (which was from BEFORE he even touched my phone) and upon holding both volume rockers and plugging in USB (no battery installed) and it still does nothing. Windows recognizes device but phone screen stays black. Tried Debug mode while doing this as well. If we hold the volume down button and power the little install bar comes on the screen and it does its thing (whatever that is) and goes right back to the way it was. I keep getting the gapps message all the time. After factory reset I cant even type in my gmail address to start the initial setup of the phone. The force close keeps cutting me off. If I type fast, I can sync the account but I cant use market whatsoever. Tried installing Rom manager to re-flash but just sticks at starting download and gapps pops up again.
My son is starting school tomorrow and he has a medical condition. I NEED this phone to communicate with the school nurse via emails and such. As of now I can only text, call, or surf web all while dodging force closes. If ANYONE out there can please help me get my phone back to normal Id greatly appreciate it. Im sure its something easy but as I said before, Im not good at this thing and thats why I never attempted it myself. Your welcome to submit answers here or PM me your phone # if you want to walk me through it on the phone. (I have a landline phone to talk to you on) Thanks in advance for everyones time and Im sorry this ended up being so long.
Hello,
Based on your post, I would suggest that you search your phone's development forum on XDA for a compatable clockwork recovery mod which will install a custom recovery on your phone. The thread will give you instructions on how to do so and how to enter recovery mode.
You can then enter the 'Backup and Restore' part of the recovery and restore your backup manually without using ROM manager. If this doesn't work, I would suggest that you then download the ROM of your choice and install it from the clockwork recovery. Make sure you clear user data and wipe the cache before you install.
Any fix yet? This is really annoying me as I rely on my bookmarks tremendously.
try this:
Open stock browser and under settings choose clear cache and deletehistory
Now that we've released CM7 again for the NT I thought I'd best start up a proper support thread. Pleas keep it as back reports and help.
Please use this thread to post feedback and to ask questions. The Dev thread is for exactly that, development and not support! Please keep the development thread clear of support and feedback posts.
Live support may be available on irc.freenode.net irc channel #nook-tablet-chat, if any of us are around we'll be happy to help but don't bug people if they are busy please. A web version of irc is available here http://webchat.freenode.net?channels=nook-tablet-chat
When posting a bug or issue please use the following format
Which install are you using (Internal or SD):
What version is your CM7 download that you are using (should be alpha final now):
Do you have any mods on your NT (updates or system modifications)
If yes to above what have you installed
Where is this bug (main system or which application):
Can this bug be easily replicated:
If yes to above how can we replicate it to check:
Description of the bug
Any other information we may find useful
Know bugs for Internal version will be in post #2
Known Bugs for SD version will be in post #3
I'm awaiting a Mod cleanup of this thread and all previous bugs up until the new release will be removed from this thread, should knock it back down to about 2 or 3 pages and give me the 2nd and 3rd posts I mention above.
Bugs / Issues from the internal version
Market will not work properly after the update unless you install the GApps (follow link in Dev thread)
Wifi sometimes does no reconnect after sleep, simply tap on the status bar to get notification up and toggle wifi off / on and it should reconnect.
There is currently no Reboot to Recovery option in the power menu, you can do this instead by going to rom manager (make sure it's updated via Market / Play)
Mounts aren't working properly due to a typo on 2 lines in build.prop. update zip to be flashed via CWM available HERE
There is still a possible issue with formatting. A member has said that asking the software to format the /media partition totally wiped his entire device completely removing the partition table creating a paperweight. As has been mentioned many times in both thread about CM7, if any formatting needs to be done please do it from a computer and if in the case of the Media partition that's not possible just delete files instead of formatting. Due to the risk involved we have not yet attempted to recreate this issue on our own devices!
Bugs / Issues from the SD version
System will reboot if you remove the SD card, this is completely normal and you should not remove the SD while device is running from it.
Market will not work properly after the update unless you install the GApps (follow link in Dev thread)
Wifi sometimes does no reconnect after sleep, simply tap on the status bar to get notification up and toggle wifi off / on and it should reconnect.
There is currently no Reboot to Recovery option in the power menu, you can do this instead by going to rom manager (make sure it's updated via Market / Play)
Mounts aren't working properly due to a typo on 2 lines in build.prop. search this thread for how to fix the issue on SD release
There is still a possible issue with formatting. A member has said that asking the software to format the /media partition totally wiped his entire device completely removing the partition table creating a paperweight. As has been mentioned many times in both thread about CM7, if any formatting needs to be done please do it from a computer and if in the case of the Media partition that's not possible just delete files instead of formatting. Due to the risk involved we have not yet attempted to recreate this issue on our own devices!
CelticWebSolutions is one of the prime devs for sure. Integrity and great attitude towards us obnoxious (sometimes) users. Kudos to you sir, and we wait patiently--well, kind of .
Birdsbeaks said:
Just reading the official B&N FAQ for the nook tablet, it indicates "Do NOT turn off your NOOK while it is charging; just allow it to go into sleep mode automatically".
I'd been turning it off to charge also, I think i'll follow their directions and see if it charges faster.
The question i'm quoting is: "How long does it take to fully charge my NOOK?" In the "hardware" category.
Sent from my SAMSUNG-SGH-I997 using Tapatalk
Click to expand...
Click to collapse
Thanks for the link. I'll try to charge it without turning the nook off. if it does charge faster, the question would be, "is there any way for it to charge quickly while off?"
On a side note,I did wonder why the nook would always boot up when I plug in the charger after the nook powered down from low battery.
Thank you sir
Just a quick thanks to Celtic & the rest of the people working on the Nook Tablet... thanks!!! Btw, on one of your forum thread pictures I've noted that your screen is quite smudgy. If you need a screen protector for your nook or any of your newer 8 GB models, let me know, at your service.
And as a side note, I've got absolutely no issues w/ your Alpha CM7 release. No wifi issues, nada. Perhaps this is because my wifi network is password less and only authentication method is via wireless mac filter. Only thing if anything is that sometimes (seldomly) when I swap SD Cards while it's powered on, the device will display the Cyanogen 7 boot animation while booted. A quick rotation from portrait to landscape mode fixes this and allows you to press the home button and "home on out" of this.
*** Btw, if you need a screen protector for any of your nooks, w/o hesitation let me know!! Thanks!
CelticWebSolutions said:
The wifi freezing / disconnecting and needing rebooting is the most well known bug of all. It's posted many times through this thread, it's also stated on the dev thread a few times. I don't mean to sound like many of the other grumpy Devs but please there is a search button! You can search a thread and see every mention of wifi quite easily!
Click to expand...
Click to collapse
I feel ashamed :-(
BangDK said:
I feel ashamed :-(
Click to expand...
Click to collapse
Once isnt something to be ashamed of. You have nine posts. I dont know how much time you have spent on other forums, but searching isnt second nature for young folks new to sites like these.
Now, so long as you do your best not to let it happen again, Im sure no one will castrate you.
Lol, prolly feels a lot like walking into a church with a cowboy hat on.
---------- Post added at 02:35 AM ---------- Previous post was at 02:31 AM ----------
Celtic, I have been thinking, now that you have a new version up, (By the way, you rock) are you going to start a new support thread? This one is VERY long and a little bit daunting, and I am sure that the new rom will bring with it new bugs. This one is almost excessively about video playback and wifi, and the new rom (As I understand) fixes both.
Who would have thought that casually asking if CM7 would be easier and less time consuming could have led to this well polished and very impressive result?
The_Joe said:
Celtic, I have been thinking, now that you have a new version up, (By the way, you rock) are you going to start a new support thread? This one is VERY long and a little bit daunting, and I am sure that the new rom will bring with it new bugs. This one is almost excessively about video playback and wifi, and the new rom (As I understand) fixes both.
Who would have thought that casually asking if CM7 would be easier and less time consuming could have led to this well polished and very impressive result?
Click to expand...
Click to collapse
I agree, I'll sort something later I will probably just clear out this thread leaving 3 posts at the start which I can populate with known issues, tips and that sort of thing.
Watch this space
hi guys, just wanted to say about 2 issues that i saw on my NT.
1. The sleep issue - I've saw that was already posted about 5 pages ago, just wanted to tell i got it too ... after closing the NT the second day could not start it up... had to long press power button a couple of times (didn't knew about shortcut PWR + N button)
2. somehow related to the first one. While playing music, after approx 15 min the sounds stops . I've pressed the Pwr on NT and the playlist is on screen and a song appear to be playing but no sound. I've tried to go to running applications too force kill the app but a get a error message about Force/wait/ ... After that I tried to restart with long press and selected restart/shutdown but it doesn't do anything , again had to long press to shut it down.
Hope this helps, i could try to get some logs if that helps.
Thanks.
sangahm said:
Thanks for responding. So there must be an issue with my configuration. I'll have to mess around with it some more (already deleted cache and uninstalled/reinstalled).
At least I know it can work.
Click to expand...
Click to collapse
Well I finally had to downgrade to v2.6 before it would work correctly. It's not as feature-rich as the latest version, but it does work now.
Just noticed something...doesn't the first post normally have a link to the software being discussed?
I have been running your first release since its inception, and it has IMO, ran fantastic compared to the first release of CM7 for the old Nook Color at this current point. That NC unit and its early CM7 was a great way to learn to troubleshoot bootloops and SOD's!
Anyway, I downloaded your updated CM7 Alpha 12 straight to the tablet and installed. I wanted to try install with only a cache and dalvik wipe first. This went surprisingly well and has been running smooth for several hours now. So far so good!
The first glitch I had on install was the old Market and updated Google play seemed to fight each other with their update. Once the browser was up, I downloaded the new Google Play apk and installed overwritting the old Market directly. Then it took well. After a reboot, all apps were restored using Titanium Backup, and another reboot. I did have one point where I had to pop the SD and reinsert as expected but no prob there.
I want to thank you and all other Team B Devs for this great work. Donation inbound!
movrshakr said:
Just noticed something...doesn't the first post normally have a link to the software being discussed?
Click to expand...
Click to collapse
Good point!
This thread will be almost completely wiped soon when the new internal verison is released, its' getting rather long now and people don't read when it's only a few pages so with 65 pages theres no chance!
When the thread is cleared I'll add in links to the software at the begining too. I'll also be requesting that people post in a set manor. Something like
CM7 build download number (e.g. alpha 12)
Device version (8gb or 16gb)
Install type (sd or internal)
How long have you been running the build?
Short description of bug:
Have you had this bug more than once ?
Can this bug be reproduced on demand, if so how?
Hopefully that will make things easier for everyone ! Although I fully expect many people won't do it like that because they won't have even bothered reading the read to know to do it!
Celtic, do you still plan to release an SD card version also?
movrshakr said:
Celtic, do you still plan to release an SD card version also?
Click to expand...
Click to collapse
Oh dear oh dear.... Do keep up lol
It's already released go look at the dev thread.
Just Flashed Rom
Ok, so this was a bit daunting for me. I've rooted my EVO several times, with several roms and had little difficulty. The NT, however was an horse of a different color.
I first used Nook and Zergy a month or so ago. Never got it working good, but good enough (better than stock B&N)
Then I tried using CMW_SD_flash_and_exe. After much frustration yesterday, I finally figured out that the NT won't boot from the SD card unless the power cable is plugged in. I could finally get into a boot loader program, but kept getting installation aborted when trying to install the ZIP. The CM7_NT_Alpha12_Public1.zip was too big once I made my SD card a boot loader, so I ended up copying this Zip to the tablet's internal memory and installing from there.
I don't know if i'm truly "rooted" in the sense that I can now boot the nook into recovery mode any time, or if I will need to use the SD card to load new ROMs.
My phone is working such that I can reboot into recovery mode any time I want without an SD card. Not sure how I would do that with the NT, or if I'm comparing apples to oranges as it were.
Anyway, all seems to be working, I wiped cache/dalvik cache/data and rebooted. CM7 seems to have loaded, I put in my google account and it's off to the races. After sharing my phones WiFi (thanks to being rooted) my NT is now dl all my installed apps. I think I upgraded to Play from Market so for now I think all is well! Sorry for the long post, but wanted to share my defeats and my success!
BBJon said:
Ok, so this was a bit daunting for me. I've rooted my EVO several times, with several roms and had little difficulty. The NT, however was an horse of a different color.
I first used Nook and Zergy a month or so ago. Never got it working good, but good enough (better than stock B&N)
Then I tried using CMW_SD_flash_and_exe. After much frustration yesterday, I finally figured out that the NT won't boot from the SD card unless the power cable is plugged in. I could finally get into a boot loader program, but kept getting installation aborted when trying to install the ZIP. The CM7_NT_Alpha12_Public1.zip was too big once I made my SD card a boot loader, so I ended up copying this Zip to the tablet's internal memory and installing from there.
I don't know if i'm truly "rooted" in the sense that I can now boot the nook into recovery mode any time, or if I will need to use the SD card to load new ROMs.
My phone is working such that I can reboot into recovery mode any time I want without an SD card. Not sure how I would do that with the NT, or if I'm comparing apples to oranges as it were.
Anyway, all seems to be working, I wiped cache/dalvik cache/data and rebooted. CM7 seems to have loaded, I put in my google account and it's off to the races. After sharing my phones WiFi (thanks to being rooted) my NT is now dl all my installed apps. I think I upgraded to Play from Market so for now I think all is well! Sorry for the long post, but wanted to share my defeats and my success!
Click to expand...
Click to collapse
Get Indirects CWM App. It will perm install CWM so you can get to it by holding down Power + N (without need for SDcard).
Link in a second
BBJon said:
My phone is working such that I can reboot into recovery mode any time I want without an SD card. Not sure how I would do that with the NT, or if I'm comparing apples to oranges as it were.
Click to expand...
Click to collapse
You need to flash CWM internally if you want to be able to get to recovery like you do with your phone.
Check out indirects app
CelticWebSolutions said:
Oh dear oh dear.... Do keep up lol
It's already released go look at the dev thread.
Click to expand...
Click to collapse
OK, sorry about that. I have just been reading THIS thread as I am not a developer, so had missed it. Did not even see it mentioned in here! Largest apologies.
For everyone else, it is here:
http://forum.xda-developers.com/showpost.php?p=22199348&postcount=1
Okay so I took the plunge and installed my first ROM (ICS Collective Base4) among other things with my SGH-I717M (Bell). Everything went very well and here are the issues that despite reading over 500 pages in threads related to these issues, I have not been able to solve them (workarounds, sure). I'm hoping that others can confirm these glitches and whether or not they have been able to remedy them:
-Upon boot, "Unfortunately, the process com.android.phone has stopped". Annoying, but doesn't seem to affect anything. No workaround or solution.
-Baseband "unknown". Tried ODIN flash install AND coming from completely stock phone via CWM flash, neither has remedied this problem. Doesn't seem to affect anything so don't really care.
-Stock calendar application missing - really don't like some of the other calendars, but I can't seem to find the APK file in any other ICS ROM's out there, so I gave up on this. So workaround, no solution.
-Time zone wrong. Workaround is to deselect automatic network management and select the correct timezone. Reverts back to incorrect upon rebooting so apparently only a workaround and no solution.
-Upon booting setCPU max/min speeds are incorrect and you have to open the application for it to correct the speeds. Perhaps it's just the widget that's broken, but for now it's a workaround and I can't seem to figure out a solution. Quandrant benchmarks seem to indicate that if I don't do this, the performance is affected as if the speeds are 1242max/384min and not 1512max/384min.
-Phone freezes on "Power Off", have to hold power button - camera flash goes off and then restarts. Workaround seems to be to use terminal emulator or other applications to reboot, etc. Don't know if there's a solution to this.
-Wallpaper incorrectly zooms - workaround: market applications. No solution that I can find yet.
-Unrelated to the ROM, but V6 Supercharger - I can only get it to report 50% supercharged, even after modifying my services.jar file and following all "step 8" instructions (that was an undertaking!!!). Don't know what's up there, but maybe some of you super-techs have figured it out.
-Only 624MB of RAM available instead of 700MB+ with GB. Haven't heard anything about why this is, so no solution or workaround.
-Doesn't seem to be an ICS keyboard available? I think this can just be installed from the market but I haven't tried it so not sure.
I'm sure there's other things like with Swype, tethering, etc.. etc... that are not working but this is just what I've noticed within the last 8 hours of flashing and trying to set-up and configure. Any comments or helpful suggestions for a n00b like me?
Thank you for any and all feedback. Thank you to all the developers working hard on this fresh release to bring us a solid ROM!
Calender: http://dl.dropbox.com/u/569065/Calendar.apk
Remember, this is a leaked firmware, these bugs are within that leak itself and a few of these issues have been addressed (unknown baseband, etc..) And will be fixed when we release the actual full ROM. this is just the base we shared in the mean time. A few are still present likesome settings not sticking through boot, and the power menu hanging.
Ithink is ur phone acting weird. Only the setcpu speeds not sticking and issue about wallpaper which can easily be fixed by using quicpics are the two issues my phone had. Just dnt use any cpu controller i noticed phone goes to sleep when no cpu controller while when there is cpu controller screen off speed sticks to 384 or 192
Sent from my SAMSUNG-SGH-I717 using xda premium
studacris said:
Remember, this is a leaked firmware, these bugs are within that leak itself and a few of these issues have been addressed (unknown baseband, etc..) And will be fixed when we release the actual full ROM. this is just the base we shared in the mean time. A few are still present likesome settings not sticking through boot, and the power menu hanging.
Click to expand...
Click to collapse
Absolutely. And considering what I've read about previously leaked versions of Android over the years, this one performs like a champ. Can't wait to see what comes out next, but I figured from what I've read this one works well enough to go the distance and install. Thanks again collective!
Felinos11 said:
Ithink is ur phone acting weird. Only the setcpu speeds not sticking and issue about wallpaper which can easily be fixed by using quicpics are the two issues my phone had. Just dnt use any cpu controller i noticed phone goes to sleep when no cpu controller while when there is cpu controller screen off speed sticks to 384 or 192
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
Yeah, just thought I would put my experience out there if it helps anyone or if someone could help me lol. It's very likely some of these are isolated problems, but most of them are problems with the leaked version. I uninstalled setCPU because I think you're right, something likes to nom nom the battery when the screen is off.
Oh and here's something odd which I don't know if anyone else has experienced with ICS or GB, but Terminal Emulator doesn't allow me to type anything unless I capitalize each individual letter. Which of course is useless because it can't accept commands in caps. When I press any key in lowercase it's like I haven't done anything. I had to switch to the pen mode where I scribe each letter and then it puts lowercase letters in for me. Anyone know what's up with this?
This is probably not the best Rom to run for your first flash. I would try one of the official releases in the development thread, unless you are an official tester for The Collective...
Can't wait till they release an official ROM ...
Sent from my SAMSUNG-SGH-I717 using Tapatalk
mk2 love i see im a vr lover Mr helios
Sent from my SAMSUNG-SGH-I717 using XDA
Helios909 said:
Oh and here's something odd which I don't know if anyone else has experienced with ICS or GB, but Terminal Emulator doesn't allow me to type anything unless I capitalize each individual letter. Which of course is useless because it can't accept commands in caps. When I press any key in lowercase it's like I haven't done anything. I had to switch to the pen mode where I scribe each letter and then it puts lowercase letters in for me. Anyone know what's up with this?
Click to expand...
Click to collapse
I had that issue in GB... In ICS it seems to be intermittent- sometimes it just works others it doesn't...
And regarding the baseband, not sure about the Collective rom, but DAGr8's ICS rom displays the modem correctly on my Bell Note.
I also had the timezone issue- strangely enough when I disabled network time and timezone, I also stopped get random slowdowns and ANRs.
Sent from my SAMSUNG-SGH-I717 using XDA
We've got the baseband unknown issue fixed in the full ROM. We just haven't released it. Still working on a couple things before we're comfortable sharing.
Hi, here are my thoughts;
1. Flash a CWM ICS modem(fixed it for me). If you cant find a modem use Dagr8's inital version of the ICS leak, it will successfully flash the modem(unlike the initial collective version(post 501 thread). The main point is to ensure you have the correct baseband(should not say unknown).
2. For now, dont supercharge the ICS leak until you have a stable running OS.
3. After fixing the baseband unknown issue(#1), reflash the collective post 501 ICS rom. It is stable, and the cleanup of the bloat was started already.
4. After installing #3, factory reset your phone.
At this point you should have a bloated, but error free ICS on your computer. Make a CWM backup, install titanium backup, and rip out the junk APK's(widgets, samsung/att garbage). Doing this will provide longer battery life and better performance.
No other wipe scripts are needed.
Factory reset BEFORE flash. The cwm script in the zip itself formats /system and /cache before it writes anything.
And the baseband unknown thing isn't a big deal. Its not that you don't have a modem at all, everything still works you get mobile data, its just the os doesn't properly report it.
if you like what you got, i say sit tight, we're working on the full ROM. You won't be disappointed
studacris said:
No other wipe scripts are needed.
Factory reset BEFORE flash. The cwm script in the zip itself formats /system and /cache before it writes anything.
And the baseband unknown thing isn't a big deal. Its not that you don't have a modem at all, everything still works you get mobile data, its just the os doesn't properly report it.
I say if you like what you got, i say sit tight, we're working on the full ROM. You won't be disappointed
Click to expand...
Click to collapse
Would be cool if you guys could make a minimalistic style rom without all the makeup and cosmetics and focused on performance
We think its cooler to do BOTH
Cause the guys at Samsung must have left their seeing eye dogs at home when it came time to theme
most of us don't usually do minimalistic... once a stable rom gets out you can expect a variety of themes. Sit tight.
studacris said:
We've got the baseband unknown issue fixed in the full ROM. We just haven't released it. Still working on a couple things before we're comfortable sharing.
Click to expand...
Click to collapse
THanks Cris, thats all im waiting for to make the jump to ICS-----is the collectives official - unofficial ics dev thread.
Studacris said:
"We think its cooler to do BOTH
Cause the guys at Samsung must have left their seeing eye dogs at home when it came time to theme"
LOVE IT!... and CAN'T WAIT! Thank you for all you do... and have a few beers on me. PayPal confirmation number: 6RE28092GB801952P
fishing.laguna.madre
NoteI717
Powered by The Unofficial
Thanked you in the ROM threads, but again, very appreciated. Thank you.
Sit tight. what we got cooking is gonna be tasty
Same experience here
well done guys excellent base.... Having the same experiences as helios909...
Really looking forward to the the fully packaged version. Not experiencing problems with cpu speed set on boot.
Face unlock not work properly yet. Device hangs on reboot as reported. Auto update time bug exists. Baseband version unknown. Phone crashes on initial boot. But recovers.
New voice type engine is amazing. As demonstrated here.
ok, for some reason, thought build.prop q's were relevant to the kernel...
anyway, I edited build.prop in /system with RootExplorer's text editor. changed the value for wifi.supplicant_scan_interval from 30 to 120. no extra lines or spaces, etc- just changed the number, saved, then rebooted. it took an obscene amount of time to boot up and the device stopped going into deep sleep after a short while. I installed better battery stats to see what was wrong and the app indicated mmc_delayed_work under kernel or partial wakelocks (i forget which). I restored the original build.prop and the device worked like normal.
Is this a bug or is ICS/JB different enough from GB that you have to go through alternate means to change build.prop (eg flashing an update script from CWM, or something similar)?
I've tried this twice already and gotten similar results and the method by which I edited the build.prop was exactly the same as I used to edit it on GB without issue.
another thread I checked out in the S II dev thread indicated that this is possible- editing build.prop (wifi scan at least, on top of a few others parameters)- w/o issue, so....yeah.
alljokingaside said:
ok, for some reason, thought build.prop q's were relevant to the kernel...
anyway, I edited build.prop in /system with RootExplorer's text editor. changed the value for wifi.supplicant_scan_interval from 30 to 120. no extra lines or spaces, etc- just changed the number, saved, then rebooted. it took an obscene amount of time to boot up and the device stopped going into deep sleep after a short while. I installed better battery stats to see what was wrong and the app indicated mmc_delayed_work under kernel or partial wakelocks (i forget which). I restored the original build.prop and the device worked like normal.
Is this a bug or is ICS/JB different enough from GB that you have to go through alternate means to change build.prop (eg flashing an update script from CWM, or something similar)?
I've tried this twice already and gotten similar results and the method by which I edited the build.prop was exactly the same as I used to edit it on GB without issue.
another thread I checked out in the S II dev thread indicated that this is possible- editing build.prop (wifi scan at least, on top of a few others parameters)- w/o issue, so....yeah.
Click to expand...
Click to collapse
I have no idea why that would happen, but I guarantee you the interval is fine where it is. I've left my player on with wi-fi over a week.
Mevordel said:
I have no idea why that would happen, but I guarantee you the interval is fine where it is. I've left my player on with wi-fi over a week.
Click to expand...
Click to collapse
I'm recording atm but problem isn't replicating. go figure; well, if it does, I'll post a logcat. if not, good for me since I forget to turn the wifi off most of the time and especially in places with no open wifi. anyway, I was posting this in case someone else did come across a similar problem and had a solution since my searches led nowhere (searching for anything mmc_delayed_work related comes up with little useful info/apparently a lot of once-valid GB tweaks are "busted"/not in ICS code base)
whether or not the scan interval isn't exactly the point, why I'm pursuing it; it's the specific point atm, but the general point is device ownership- tailoring your device to your heart's desire; complete ownership. that's the premise behind this whole site as I'm sure everyone here is aware. if I did something to mess it up along the way, great. but if it is a bug or something with ICS code base, it's be nice to know. a lot of folk like messing with build.prop so it'd be nice to know what can or cannot be messed with.
atm, it does look like I messed something up when editing and saving- perhaps I added a space or line where it shouldn't've been- since the device is sleeping as it should, again, if I find something, I'll post the logcat.
thanks for the re:
alljokingaside said:
I'm recording atm but problem isn't replicating. go figure; well, if it does, I'll post a logcat. if not, good for me since I forget to turn the wifi off most of the time and especially in places with no open wifi. anyway, I was posting this in case someone else did come across a similar problem and had a solution since my searches led nowhere (searching for anything mmc_delayed_work related comes up with little useful info/apparently a lot of once-valid GB tweaks are "busted"/not in ICS code base)
whether or not the scan interval isn't exactly the point, why I'm pursuing it; it's the specific point atm, but the general point is device ownership- tailoring your device to your heart's desire; complete ownership. that's the premise behind this whole site as I'm sure everyone here is aware. if I did something to mess it up along the way, great. but if it is a bug or something with ICS code base, it's be nice to know. a lot of folk like messing with build.prop so it'd be nice to know what can or cannot be messed with.
atm, it does look like I messed something up when editing and saving- perhaps I added a space or line where it shouldn't've been- since the device is sleeping as it should, again, if I find something, I'll post the logcat.
thanks for the re:
Click to expand...
Click to collapse
I understand.
Thinking about it, mmc_delayed_work seems like it's tryng to catch up the SDcard or something. Did you reboot cleanly? That may be the issue.
Mevordel said:
I understand.
Thinking about it, mmc_delayed_work seems like it's tryng to catch up the SDcard or something. Did you reboot cleanly? That may be the issue.
Click to expand...
Click to collapse
No clue. what do you mean by "reboot cleanly"? if by that you mean, did I reboot using the reboot option in the power menu, then yes. always.
After restoring a backup and re-editing build.prop, sleep worked like gamebusters. Except, bluetooth auto-toggled on ("bluetooth is turning on"). After rebooting, it was stuck on the boot animation screen for a few minutes. A reboot after that pretty much boot looped it. I restored my backup afterwards...
Looking in the logcat (after editing), I noticed a ton of errors and permission denials.... Since I don't have much expertise here, I can't say for sure that they're normal but they seem to be abnormal. Wayyy more than I remember seeing when I browsed through before on a "clean" boot. But again, with the lack of expertise (or any functional knowledge for that matter)
==
Now, after having restored the backup before making the edits and rebooting, it seems to be stuck in a bootloop....huh. ok, after rebooting it 2x, it finally seems to have booted up "normally." Both before restoring (w/ edits and BT error) and after restoring (w/o build.prop edits), it's taking a lot longer to boot up than it used to....guesstimating 3-4 minutes. When it boots up, I get/got: "process system isn't responding" (both before and after restores now) and something about alarm error.
I've attached logcats of both pre- and post-event, if you're curious. As to "solving" this,I'm just gonna re-flash the PA ROM and wipe caches to get rid of these problems. ergh. device meets my foot against the wall is next on the checklist.
thanks again. I'd like to say, Stay classy, San Diego, but we all know San Diego and its class
I did the whole manual update to Lollipop, unfortunately, my phone keeps searching for GPS when I use apps that need it.
The problem is I like to use a boating app, and I go far enough offshore that I do not get data. Btw, I get this issue with any app that needs GPS, including Pokemon Go!
After searching online, it appears to be a bug in Lollipop itself.
Either downgrade, of go to Marshmallow if I can find a decent daily driver.
Anyone else have similar issue?
leroadrunner said:
I did the whole manual update to Lollipop, unfortunately, my phone keeps searching for GPS when I use apps that need it.
The problem is I like to use a boating app, and I go far enough offshore that I do not get data. Btw, I get this issue with any app that needs GPS, including Pokemon Go!
After searching online, it appears to be a bug in Lollipop itself.
Either downgrade, of go to Marshmallow if I can find a decent daily driver.
Anyone else have similar issue?
Click to expand...
Click to collapse
My Mate2 did the same thing...mostly after google updated a bunch of stuff. Just started doing it about a month or so ago.
Haven't touched it (all stock) in about a week. Got my new Mate8 about 4 days ago
"Searching for GPS" bug, might need to downgrade to KitKat
Try this:
http://forum.xda-developers.com/showthread.php?p=68572626
See post 35!
More details of my experience in that thread. Wife just pre-ordered an iPhone 7, probably out of pity, for me. One day I showed her my Google Maps and set it to drive home. No sound, no directions, but it quickly discerned origin and route home, when we got home it said "you have arrived," but the map, even though the pointer updated position throughout the drive, still showed the route line from the origin!
Sent from my iPad using Tapatalk
I've never had this issue on any ROM
Found a workaround
I was experiencing exactly the same issue! Not only that but it seems like this issue has popped up on reddit and latest amazon reviews too. Seems to have started occurring after July of this year for many people. I haven't determined the root cause, but it seems like it's affecting too many people to be a hardware issue. Some things I tried that DIDN'T work:
* Flashed latest Cyanogen snapshot, although I like it a lot more than stock
* Tweaked the /system/etc/gps.conf file for my region
Finally I found that my phone time significantly drifted off atomic time, noticed it could be a whole second off. After reading online about GPS technology, it seems having an accurate client atomic time should improve GPS performance. I used an app called ClockSync (with root is easier) to make sure my time was accurate and turned off syncing time with cell tower. It worked!! Using a GPS testing app (GPS Status & Toolbox) I can lock on to my position reliably in < 10 seconds. This is still running on Cyanogen.
I'm in love with this phone, so happy I don't have to buy a new one.
fenwaysnow said:
I was experiencing exactly the same issue! Not only that but it seems like this issue has popped up on reddit and latest amazon reviews too. Seems to have started occurring after July of this year for many people. I haven't determined the root cause, but it seems like it's affecting too many people to be a hardware issue. Some things I tried that DIDN'T work:
* Flashed latest Cyanogen snapshot, although I like it a lot more than stock
* Tweaked the /system/etc/gps.conf file for my region
Finally I found that my phone time significantly drifted off atomic time, noticed it could be a whole second off. After reading online about GPS technology, it seems having an accurate client atomic time should improve GPS performance. I used an app called ClockSync (with root is easier) to make sure my time was accurate and turned off syncing time with cell tower. It worked!! Using a GPS testing app (GPS Status & Toolbox) I can lock on to my position reliably in < 10 seconds. This is still running on Cyanogen.
I'm in love with this phone, so happy I don't have to buy a new one.
Click to expand...
Click to collapse
I tried to install CM13. I failed miserably. Then I started by playing the Pokémon Go game and observing the erratic character movement. Then played with the GPS settings. Turning off High Accuracy and leaving on Device Only still is working, except inside structures that block GPS signal. Tried High Accuracy while visiting San Francisco this last weekend and started having issues there, so back to Device Only for me.
Thank you for sharing what has worked for you!!!!
Sent from my MT2L03 using Tapatalk
I found the latest Cyanogen snapshot I tried (cm-13.0-20160823-SNAPSHOT-ZNH5YAO0M5-mt2) too unstable. I started to experience random reboots every day, even while using Google maps turn-by-turn navigation. Restored back to official lollipop build (MT2-L03C00B322) from my backup (that was factory restored before backing up). Now it's suddenly working without any workarounds! I have no idea why it's working now. If you are considering dumping your phone for a new one, you could try a factory reset first to make sure it's not a hardware issue. :/
---------- Post added at 05:26 AM ---------- Previous post was at 05:19 AM ----------
jzchen said:
I tried to install CM13. I failed miserably.
Click to expand...
Click to collapse
It was definitely not straightforward, I ran into several issues. First, TWRP recovery was complaining about invalid file system format so I switched to Cyanogen recovery to flash system. Second, I was getting constant Google services has crashed messages. Found out I needed to install it right after, before rebooting first. Third, I was stuck in boot-loop during Cyanogen startup. A hard reset finally fixed it.
fenwaysnow said:
I found the latest Cyanogen snapshot I tried (cm-13.0-20160823-SNAPSHOT-ZNH5YAO0M5-mt2) too unstable. I started to experience random reboots every day, even while using Google maps turn-by-turn navigation. Restored back to official lollipop build (MT2-L03C00B322) from my backup (that was factory restored before backing up). Now it's suddenly working without any workarounds! I have no idea why it's working now. If you are considering dumping your phone for a new one, you could try a factory reset first to make sure it's not a hardware issue. :/
---------- Post added at 05:26 AM ---------- Previous post was at 05:19 AM ----------
It was definitely not straightforward, I ran into several issues. First, TWRP recovery was complaining about invalid file system format so I switched to Cyanogen recovery to flash system. Second, I was getting constant Google services has crashed messages. Found out I needed to install it right after, before rebooting first. Third, I was stuck in boot-loop during Cyanogen startup. A hard reset finally fixed it.
Click to expand...
Click to collapse
That's a lot to deal with!!!
As of yesterday I am back to High Accuracy, and just as you note everything seems fine, particularly with regards to GPS.
I guess if I want to have Android 7, I'll save up for a phone that comes with it, unless I learn how to manually do it myself. (I was once a CECS major, about 16 years ago...)
Thank you again for sharing your experience! I hope we can all go back to enjoying our exceptionally large screens....
Sent from my MT2L03 using Tapatalk