This fixed both my Camera and Google Talk that stopped working in Sense ROMS om 08-31-11.
FIX:
1. Go to Settings and select Date & Time.
2. Un check Automatic
3. Change the time to 08-01-11
4. Go and open your camera (it should work now)
5. Now you can go back and check Automatic in the Time & Date Setting
yes,I see log:
Code:
I/CameraService( 3944): CameraService started (pid=3944)
I/OlaEngine( 3944): [Ola_Engine_Create:75] engine build info [ name ] : htc
I/OlaEngine( 3944): [Ola_Engine_Create:79] engine build info [ date ] : 2011-05-13 18:34:22
I/OlaEngine( 3944): [Ola_Engine_Create:83] engine build info [ version ] : __bulid_revision_171__
E/OlaEngine( 3944): [Ola_Engine_Create:91] This library will be expired at 2011/8/31.
D/OLAWORK ( 3944): create OlaEngine failed -32
Have time to lock this file:/system/lib/libcameraservice.so
However, I found that you can use incredible_s (s710d) file to replace.
I put a file in here, from RUU_Vivo_W_CT_Gingerbread_S_HTCCN_CHS_CT_2.13.1401.4_Radio_1_01_50_0701_NV_MFG_CT_2.22_release_202988_signed extraction.
This file is not the time lock. 2.07.605.0 ~ 2.11.605.0 stock rom application.
View attachment libcameraservice.zip
I TAKE NO CREDIT FOR THIS. Thanks to the help of mpwt51 on the Android Central Forums and Snow02 on the BAMF Forums, this issues is now resolved.
Looks like Verizon put some sort of time bomb into these apps. Simply changing the date back wil resolve this issue. Of course that is no way to actually resolve it. Flash this http://db.tt/Bcltlcr instead and it should solve these two issues.
Source: BAMF via Android Central Forums
You guys are freaking geniuses. I have been looking for a solution for this for over 4 hours and found nothing. Figures, the minute I check XDA there is a solution, right there.
Kalandros said:
You guys are freaking geniuses. I have been looking for a solution for this for over 4 hours and found nothing. Figures, the minute I check XDA there is a solution, right there.
Click to expand...
Click to collapse
That wasn't the case last night when I originally posted the issue and 4 guys over at TheMikMik were flashing like mad men, including myself, to try to figure out what sickness was ailing our beloved devices! Glad there's a cure though.
not rooted
This can't be flashed if not rooted, correct? I'm on GB 2.11 not rooted
It worked on GB 2.11 1nd 2.10 not rooted, Thank you very much!
Mig1234 said:
This can't be flashed if not rooted, correct? I'm on GB 2.11 not rooted
Click to expand...
Click to collapse
I seriously doubt it.
I've tried this and can confirm it works like a charm.
8-1-11?
Hey guys,
I'm amazed that someone actually figured out that the date is causing this problem. Seems lame that there's this code in the system with expiration dates. WTH Verizon!
Thank you for this fix its a life saver
Sent from my ADR6400L using xda premium
Does this fix the front camera issue on google talk on gingerbread?
wj_johnson said:
Does this fix the front camera issue on google talk on gingerbread?
Click to expand...
Click to collapse
No idea what you're talking about.
Google talk video on gingerbread (thunderbolt) will not use the front facing camera
wj_johnson said:
Google talk video on gingerbread (thunderbolt) will not use the front facing camera
Click to expand...
Click to collapse
That's always worked fine for me. You're ROM is the issue.
UndergroundWire said:
I TAKE NO CREDIT FOR THIS. Thanks to the help of mpwt51 on the Android Central Forums and Snow02 on the BAMF Forums, this issues is now resolved.
Looks like Verizon put some sort of time bomb into these apps. Simply changing the date back wil resolve this issue. Of course that is no way to actually resolve it. Flash this (nooblinkremoved) instead and it should solve these two issues.....
Click to expand...
Click to collapse
I'm not really sure why, but this only fixes my google talk, but not my camera. I've tried several of the camera fix .zip files and the most common result, across multiple ROMs is that google talk gets fixed, but the camera stays black, acting like it's working, but there are no buttons and the screen is black.
I first tried this on BAMF Forever 1.10 and acheived that result. Then, I tried it on Liquid Vigorsense v1.1 (can't find v1.2 on Rom Manager and the rootzWiki link doesn't work b/c it was on multiupload) and had the same problem. Eventually, I flashed each ROM again, wiping data, cache, dalvik and batter stats multiple times and when I wen't back in to BAMF Forever, it worked. B/C I liked sense 3.5, I wanted to go back to Liquid VS, so I tried flashing back to it and sure enough, both gtalk and the camera worked.
At that point, the only thing I wanted on a sense 3.5 ROM to make my life complete was the keyboard with arrows, so I tried a few keyboard w/arrows zips and none of them worked, so I tried flashing one of the Infected ROMS (Airborne). I found a keyboard w/arrows zip within their lists, so I flashed it and got the keyboard to work, but then the camera was gone. I found a camera fix that they had and it didn't work initially, but after a few re-flashes, everything worked.
Then I got greedy and wanted my sense world clock/widget, so before flashing back to one of my backups from liquid vs, I backed up the Infected ROM and when it booted back up, gtalk and camera were broken again. I tried flashing all of my backups from liquid and bamf forever that had a working camera and the camera/gtalk were broken on them as well.
So, I've flashed Bamf SOAB and I used the keyboard zip for bamf SOAB (worked!) and the camera fix mentioned in this thread and no dice. gtalk works, but still, just a black screen camera. I've wiped and flashed and wiped and flashed each, liquid and SOAB couple of times each (each time, wiping multiple times).
I've got a hilarious 1 year old girl and really want to get back to documenting her life in the candid fashion she so often provides, but I need my camera to be fixed.
I haven't seen many posts on this topic across most of the forums/sites after Septemer, 2011, so it makes me feel like everyone else got this to work. I didn't have the problem in September. It never hit me until I had to swap out my TBolt due to the right side of my screen crapping out. When the new one came from VZW, the camera/gtalk problem happened.
Any help or ideas? (sorry for writing a book)
Much thanks in advance.
Related
Just wondering if anyone has anything (good/bad) to report about the OTA update. Figure this would be a good place to post those issues for the people who are still hesitant about updating. I have the 2.1 v3 non-root and have yet to update. Thanks.
Having issues with 2.1 I can't find ANY HTC widgets. Tried to reload the digital clock with the weather app at the bottom and realized the phone doesn't have any HTC widgets, only shows the android native widgets. Anybody else having this problem, got any advice how to solve this?
I just manually updated to 2.1 (Official) and now my weather app doesn't work. Widgets are ok, just opening the app causes a force close. Any way to fix this? Might call customer support tomorrow and tell them the OTA got to me and it won't work now.
From what I've seen around a reboot might fix that if you haven't tried that already
-------------------------------------
Sent via the XDA Tapatalk App
Haha thanks, but I've tried it several times. Also, the recovery doesn't work with the official update.zip. I'm assuming that it's because the versions are the same, but if it says RECOVERY then I'm wondering why it won't RECOVER like I'm trying to do now. Any other ways to reinstall the OTA?
I manually updated my wife's around 10 am today and about 3 hours ago, she started havin no sound issues. couldnt hear through the earpiece, phone vibrates instead of rings, speaker will not play volume. I have tried everything. Making sure all settings are in place like volume TTY. Reboot fixes it for about five minutes then right back to the same thing. Hard resetting now. If it still does it I'll probably take it in and demand a new one i guess...lol
EDIT: Should I have to reprogram on a hard reset after this update? Hmm somethings not right about that...
Ive had no problems with the OTA. I went from stock 1.5 to OTA 2.1
It seems that people with leaked 2.1 v3 won't get the ota. My friend has an Eris with 1.5 and just got
it but I didn't.
-------------------------------------
Sent via the XDA Tapatalk App
I don't think anyone who is running any leaked version is getting an update right now. There is an issue with the hboot versions it seems.
Don't worry, two things have been confirmed.
First the OTA will not work with the leaked ROMs installed.
Second, the OTA is exactly the same as the 2.1 leak v3.
This was confirmed on Android forum by someone that took the time to compare every single file and CRC the binaries. The only difference was that the leaked ROMs use a different bootloader to install as they did and the actual OS and apps are exactly the same so if you got leak v3 you got the OTA.
The OTA won't install because you are already running it.
if you have rooted 2.1 (test keys) and you downgrade to back to 1.5 any one if this will allow you to get the OTA update? i installed the rooted 2.1 (test keys) but never installed a custom ROM (the second half of the directions on XDA forum) and I still haven't received the update. but I was thinking of downgrading to 1.5 to see if i can get the update.
anyone having problems with live wallpapers on 2.1? or was this not included with the 2.1 for eris?
Jrbourque said:
anyone having problems with live wallpapers on 2.1? or was this not included with the 2.1 for eris?
Click to expand...
Click to collapse
Unfortunately it wasn't included.
just found out about 2.1 this morning...
I'm a verizon rep for an authorized premium retailer, and one of my customers came up to me today with her eris complaining about all her contacts being gone and her album not being there... her exact words: "What happened??? I clicked the update thingy and now half my ****'s gone!" Personally I laughed slightly, then checked the software version, found it updated to 2.1 and figured the deal. Her sound is working fine, she now has a couple more widgets she wont know how to operate, and albums is now "photos", and contacts is now "People". also required a resync to get her contacts back, but now she's golden.
-vzw rep in MS
turboguy said:
Unfortunately it wasn't included.
Click to expand...
Click to collapse
thanks for the info
Quick question about TaskBar (process killer) widget. Anybody know how to program it to ignore certain processes? Like sense... I tried using it but it killed sense every time. Along with mail and the weather process, which I don't care so much about, waiting for sense to reboot every time is a serious pita though...
I previously had 1.5 stock eris. I downloaded the official OTA zip and manually installed it. I had a few issues at first.
1. I had Spare Parts installed and had set my End key to first goto home screen and then lock. 2.1 did not like that setting and so my end key wouldn't do anything except turn it on from sleep and end a call until I changed the setting to just lock the phone.
2. Couple apps wanted to be updated to a new version after installing 2.1 before they would work.
3. Here is my unresolved issue - All my apps that I had installed before 2.1 no longer have write access to my SD card.
For example Astro File Manager showed my permissions on /sdcard as dr-. Reloading the card, rebooting, etc did not fix the issue. Uninstalling and reinstalling seems to have fixed the issue.
Why did this happen in the first place and is there an easier fix than uninstalling/reinstalling all my apps?
I've had the same disappearing HTC widget issue as was mentioned earlier, but a reboot (with a battery pull) didnt fix the problem. Is a hard reset my only option?
my girlfriend installed the OTA and now only the stock ringtones work when receiving a call- she set up custom ringtones for a few contacts, but if they call, the default ringtone rings.
I was running the leaked 2.1 eris rom on a MyTouch 3g and had the same issue, so i'm guessing it's not an easy fix. anyone else seeing this?
2.1 OTA back to 1.5
Hi everyone, I had many problems with 2.1 I manually installed 2.1 OTA from 1.5. everything went smooth, once running first thing i notice I click on the HTC clock weather, and it force closes, ok great, found a trick to delete the cache for weather provider, boom works, then i find out I do infact have the 50% time without signal issue, well I figured it wasn't too big of a deal, but after basically cutting my time in half going from 2 days no charge, to barely making one day, and I've heard that it would just take time as it did when first getting the phone.. which makes sense as it was the case with 1.5, week later not much improvement, so..
I would just like to comment on my experience. It went so smooth, it was in-fact easier to set back to 1.5 than it was to initially, manual install the OTA 2.1... I downloaded the MR2 file, unzipped the file, went through the computer on screen step-by-step process, Took less than 10 minutes, and of coarse as soon as turning the phone back on with 1.5 I see the OTA msg. I'm, just praying it doesn't get too annoying..
i just noticed that the "My Apps" button in the market now looks like a phone and says "sprint"
If i click on it it doesn't take me to my apps.
Anyone else having this problem?
That's normal for this build. If you click on your Menu, you'll find My Apps there.
Thanks you were right
Best ROM on XDA
+1
I'm really enjoying this ROM. The speed of the machine is phenomenal.
Love the Rom ad well but can't seem to get the market updated or to show all apps. Any thoughts?
I've tried market enabled to no avail.
Issue with ROM or with G-Tab?
I've noticed that if I let the g-tab go to sleep, I'm having to reboot it get it to wake up.
Is anyone else having this issue? I've had my tablet since x-mas, but have nto used it much. It sat in a desk drawer for about 2 months, and I'm just now getting into using it.
Daniel
I have this issue with every rom ive tried on my gtab. So now I pretty much just install clem's kernel everytime. Plus it gives me CIFS so I can stream media from my windows pc .
http://forum.xda-developers.com/showthread.php?t=895825
boots77 said:
Love the Rom ad well but can't seem to get the market updated or to show all apps. Any thoughts?
I've tried market enabled to no avail.
Click to expand...
Click to collapse
Yeah, again it's just the build. There are a ton of hacks that will get you more of the market, but I doubt you'll ever get "everything". Considering that the GTab wasn't blessed by Google, we're lucky to have the devs here to get the market at all.
IndysComputerGeek said:
I've noticed that if I let the g-tab go to sleep, I'm having to reboot it get it to wake up.
Is anyone else having this issue? I've had my tablet since x-mas, but have nto used it much. It sat in a desk drawer for about 2 months, and I'm just now getting into using it.
Daniel
Click to expand...
Click to collapse
Another issue with this ROM. Some have fixed it by going to Clemsyn's kernel, others to Pershoot's and still others by using CPU Master Free. Personally, I just set my tab's Screen Timeout to Never. What can I say...I like simple.
jccrumpler said:
Best ROM on XDA
Click to expand...
Click to collapse
Been getting over 2500 on quadrant consistently with a high of 2612. It's the fastest my tab has run so far.
jccrumpler said:
Best ROM on XDA
Click to expand...
Click to collapse
I agree. The only problems I see with it are no news and weather widget like on tnt, and the horrible photo album (I think it's from stock?)
Fireware
This may be a stupid question, so I am sorry if it is, but Calkulins v1.1 says it is "Based on rooted 2.2 / FRF91 - TnT 3991"...
so can you run it on the 1.1-3588 firmware, or will that brick?
Again, sorry for my ignorance...
Thanks!
ROM's and Firmware are the same thing. If you're asking whether you can use ClockworkMod or standard recovery, the answer is yes. Calkulin's ROM is a hybrid using the newer 3991 build for features but the older bootloader and recovery. It shouldn't cause you any trouble loading it over 3588.
Thanks! Sorry, I confused the firmware with bootloader, thanks for straightening that out!
No problem. Just want to make sure that I understand the question correctly. Happy modding!
All Done!
Woot!! I will say, I bought this on the woot! deal... and although I consider myself very computer savvy, I have never rooted/hijacked/whatever a device before...
Happily this was super easy! I wanted use the stock ROM for a bit to get familiar with it, but I just couldn't stand how slow/unresponsive/just crappy it was!!
So I jumped the gun and started in... luckily I did a lot of reading first!!
Loaded up Clockworkmod - and made a backup first!! lol
Used clockworkmod to install Calkulins ROM---OMG is it fast!!
The found that I was having the sleep-death issue... so I loaded up Clemsyns Kernel Too!!
Not a single hiccup! Even for a noob- this is super easy! Just follow all the great advice on the XDA forums (and don't skip steps!) and you can't screw it up.
Thanks to all the great people on here, for the hard work, and patience... I love seen good communities like this!
DeadEnd
Which version of Clemsyns is recommended?
Hi,
clakulins ROM is my prefered ROM so far
But, it needs some issues to be addressed to make it my daily driver.
1- sleep-to-death
I know we can use another kernel to fix this (so I keep this fix for later if everything else can work)
2- Settings/Family accounts/add member
This FC every single time. I definitly need this functionality. My Gtab being a family device....
3- Photos is horrible as previosuly pointed out in this thread. I want a centralized place for all my photos, or at least for local storage + picasa. With this gallery, we can only access picasa public albums. What about my own account !!!
4- Photos started to display pictures roatated one quarter to the left. It doesnt let me re-rotate them back to original. It does that for evey single picture, i cant fix this. Photos is now unusable
I tried a few Photos gallery apps from the market (6-7 so far). None of them works to my liking.
I just want somethings simple that get access to all my pics.
5- Cant play videos anymore. Not even the sample 'car' and 'king kong' that came with the Gtab.
If I can fix all of the above, calkulin will be my only and permanent ROM.
(ps items 4 and 5 were previously working ok in this ROM, this started yesterday)
Also, another things that is on my whish list:
- Have bluetooth HID
I have this blutooth keyboard collecting dust on the used parts shelve that I would like to use with the Gtab
thank you calkulin for all,
So, I decided to install clemsyn kernel to fix this sleep-death problem.
No problem installing, everything went well.
But now instead of comlaining that it cant play videos, it just FC on every videos I try to play.
I feel a complete reinstall will be necessary.
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.
Alright, this is a little embarrassing. A friend asked me to root, back up and put ICS on his SII. I own a ZTE Blade and am at least a seasoned observer of the MoDaCo Blade community, so I figured it wouldn't be any trouble. Rooting was easy as anything, with su and the SII variant of ROM manager working fine. Backing up took ages but was broadly successful. I then flashed the 08/04 build of HyDrOG3N, following the flash order to the letter. Launcher operated smoothly and the few functions I tried were all OK. I got a couple of bizarre force-close warnings but ignored them (Exchange services and Camera I think). Then I decided, foolishly it turned out, to flash ICS gapps and the Phenomenal 4.0 kernel Extreme kernel in recovery. This was when I also realised the phone had only 10% charge, judging by the amount of time since I'd last seen the battery meter. So when I selected 'reboot', it didn't seem to do anything apart from keep the screen on. I left it for a while, then realised it wasn't going anywhere so I took out the battery, replaced it, booted back into recovery and flashed HyDrOG3N & ICS gapps again. Everything was fine, so I restored his apps, synced contacts, restored SMSs and began customisation. Until I realised that his camera photos had disappeared (not a huge issue, backed up on PC), loads of background apps kept FCing and Messaging was broken. I was unable to read or send text messages. The main screen of the app worked, but it was impossible to navigate from there. I then flashed another HyDrOG3N build, the 08/04 Easter Egg version, wiping Dalvik before. Same issue, and same dammed Kang unicorn (yes, I'm a jerk -and proud).
My 'friend' now wants to rip my overconfident head off, while I assure him that I've got a thousand and one solutions. Er, yeah, flash different gapps (idiot, should have done that straight away) or use a different ROM. So much for 'rockstability'.
I won't have the phone until Wednesday, but am wondering if anyone has any idea what went wrong? Sorry for the novel, I just hope somewhere there's an explanation...
Thanks for any suggestions.
Sir, try to flash another ics rom, is lot of them. I flashed 2 days ago Hydrogen rom and I had same strange issue, I dunno why. So I flashed another rom and now it's fine. Good luck!
Thanks for quick reply, think it's the only thing I can do, really...
First off, I'm sorry if it seems like this has been answered before, but I did a good deal of searching and couldn't find anyone who had quite the same problem I do.
I've been using Agrabren's CM10 - Disarmed Toaster for CDMA since Friday. But I ran into a "storage running low" problem this morning (after I let my phone go dead last night and then put it on the charger overnight) which caused me to do a full wipe and re-flash with his latest version (0.2.2). Since then, I haven't been able to receive texts at all. I have Google Voice, and I was getting the texts there, but not in the actual messaging app. I have since tried disabling and re-enabling Google Voice to no avail, and it is currently disabled to remove extra variables. I haven't been very scientific about my troubleshooting process, which has mostly involved a lot of flailing around, wiping, and re-flashing. But I've re-installed the ROM countless times and twice now have flashed a Sense ROM (MeanROM 2.6) to update my PRL and Profile and then flashed back to CM10. I suddenly got a flood of all my texts when I flashed to Sense, but still don't get any texts after flashing back to CM10.
I tried Paranoid Android and AOKP variants and have the same problem. I even tried Team DIRT's CM10 Codename Android and texts still didn't come in. I should also mention that I had the same problem a while back with Disarmed Toaster 0.1.6, and it probably started the same way with running out of battery and then having the storage low issue and re-flashing. I never figured out exactly what the issue was, but I think at the time I was able to fix it by flashing a Sense ROM and updating profile and PRL.
Sorry for the long explanation. Let me know if there is any other info I can provide to help. I really didn't want to go back to MIUI, but that might be only option at this point.
Also, for reference:
HBOOT - 1.40, S-Off
Recovery - 4ext 1.0.0.5 RC5
THANKS
you might wanna try looking here.
http://forum.xda-developers.com/showthread.php?t=1818387
efan3719 said:
you might wanna try looking here.
http://forum.xda-developers.com/showthread.php?t=1818387
Click to expand...
Click to collapse
Thanks. I already asked there and I've been following the thread. I don't think anyone else has mentioned this problem.
Sent from my PG86100 using xda app-developers app
I think it's the 4g logs growing exponentially and filling the space. You need to periodically clear the logs.
coal686 said:
I think it's the 4g logs growing exponentially and filling the space. You need to periodically clear the logs.
Click to expand...
Click to collapse
Yeah, I think that's what caused the "Storage space running low" that started the whole thing. But the real issue is why I was no longer able to receive texts in any CM10 ROM since I re-flashed to "fix" the storage problem....
Thanks for the tip.
Anyway, it seems as though the problem has been resolved. So far I'm receiving texts okay - here's what I did:
1. Called Sprint while on CM10 Disarmed Toaster, they said provisioning looks okay, and the did a "refresh" on their end - didn't help anything
2. Flashed MIUI - received texts fine
3. Flashed CM10 again - still not working
4. Restored backup of MIUI - received texts fine, used for a little while
5. Flashed CM10 again - now able to receive texts
I think there's something going on behind the scenes that I am not aware of. Somehow it looks like restoring my backup and using it for a while fixed whatever the issue was.
It could be the apn xml file in the cm10 rom. The settings are probably not set correctly. Have you looked through the thread where you got the rom to see if anybody else was having the same problem? If not you could always address this issue to the dev. Ask him if you can provide a logcat to him on the thread or pm him the logcat.
Jsparta26 said:
It could be the apn xml file in the cm10 rom. The settings are probably not set correctly. Have you looked through the thread where you got the rom to see if anybody else was having the same problem? If not you could always address this issue to the dev. Ask him if you can provide a logcat to him on the thread or pm him the logcat.
Click to expand...
Click to collapse
That's an interesting thought, but it doesn't seem to explain why no one else is having the same problem, or why it worked at one time, and then didn't work after I re-flashed.I guess there could be something wrong with the flash process that was corrupting that file on my phone. But I was able to *send* sms without a problem, so I'm not sure.
As I mentioned before, I've been following the threads for the ROM and no one else has mentioned the same problem. I asked the question in the thread, but I didn't get an answer.
Anyway, as I mentioned above it's working now, so I wouldn't be able to provide a logcat unfortunately. For anyone else with the problem, I guess the only suggestion I can give it to make sure you keep a backup of a working ROM handy if you're going to re-flash a lot.
I have had the same problem its agrabating get it
But it seems as the issue is inconsistent at best. I found out how to clear the 4g logs why are those logs even kept anymore?
The messaging this is the worst part I too use google voice
We need to find a better solution to this
mastadave99999 said:
I have had the same problem its agrabating get it
But it seems as the issue is inconsistent at best. I found out how to clear the 4g logs why are those logs even kept anymore?
The messaging this is the worst part I too use google voice
We need to find a better solution to this
Click to expand...
Click to collapse
Haha...
Just so you know, once you've cleared out the 4G logs, you can make that directory "immutable" so that the logs don't get created anymore. Just run this command in terminal emulator:
chattr +i /data/wimax/log
I'm obviously not an android developer, and I have no idea why the logs are still created. I also have no idea what caused the text message issue, but if you are currently not getting texts, I would suggest you restore a working backup and then re-flash Agrabren's ROM like I did.
SMS Help!!
soldierforchrist2 said:
Yeah, I think that's what caused the "Storage space running low" that started the whole thing. But the real issue is why I was no longer able to receive texts in any CM10 ROM since I re-flashed to "fix" the storage problem....
Thanks for the tip.
Anyway, it seems as though the problem has been resolved. So far I'm receiving texts okay - here's what I did:
1. Called Sprint while on CM10 Disarmed Toaster, they said provisioning looks okay, and the did a "refresh" on their end - didn't help anything
2. Flashed MIUI - received texts fine
3. Flashed CM10 again - still not working
4. Restored backup of MIUI - received texts fine, used for a little while
5. Flashed CM10 again - now able to receive texts
I think there's something going on behind the scenes that I am not aware of. Somehow it looks like restoring my backup and using it for a while fixed whatever the issue was.
Click to expand...
Click to collapse
Has anyone figured out why SMS stopped working? I am running AOKP JB ROM and I can send text messages but I am not receiving them. Thanks for your help.
Still not working
I've been having the same problem with the sms, it works if you re-flash something else a couple times then flash CM10 back on but sms will only work for so long. I would like to pick apart the problem and see if we cant find the source of the problem, it could be a temp file that CM10 has been saving that interferes with the sms, but that's just a guess. any help on this is greatly appreciated
Just wanted to say I too have encountered this. I have tried flashing unofficial aokp 3.5 and unofficial slimbean 1.1. Getting ready to flash an MIUI rom like mentioned above.
Some Experimenting....
I did a small experiment just now (to try and get incoming SMS working) because I had essentially experienced the EXACT same problem, except that it was with P.A.C.MAN v.23 instead. What I did was installed a stock-based rom (I used unSENSABLE), which obviously allowed all my SMS to come flooding in, and stayed on that rom for about a day. After that I made a nandroid backup (of unSENSABLE) in 4ext, wiped everything except sd (not using the superwipe, and including caches) and then restored the backup. After that I booted up, let it sit for a while, then restarted into recovery. Again I wiped everything without using the superwipe, and flashed P.A.C.MAN v.23.0.0 and then GAPPS and booted. After all that, SMS was working again. We'll see how long it lasts...