Database Develop

Hero With Bluetooth

First off sorry if I got your hopes up with the above heading
Anyways Now that I got your attention
I would like to know how do you undo all cache to the sd
I used the stupid @ss ta utility from the market trying to see if I could undo the marrket cache, that isn't revertable(< is this even a word???)I tried multiple methods searched found one posting that was a total fail
And now I'm looking into straight up commands to revert
I know uninstalling the app doesn't undo the changes it just leaves them alone and still keeps on telling the phone to push all cache to sd
So what's next deleteing the folder that stores the cache just causes force closes so what the hec?
I've tried reflashing, over the current settings but with no wipe cuz I don't want to lose my current setup
So anyhelp appreciated
Thanks In Advance

If you don't want to wipe you will need to remove the symlinks, copy the folders to internal memory, and reboot the phone.
BTW did you notice it took 10 hours to get a response. People aren't too eager to help after being mislead into reading. Next time try a subject that fits the post & I can almost guarantee you will get responses quicker.

Agreed. I just now checked this out after seeing ONE post maybe 1 or 2 more now that it reads 2 replies I thought this was someone asking if a hero rom had bluetooth support and was gonna laugh

CM 4.2.1 / CM4.1.99x Exception with contact group

Some poeple are the meaning, that the place for this thread will be better here: OK, lets following this issue here. Here is a copy from the previews one:
CM 4.2.1 / CM4.1.99x Exception with contact group
Exception with Contacts - so like as in 4.1.99x
I have the same problem as in 4.1.99x, that I can not add a contact in my group (there is still ony one, which was working after some crashes in 4.1.999) without a crashed application
If I look into the exception Monitor, I can found a lot of:
Quote:
java.lang.IllegalStateException: Failed to find the My Contacts group"
Click to expand...
Click to collapse
What can I do or must do ?
History: I have had the G1 not so long time, but modif. it via WIPE to the 4.0.x ( stable )
After this (2 days later I upgrade to 4.1.111)
from this status I was following the description with the 2 Step to 4.1.999, where I have see the error the first time. With 4.0.x / 4.1.111 I haven't recognize this problem, because I have add some friend in my contact-list. For my meaning, this one was coming in, during upgrade in the 3 steps: WIPE, Google-Recovery, CM-Update 4.1.999.
Hint: If I update the phone, I start the phone WITHOUT a Mobile-Card: because I have had one time a bill over 200€ for data connection, and nobody knows why. So I boot the phone after update without card, check APNdroid, if 3G etc. disabed, shut down the phone, insert the casrd and boot again.
Maybe this handling calls the error ?
......
......
YES, I have use the search function and didn't found any usefull infos.
>>> ( how does I love this answer! If you found time to write this one, than I think, you know the answer - pls give me this one )
YES. I have reflashed the 4.2.1 with the card inside the phone: No change
Btw.: I was falling also in the error with the ext2 and ext3, so I change this one on the PC via tune2fs. But normaly every program, which need a DB and did not found it, create one. Or isn't it ?

Push > because its still avail and a Java exception is not a handling error

Just to bump this a bit and to pretend like it is actually useful to post in this forum...
Have you tried backing up your contacts via the browser, deleting them, sync the phone and then restoring?

Have you tried backing up your contacts via the browser, deleting them, sync the phone and then restoring?
Click to expand...
Click to collapse
No I haven't, because I have not so much contacts... So I was starting with a brand-new phone, "root" them, wipe them and change to CM4.0.x (Stable), jump to CM 4.1.11 and after a few days following the instruction to move to 4.1.999 with WIPE, 1st paket and the CM-paket.
Here I see the problem and also in 4.2.1.
About a missing Backup, I try only to create a contact manual on the phone.
THe first time, if I want to add the contact, the phone ask me to syncronise - but I was offline at all. So I reject this message ( there are also no datas to sync online )

Push .... .....

So my phone's slowed waay down, someone want to make sense of my logcat?

I'm having random freezes(ya know the kind where you have to yank the battery..) and the home screen takes forever to load sometimes. Also after not opening the app drawer for a while I takes a minute to repopulate what apps belong where.. Here's the logcat right after boot, I noticed a few oddities but can't really make heads or tails of it. Any help or suggestions would be greatly appreciated. (rooted official 1.6 if that matters)
http://pastebin.com/f750d9ab
i was curious about a few areas
1. the permission errors such as lines 12, 21, 34, 51 and 62.
2. the unknown/not granted permissions, lines 104-119
3. lines 188-204 don't look like a good thing(related to HOME it appears)
4. UltimateFaves seems real screwy.. lines 258-274 (thinkin i should just uninstall it)
5. then there seems to be another sort of error W/System.err... lines 313-322
all that appears to happen during boot(pre home?).. then i don't see much else. alot of starting and stopping of processes and a few of these
6. Line 508 W/Process ( 530): Unable to open /proc/997/status
which appears to be related to this
Line 478 I/ActivityManager( 530): Process com.android.music (pid 997) has died.
and so forth, each "W/Process..." having a related pid that has died.
anyone have a minute to give me a quick breakdown?

Im just seeing two exceptions...if i were you i would run fix_permissions in terminal before proceeding further

will do, thanks. oops, looks like I need to be su in order to do that heh.
Unable to chmod any system apps which i assume is because they are infact read only system apps.
Ok, done. changed about a dozen or so permissions o.0 will give it a day and see how things go. Thanks B-man007

sonikamd said:
will do, thanks. oops, looks like I need to be su in order to do that heh.
Unable to chmod any system apps which i assume is because they are infact read only system apps.
Ok, done. changed about a dozen or so permissions o.0 will give it a day and see how things go. Thanks B-man007
Click to expand...
Click to collapse
type su then

sonikamd said:
will do, thanks. oops, looks like I need to be su in order to do that heh.
Unable to chmod any system apps which i assume is because they are infact read only system apps.
Ok, done. changed about a dozen or so permissions o.0 will give it a day and see how things go. Thanks B-man007
Click to expand...
Click to collapse
fix_permissions in recovery, not from term emu.

evilkorn said:
fix_permissions in recovery, not from term emu.
Click to expand...
Click to collapse
No do not run it from recovery, the one written into the rom is always more up to date and relevant to the rom.
Just type su, then fix_permissions ...

All browsers crash without a "force close"

Hey all,
I've been an xda stalker for a while and have been using all sorts of roms for a while now, but now I am in need of my own question.
For a while now, my mother's G1 has been acting up, whether it be her own fault or a bug. But this one has me confused. Over the past three roms i flashed (dwang, cm, superd) this same problem is always around. Everytime I touch browser, dolphin, etc the page begins loading and then i see the home screen.
Everything else works as it should, which confuses me. Everytime I flash a rom, i wipe, wipe ext, repair ext, wipe, flash.
I'd be happy to post a logcat if someone would be so kind as to inform me how to dump to a txt file.
Hopefully this is something extremely easy so I can get her off my back hah

erkmasterflex said:
Hopefully this is something extremely easy so I can get her off my back hah
Click to expand...
Click to collapse
sure its easy, if its your mom's phone, dont have a unsupported non-factory rom on it... the REAL awnser is: wipe EVERYTHING, even your ext partition, and reinstall base, then CM... I'm guessing its something you mucked up by going between builds without wiping, or not fixing permissions between builds, or some app on your ext didnt play nicely.
*oh yeah, wrong section, read stickys, or DIAF, your choice*

jmhalder said:
sure its easy, if its your mom's phone, dont have a unsupported non-factory rom on it... the REAL awnser is: wipe EVERYTHING, even your ext partition, and reinstall base, then CM...
Click to expand...
Click to collapse
Nah I think he should install the RC29...just kiddin you should use Super-D or Enom's official. I kinda assumed this thread was about some kind of fix for browser problems.

Ace42 said:
Nah I think he should install the RC29...
Click to expand...
Click to collapse
well, the RC29 might actually force a wipe... and would update itself and have OTA keys... honestly probably not a bad way to go... Super-D is good, but honestly dont notice a huge difference between that and CM.

it was even not working when i reverted to complete stock. could this be a problem with the phone itself? Maybe revert to stock again and take it in to t-mo?
There should not be any problem with leftovers from previous roms, since i completely wipe data and ext as i mentioned in my first post.
Moderators, please move this to correct section. this seemed like the correct section since this seems to be more involved in the development side of things. Definately not Accessories but more involved than Q&A. Thank you

Phone ><---USB--->< PC/Laptop/Mac
adb logcat
watch text fly up screen ... make browser crash
quick !!!!! take a picture of that text.............
if you don't have a usb cable handy, a PC or the time to figure out how to get adb installed
go to terminal emulator on phone, and type
logcat|tee /sdcard/logcat.txt
( get the pipe "|" with alt then s )
make browser crash
go back to terminal press ball then C
Edit : the ball can be a bit of a pain, when in term do menu --> preferences --> control key , and set to which key you prefer, I like left alt as ctrl[\i]
now have a look at the logcat.txt file, it
less /sdcard/logcat.txt
you could just do logcat > /sdcard/logcat.txt
but it doesn't look as geeky
NB use >> instead of > to append > will make new file >> will add to file
to append to file with tee use tee -a file.txt[\i]
and yeah, wrong section

thank you very much for your assistance and the little linux command briefing ha
i decided to try every sort of wipe, repair, etc and do it multiple times. probably didn't do anythin, but worth a shot ha.
Ended up working! I removed the ext and swap partitions, wiped anything i could multiple times, flashed super d, didn't work, wiped a bunch, flashed htc recovery image, then cyan, and presto. For whatever reason it finally worked.
Shoulda done the logcat and posted it so y'all could see whatever was going on and hopefully help someone out later. but all is resolved for now.
If there is a next time, I will post in Q&A. I want to thank everyone for their input and wish all a good night.
-Eric

Moved as not Android Development.

[ROM] Helly_Bean [4.3] [nightly builds] - Vibrant

Many thanks, to pawitp, FaultExeption, Jt1134, be18 and all the other people who commit to gerrit. without these, this rom wouldn't be possible
you can find the official website for this projekt here
http://www.hellybean.com/index.html
you'll find download links and faq on this site.
IRC channel:
http://webchat.freenode.net/?channels=hellybean
Install instructions:
coming from any other rom:
- make sure to have gingerbread bootloaders
- flash zip
- reboot recovery
- flash zip again
- flash gapps
if you are coming from a previous version, older than 08/28 your data will get wiped due to new partition layout!
coming from previous version:
- flash zip
Additional changes, compared to cm10.2 (this list might not be complete):
- facebook sync integrated
- option to enable high end gfx effects
- possibility to activate and customize navigation bar
- aokp clock (right/center, custom color, big/small am/pm, display weekday)
- misc settings in settings menu
- added possibility to change the colors of the statusbar toggles
- added option to enable/disable coloring of toggles
- added option to display a small bar below the toggles as indicator for toggle state
- possibility to change quicksettings tile background color
- added pie control from slim roms
- added app sidebar from chameleon os (unfortunatelly it still seems to be a little buggy...wip)
- alternate default app picker (from aokp)
- removed cm stats
- removed cm updater
- lockscreen seethrough
- possibility to change color of lockscreen text/pictures
- customizable "long press back to kill" timeout
- added HALO
- more options for rebing the hardware keys
- build.prop mods
- TRDS (The real Dark Slim)
- ...
Click to expand...
Click to collapse

Can we please keep this thread clean?
If you like Der's work, hit his Thanks button. Please refrain from posting like "Thanks", "Great ROM" or "Can't wait" These types of post just cause clutter and cloud the real questions like about wifi, the God forsaken GPS, Devil OC/UV settings,....
We have a great group here who know proper "Net-iquette", but there has been a rather large influx of new users too.
Good luck and Happy Flashing.

New ROM online here
Sent from my Olympus via Hermes.

...sorry if I'm the party-p**per but it's something I wish to know about the new version (if it is fixed or going to be). It's a long standing bug which has often driven me crazy. I've written about it in the other thread but let me restate it here and the possible workarounds that kinda work but (which) are far from elegant. Anyway here it is:
In both the 0817 and 0828 that I've tried it is there (and probably it was from the start), it's the duplicating effect that media scanner has over my media. That's to say that every time I reboot it re-adds my media, creating (false) duplicates which disrupt my music player but also the gallery. Of course an obvious work-around is to use apps which use their own SD scanner or (worse yet) to delete the "media provider"'s cache before each and every reboot.
Since smartphones -though- are almost primarily for media consumption I would prefer an actual fix to this problem. It does not belong to the "popular" bugs (bad GPS etc), but it is a bug I don't often see discussed and I think it deserves part of the limelight. Anything approaching to a fix would really "untie my hands" for one...
BTW thanks for the great rom

@guy above me
It probably isn't in the bugs list because not too many people have suffered from it.
Did you do a complete wipe before flashing 828
Sent from my SGH-T959 using Tapatalk 2

Steve - thats been a random bug since ICS and maybe even before. Try some file maintenance on your SD card. Delete the Lost.dir on your internal SD, and the .thumbnails folder in your DCIM folder. Also, maybe try backing up your important data from both the internal and external sd, format them both, then load your data back onto it. That problem always seemed to stem from cache files. I personally have never seen it, but I run basic file maintenance before every flash, it takes just a few minutes, and saves a ton of headaches.

I`m coming from 817.....So just flash allinone zip. No GAPPS? Just curious before i flash.

Guitar100 said:
I`m coming from 817.....So just flash allinone zip. No GAPPS? Just curious before i flash.
Click to expand...
Click to collapse
I needed to flash gapps because of the partition swap. So back up your apps because they will be wiped.
Sent from my Olympus via Hermes.

What about the Battery?? My battery drains too early. I can't use 1.5 hours at a stretch!!!
Sent from my SGH-T959 using xda app-developers app

Br1cK'd said:
Steve - thats been a random bug since ICS and maybe even before. Try some file maintenance on your SD card. Delete the Lost.dir on your internal SD, and the .thumbnails folder in your DCIM folder. Also, maybe try backing up your important data from both the internal and external sd, format them both, then load your data back onto it. That problem always seemed to stem from cache files. I personally have never seen it, but I run basic file maintenance before every flash, it takes just a few minutes, and saves a ton of headaches.
Click to expand...
Click to collapse
The problem seems to be on/in my external SD alone. I've formatted it before reinserting it, also I installed the version that I have now (0828) coming from stock, so I thought my starting point was a clean sheet... but no, the problem came back to haunt me, I dunno maybe my micro-SD is dying, I'm hoping that it ain't. Thanks for the reply though...

On the lighter side of things; If anyone misses the MIUI V4 like-UI
http://forum.xda-developers.com/showthread.php?t=1853132
released about a hour ago
-When you first install it might crash System UI- Just press home button and it should be back in a few seconds.

Stevethegreat said:
The problem seems to be on/in my external SD alone. I've formatted it before reinserting it, also I installed the version that I have now (0828) coming from stock, so I thought my starting point was a clean sheet... but no, the problem came back to haunt me, I dunno maybe my micro-SD is dying, I'm hoping that it ain't. Thanks for the reply though...
Click to expand...
Click to collapse
Do you have access to another microSD to try, and see if the problem repeats itself on a different card? Its worth a shot, and could let you know if its the card or not.

How to choose vc or cmc when flashing? old version only make a devil/voodoo_color works. But it seems like not working in new versions.

dddtc2005 said:
How to choose vc or cmc when flashing? old version only make a devil/voodoo_color works. But it seems like not working in new versions.
Click to expand...
Click to collapse
From OP.
DerTeufel1980 said:
Install instructions:
if you want the rom to be installed with voodoo color kernel instead of the default one, just create a folder called devil at your sdcard, and place an empty file named voodoo_color in this folder. Then just install the rom as followed below
Click to expand...
Click to collapse

I have had one bug come up on the latest build, 0901, wondering if anyone can verify. Exchange Services keeps crashing on my corporate email account. Anyone else run into this on the latest build?
Here is a logcat, if it help at all DT.
Code:
W/dalvikvm( 7890): threadid=13: thread exiting with uncaught exception (group=0x40a7f300)
E/AndroidRuntime( 7890): FATAL EXCEPTION: ExchangeService
E/AndroidRuntime( 7890): java.lang.NullPointerException
E/AndroidRuntime( 7890): at com.android.exchange.ExchangeService.collectEasAccounts(ExchangeService.java:560)
E/AndroidRuntime( 7890): at com.android.exchange.ExchangeService.access$600(ExchangeService.java:107)
E/AndroidRuntime( 7890): at com.android.exchange.ExchangeService$AccountObserver.<init>(ExchangeService.java:665)
E/AndroidRuntime( 7890): at com.android.exchange.ExchangeService.run(ExchangeService.java:1973)
E/AndroidRuntime( 7890): at java.lang.Thread.run(Thread.java:856)
I/BufferQueue( 412): BufferQueue: minUndequeued=2
W/ActivityManager( 3817): Duplicate finish request for ActivityRecord{40ea6a38 com.android.email/.activity.Welcome}

omnifarious said:
From OP.
Click to expand...
Click to collapse
Thanks, this works for version 0901 again. but failed for version 0830.

battery seem to be a major issue I am not sure why. I flashed 9/1 an hour go and I had the battery fully charged, other then doing the required updates and setting up my apps, I left it on alone, an hour later i notice my battery status was 76%...Android System seem be utilizing it mostly. I hope there is a solution.....other then that everything seem to be pretty smootth. It was little choppy at first and it got smoother the more i played with....

Br1cK'd said:
I have had one bug come up on the latest build, 0901, wondering if anyone can verify. Exchange Services keeps crashing on my corporate email account. Anyone else run into this on the latest build?
Here is a logcat, if it help at all DT.
Code:
W/dalvikvm( 7890): threadid=13: thread exiting with uncaught exception (group=0x40a7f300)
E/AndroidRuntime( 7890): FATAL EXCEPTION: ExchangeService
E/AndroidRuntime( 7890): java.lang.NullPointerException
E/AndroidRuntime( 7890): at com.android.exchange.ExchangeService.collectEasAccounts(ExchangeService.java:560)
E/AndroidRuntime( 7890): at com.android.exchange.ExchangeService.access$600(ExchangeService.java:107)
E/AndroidRuntime( 7890): at com.android.exchange.ExchangeService$AccountObserver.<init>(ExchangeService.java:665)
E/AndroidRuntime( 7890): at com.android.exchange.ExchangeService.run(ExchangeService.java:1973)
E/AndroidRuntime( 7890): at java.lang.Thread.run(Thread.java:856)
I/BufferQueue( 412): BufferQueue: minUndequeued=2
W/ActivityManager( 3817): Duplicate finish request for ActivityRecord{40ea6a38 com.android.email/.activity.Welcome}
Click to expand...
Click to collapse
When that happens I clear the app data.
Sent from my Olympus via Hermes.

nht48823 said:
battery seem to be a major issue I am not sure why. I flashed 9/1 an hour go and I had the battery fully charged, other then doing the required updates and setting up my apps, I left it on alone, an hour later i notice my battery status was 76%...Android System seem be utilizing it mostly. I hope there is a solution.....other then that everything seem to be pretty smootth. It was little choppy at first and it got smoother the more i played with....
Click to expand...
Click to collapse
I haven't flashed 09012012 yet so I don't know if it still utilizes the KA7 modem. If it does refer to this post:
http://forum.xda-developers.com/showpost.php?p=30966626&postcount=1255

iKoolkid said:
When that happens I clear the app data.
Sent from my Olympus via Hermes.
Click to expand...
Click to collapse
I tried that, also fixing permissions, clearing out the accounts, even pushed the exchange2.apk from 0817 which worked great to my recollection.