Database Develop

Super Circle Battery

Is it possible to install the Super Circle Battery in Htc Aria?

Try this http://forum.xda-developers.com/showthread.php?t=775970

zeyoner said:
Try this http://forum.xda-developers.com/showthread.php?t=775970
Click to expand...
Click to collapse
Many thanks! It works great!

AWESOME! I'll be using this now!

I have to say, that site above is the coolest thing since sliced bread. I just made a custom rom with it and it worked flawlessly.

Just sharing the love It's a great find, I've spreading the link around.

Are you guys using this on CM6? I tried it and it did not work :/ any tips ?

I too am running CM6, but I am getting FC on apps like ROM manager, and certain settings windows like User Interface.
Any ideas?

pcruz said:
Are you guys using this on CM6? I tried it and it did not work :/ any tips ?
Click to expand...
Click to collapse
I'm using it on cm6 with no issues...works great....what isn't working for you
sent from my aria on cm6 v6.0.2.1 dumfuq's oc kernel v3.2, 844

delutedsoul23 said:
I'm using it on cm6 with no issues...works great....what isn't working for you
sent from my aria on cm6 v6.0.2.1 dumfuq's oc kernel v3.2, 844
Click to expand...
Click to collapse
Which nightly are you running, as I don't have the same Kernel version as you. I am running 2.6.69.6. It works, just features in Settings keep force closing.
********
Message from Mendozinas on the other thread:
sorry for all, we have some server side isues and all coocked files are corrupted.
You can get a lot of FC's and corrupted Ringer volume progbar.
we will fix this ASAP.
********
I will try again later, and advise if I still need help.

Ok so im running CM6 6.0.2.1 "stable" from 9/12 I believe. it is not a nightly.
I downloaded the rom, extracted the res file and I got an error after the zip was compiled (at the pick up site)
after that I tried it with the res provided for cyanogen roms and it compiled fine, I installed it fine. When i rebooted I got a red circle with an exclamation mark.

i am getting the rom manager force close as well on liberated... not a major deal ... everything you can do in rom manager you can do in clockwork... back ups and restores...but on a lighter note i love the site cooked me up a nice little meal there... although after i d/l my framework res file and installed it the UOT Kitchen went offline at 2:30pm PST on 10/13/10 with a statement of
"Ultimate Online Theme Kitchen
We are sorry, server experience some technical problems.
All coocked files are corrupted.
You can get a lot of FC's and corrupted Ringer volume progbar.
We are fixing this now. Kitchen will be online ASAP.
Follow us at XDA:
http://forum.xda-developers.com/showthread.php?t=775970"
may want to redo your meal there after things get back up
ok update... UOT kitchen is back up and i redid my meal and no more force closes!

Tried this again today, worked perfectly with the CM6 liberty res file.

I imagine that we can use this for the Liberated ROM as well? Been wanting the sort circle battery for a while, will get rid of the widget fire me.

I think I'm getting way ahead of myself, but is this only for rooted Aria's? Or can I use the kitchen to customize my stock phone?
Give me a tiny break, okay, I was using a Moto RAZR 2 less than 48 hours ago!

911jason said:
I think I'm getting way ahead of myself, but is this only for rooted Aria's? Or can I use the kitchen to customize my stock phone?
Give me a tiny break, okay, I was using a Moto RAZR 2 less than 48 hours ago!
Click to expand...
Click to collapse
Root only... I don't think you can push something adb without being rooted, although I might be wrong!
Sent from my Liberty using XDA App

I think you're right... I had come to the same conclusion earlier today. Thanks though!

so, im running CM6.1.0 RC
every time i upload my framework (which is custom), i am getting an error log file and it will not work for me!
-sighs-
all i want is a circle battery... it would take me a year to edit the files!!

UOT with FR008
Hi,
With FR008, I could not get it to work after I download the UOT ROM (with circle battery only) and installed it through clockwork, I managed to get to this message "Installing: SDCARD:UOT-.....zip.... Install from sdcard complete". But whenever I selected "go back", my screen would go blank and I could not get to the reboot menu.
Please help.

[USER][CM9/ICS][5-28 PATCH NO LONGER NEEDED] CM9 240 dpi with Soft Navigation Keys

PATCH NO LONGER NEEDED!
This post used to discuss a patch I made to show the Navigation Keys in Phone GUI mode. I am happy to announce that the patch is no longer needed.
In CM9 the Phone GUI is activated anytime you set the lcd density to anything higher than 160 dpi. With the Nook Color when you go to the Phone GUI the navigation keys are suppressed.
There is a method to activate the Navigation Bar that requires no patches or zip flashes. Just add the two lines below to your local.prop file in /data. I recommend using local.prop instead of build.prop so that it is not necessary to re-edit the file after each flash of a new ROM. If you do not have this file, create an empty txt file and put these two lines in it:
qemu.sf.lcd_density=240
qemu.hw.mainkeys=0
The first line tells your system to change lcd density to put it in phone gui. You can change the 240 number to any number above 160 and the phone gui will be displayed.
The second line tells your system that your hardware has no physical keys and enables the soft key navigation bar.
Reboot.
If you want to return to 160 dpi and the tablet gui, just delete or comment out the two lines above and reboot.
Also CM has added the ability to customize the navigation bar. Go to settings, system, navigation bar and it will tell you how to do it. You can move the buttons around, add buttons, change how they perform, etc.
5-28-2012 is the last day I will be making patches.
No-moar zips! Yay!
Edit (6-24): Removed last patch. Too many users will still downloading it and it does not work properly with the current nightlies.
Removed screenshots

The board lists the latest version as only being a few bytes compared to the other earlier versions of this, is this a sign of a bad upload?
Will be giving the second to last version a try to see if this is what I hope it will be.. Thanks!
Sent from my NookColor using Tapatalk

bornagainpenguin said:
The board lists the latest version as only being a few bytes compared to the other earlier versions of this, is this a sign of a bad upload?
Will be giving the second to last version a try to see if this is what I hope it will be.. Thanks!
Sent from my NookColor using Tapatalk
Click to expand...
Click to collapse
I still see 4.1MB as the size of rev 11, which is the latest.

Okay, that's screwy. On my nook it said it was only a few bytes, but now on my phone it is listing the same size as the others. Sorry for wasting your time.
Oh, a quick question while I have your attention --is there any way to get the two status layout but with a lower dpi (160)? Or are we stuck choosing between phone and tablet interface if we want more screen space?
Sent from my LG-VM670 using Tapatalk

bornagainpenguin said:
Oh, a quick question while I have your attention --is there any way to get the two status layout but with a lower dpi (160)? Or are we stuck choosing between phone and tablet interface if we want more screen space?
Click to expand...
Click to collapse
Not sure what you mean by two status layout. Do you mean status at top and navigation on bottom?
160 always gives you the tablet layout with the status bar at the bottom, with the battery and time, etc there. You can use other launchers that allow you to modify such things as icon grid layout, etc, but the full status bar remains at the bottom.
If you set anything above 160 (180, for example), it goes to phone mode with the status bar at the top, and if you use my patch, the navigation bar will be at the bottom. You can change the density to anything above 160 and my patch will work. I just chose 240 because it is what I like and gives the most market compatibility. After applying my patch, just change the value in build.prop in /system (ro.sf.lcd_density=).

Yeah, that's what I meant. I will probably give 180dpi a try next time I use the nightlies. Going to mess around with CM7.2 Kang and see how it goes. Thanks for everything, I really hope your patch is made a default option once CM9 goes stable.
Sent from my LG-VM670 using Tapatalk

Could you please check the last file again? This one: update-softkey-240dpi-4-17-Rev13.zip Thanks.
I can see it to be the same size as the others, but when I try to download it all I get is an html 404 page. update-softkey-240dpi-4-15-Rev12.zip downloaded just fine.
--bornagainpenguin

bornagainpenguin said:
Could you please check the last file again? This one: update-softkey-240dpi-4-17-Rev13.zip Thanks.
I can see it to be the same size as the others, but when I try to download it all I get is an html 404 page. update-softkey-240dpi-4-15-Rev12.zip downloaded just fine.
--bornagainpenguin
Click to expand...
Click to collapse
It downloaded fine for me just now and 23 others have downloaded it.
Sent from my Nook Color running ICS and Tapatalk

I'm also not able to download a complete Rev13. I just get a file with a length of 554. I was able to get Rev12, but it's not working with the latest builds. Thanks for all your help on this!

Sudonym said:
I'm also not able to download a complete Rev13. I just get a file with a length of 554. I was able to get Rev12, but it's not working with the latest builds. Thanks for all your help on this!
Click to expand...
Click to collapse
The old versions do not work with the latest build, that's why I updated it. I just uploaded it again. Try now.

leapinlar said:
It downloaded fine for me just now and 23 others have downloaded it.
Sent from my Nook Color running ICS and Tapatalk
Click to expand...
Click to collapse
At least ten of those were mine. I was out and about last night and yesterday morning so I tried at different places and times before asking about it. I didn't want a repeat of last time where I asked and it was fine later that day. I appreciate the effort you guys put into this kind of stuff and the last thing I want to be is a bother.
leapinlar said:
The old versions do not work with the latest build, that's why I updated it. I just uploaded it again. Try now.
Click to expand...
Click to collapse
Just downloaded it on my phone and it looked like a complete package! Thanks!
update: how long is it supposed to take on reboot to apply? I'm stuck in reboot for a while now and starting to worry...
Sent from my LG-VM670 using Tapatalk

Okay. This is not working for me at all. I don't know how many times I've flashed now. All that happens is a message about Android updating my applications and then a return to the bootanimation that never ends. Not sure where things are going wrong. :banghead:
Wish I knew what I was doing to screw things up.
Sent from my LG-VM670 using Tapatalk

bornagainpenguin said:
Okay. This is not working for me at all. I don't know how many times I've flashed now. All that happens is a message about Android updating my applications and then a return to the bootanimation that never ends. Not sure where things are going wrong. :banghead:
Wish I knew what I was doing to screw things up.
Are you flashing the Rev13 patch with a 4/18 build? That combination works for me.
Click to expand...
Click to collapse

Sudonym said:
Are you flashing the Rev13 patch with a 4/18 build? That combination works for me.
Click to expand...
Click to collapse
I tried it with that build and I tried it with the one from yesterday. In both cases, I get a message about moving applications and a return to the bootanimation. Then ten or more minutes go by while the bootanimation spins with no feedback or signs of ever getting back into the GUI.
Really frustrating.
Sent from my NookColor using Tapatalk

Sorry if this is a stupid question, but will this work with Eyeballer's nightly builds (with/without opengl) or just with the one in the "work in progress" thread?

bornagainpenguin said:
I tried it with that build and I tried it with the one from yesterday. In both cases, I get a message about moving applications and a return to the bootanimation. Then ten or more minutes go by while the bootanimation spins with no feedback or signs of ever getting back into the GUI.
Really frustrating.
Sent from my NookColor using Tapatalk
Click to expand...
Click to collapse
The update to the CM repo broke the packages I offer in Botbrew, which happens when they significantly update the framework apps. Leap's patches always seem to break at he same time. The behavior your describing is what happens when you match a patch and a ROM that are incompatible. I know you have had problems with the downloader, (trust me you're not alone.) Just, one more time, flash the latest build and the latest patch together. The repo did not update again, I can promise you that. I bet with all the flashing and patching, you just did not patch the right build.
I have swapped in the old system apps maybe fifteen times over the last couple days, I know what that behavior is. And I use my own version of leapinlar's patch, so I know exactly how it works and what that behavior means. If it is working for others it will work for you if it has downloaded correctly.
slack04 said:
Sorry if this is a stupid question, but will this work with Eyeballer's nightly builds (with/without opengl) or just with the one in the "work in progress" thread?
Click to expand...
Click to collapse
The system apps work in any build for the Nook Color, opengl or not.

slack04 said:
Sorry if this is a stupid question, but will this work with Eyeballer's nightly builds (with/without opengl) or just with the one in the "work in progress" thread?
Click to expand...
Click to collapse
This patch will work with eyeballer's, Samiam303's or your home built version. All you have to make sure of is that you are using a version that is reasonably close in date to the build. As CM9 evolves and improves the base files that I am patching change and old versions of the patch will not work on that build. For instance, the 4-15 patch will no longer work on 4-17 or newer builds. I try to upload new versions when that happens.
I just tested eyeballer's 4-19 non-opengl build with the 4-17 patch and it still works.
@bornagainpenguin - are you flashing the build first and booting to that to be sure the base build download is ok before you flash my patch? If you do that it should say updating only 1 application after flashing mine. You might also try manually clearing your dalvik cache. That is what it is supposed to be doing automatically when it says updating applications.
Sounds like you are having download problems with with your devices so that might be the issue too.
Sent from my Nook Color running ICS and Tapatalk

leapinlar said:
@bornagainpenguin - are you flashing the build first and booting to that to be sure the base build download is ok before you flash my patch? If you do that it should say updating only 1 application after flashing mine. You might also try manually clearing your dalvik cache. That is what it is supposed to be doing automatically when it says updating applications.
Sounds like you are having download problems with with your devices so that might be the issue too.
Sent from my Nook Color running ICS and Tapatalk
Click to expand...
Click to collapse
I am making sure I boot up to a complete Android environment (beginning the setup part where they ask you which language and your google account, etc) before rebooting to recovery to install.
I just gave it another try using eyeballer's 4-19 opengl build and everything seemed to work right up to the point where I tried to set the DPI. Using Nook Color Odds and Ends results in no change. I then try LCD Resolution (Root) which results in an error on reboot:
Code:
Unfortunately, System UI has stopped.
I suppose I could just give up and accept the 240 DPI, but I really don't want my icons to be that big...
Back to CM7 with me I suppose....
--bornagainpenguin

bornagainpenguin said:
I am making sure I boot up to a complete Android environment (beginning the setup part where they ask you which language and your google account, etc) before rebooting to recovery to install.
I just gave it another try using eyeballer's 4-19 opengl build and everything seemed to work right up to the point where I tried to set the DPI. Using Nook Color Odds and Ends results in no change. I then try LCD Resolution (Root) which results in an error on reboot:
Code:
Unfortunately, System UI has stopped.
I suppose I could just give up and accept the 240 DPI, but I really don't want my icons to be that big...
Back to CM7 with me I suppose....
--bornagainpenguin
Click to expand...
Click to collapse
What were you trying to set the dpi to? The best way to set it is to edit the build.prop file in /system manually. Change the line ro.sf.lcd_density=240 to some other value above 160. That line does not exist there until you flash my patch. Also make sure there is not a density line in local.prop in /data. Some of those density changing apps try to set density there and if they do, that setting never gets overwritten in a flash and always overrides what is in build.prop.
Sent from my Nook Color running ICS and Tapatalk

leapinlar said:
What were you trying to set the dpi to?
Click to expand...
Click to collapse
180 DPI. Trying 160 DPI just means that I lose the phone GUI
leapinlar said:
The best way to set it is to edit the build.prop file in /system manually. Change the line ro.sf.lcd_density=240 to some other value above 160. That line does not exist there until you flash my patch.
Click to expand...
Click to collapse
I've never had great luck remembering the adb commands to push and pull files. I could probably try using root explorer to copy to the SDCard and do it on the netbook? Will look into this....
leapinlar said:
Also make sure there is not a density line in local.prop in /data. Some of those density changing apps try to set density there and if they do, that setting never gets overwritten in a flash and always overrides what is in build.prop.
Sent from my Nook Color running ICS and Tapatalk
Click to expand...
Click to collapse
Just checked that out and doesn't seem to be a factor. Thanks for bringing it up so I could eliminate it though.
Sent from my NookColor using Tapatalk

GTalk Video on CM10 - Solutions & Opinions

Hey all,
The GTalk video call fc bug on CM10 has been discussed sparsely in various threads and in order not to spam/pollute them even more with posts regarding the issue i decided to make a new one, just to figure out if it really works ok for some and why's that. Recently it was mentioned that if one flashes the Xoom modded gapps (by EOS team - found here http://forum.xda-developers.com/showthread.php?t=1777987) he'll get video call running since the EOS team has modded the package in order to work with non-NEON devices (or something like that - haven't been able to find clear documentation in their thread). I flashed said gaps package and, even though the phone is able to initiate the video call in the background, i get a foreground 'unfortunately gtalk has closed' or so message. Thats definitely better than before when the program was simply crashing, but doesn't solve the issue. Audio calls run fine though. Pengus mentioned that he wiped dalvik/cache, flashed EOS gapps, rebooted and rebooted again and it worked. Didnt happen for me, still same issue on video calls. I must also note that even b4 flashing EOS gapps, i was able to do video calls and even videoconference (3 way video call) using G+ hangouts, so it must be a program specific issue more than a general android libs situation (excuse my ignorance - doing my best to understand how things work in this OS ). So how do this run for you people? Is there anyone who managed to get it running fine on CM10, and if yes, can you give some details on your current setup? Also, if you did manage to get it running, did you follow a different flashing procedure than the one mentioned here? Thanx for your replies/participation
My current setup: CM10 3/1 nightly, old BL, v28e BB, EOS gapps
Peace

Ximo F. Verde said:
Hey all,
The GTalk video call fc bug on CM10 has been discussed sparsely in various threads and in order not to spam/pollute them even more with posts regarding the issue i decided to make a new one, just to figure out if it really works ok for some and why's that. Recently it was mentioned that if one flashes the Xoom modded gapps (by EOS team - found here http://forum.xda-developers.com/showthread.php?t=1777987) he'll get video call running since the EOS team has modded the package in order to work with non-NEON devices (or something like that - haven't been able to find clear documentation in their thread). I flashed said gaps package and, even though the phone is able to initiate the video call in the background, i get a foreground 'unfortunately gtalk has closed' or so message. Thats definitely better than before when the program was simply crashing, but doesn't solve the issue. Audio calls run fine though. Pengus mentioned that he wiped dalvik/cache, flashed EOS gapps, rebooted and rebooted again and it worked. Didnt happen for me, still same issue on video calls. I must also note that even b4 flashing EOS gapps, i was able to do video calls and even videoconference (3 way video call) using G+ hangouts, so it must be a program specific issue more than a general android libs situation (excuse my ignorance - doing my best to understand how things work in this OS ). So how do this run for you people? Is there anyone who managed to get it running fine on CM10, and if yes, can you give some details on your current setup? Also, if you did manage to get it running, did you follow a different flashing procedure than the one mentioned here? Thanx for your replies/participation
My current setup: CM10 3/1 nightly, old BL, v28e BB, EOS gapps
Peace
Click to expand...
Click to collapse
Hi,
here is what I did to solve this: I just took the libvideochat_jni.so from the eos-package and pushed it to /system/lib. Afterwards I cleared gtalk data and cache, restarted the device. Finally I could do video-calls
I've also attached the libvideochat_jni.so I used, maybe someone can make a flashable zip from it. I'm on pengus latest rom+kernel by the way.
Regards,
orgler

orgler said:
Hi,
here is what I did to solve this: I just took the libvideochat_jni.so from the eos-package and pushed it to /system/lib. Afterwards I cleared gtalk data and cache, restarted the device. Finally I could do video-calls
I've also attached the libvideochat_jni.so I used, maybe someone can make a flashable zip from it. I'm on pengus latest rom+kernel by the way.
Regards,
orgler
Click to expand...
Click to collapse
thanx for the tip mate. pushed the file w quick adb pusher, wiped app's data/cache but still get fc when trying to video call.. all this after i moved to official cm10.1, but i doubt that thats the problem. what a terrible bug #@$%&$#@&!!!!
Sent from my LG-P990 using xda app-developers app

reverted to cm10, gonna try it out again.
Sent from my LG-P990 using xda app-developers app

I didn't even wipe dalvik cache. Just the gtalk data. And then I did a reboot. Does voice chat work? Does the app just close or do you get a fc?
Gesendet von meinem LG-P990 mit Tapatalk 2

ok, went back to cm10 3/1 nightly (old BL), flashed pengus' new kowalski kernel, pushed the .so file, deleted talk's data, rebooted. getting instant fc on both video and audio calls. :banghead:
Sent from my LG-P990 using xda app-developers app

Could you create a logcat?
Gesendet von meinem LG-P990 mit Tapatalk 2

ok, doin it now
Sent from my LG-P990 using xda app-developers app

There you go. Logcat of fc first on video call n then on audio call. View attachment gtalk-video-audio-fc-logcat.txt

I installed the gapps and gtalk video work after my first reboot.

gTalk video doesn't work for me either... Hangouts work, even though they had a hard time starting to work, but eventually I was able to do a video conference, after some hangs and reboots...
The simplest of features don't work on android 4.x... I like the fluidity but this is starting to get irritating...

wucinac said:
I installed the gapps and gtalk video work after my first reboot.
Click to expand...
Click to collapse
what rom? BL? gapps?
Sent from my LG-P990 using xda app-developers app

LarsPT said:
gTalk video doesn't work for me either... Hangouts work, even though they had a hard time starting to work, but eventually I was able to do a video conference, after some hangs and reboots...
The simplest of features don't work on android 4.x... I like the fluidity but this is starting to get irritating...
Click to expand...
Click to collapse
hangouts worked with no issues for me.. but the gtalk fc's really start to irritate me as well, especially because it seems that for some it runs well, but dont know why. another BL issue then?
Sent from my LG-P990 using xda app-developers app

Ximo F. Verde said:
what rom? BL? gapps?
Sent from my LG-P990 using xda app-developers app
Click to expand...
Click to collapse
new bootloader, P.A. by tonyp, [email protected] kernel, gapps with gtalk video chat and JT Inverted Productions JusTunBean Inverted JB.
I flash this order and everything works ok.

it seems that it works on some new bl roms. anyone that got it workinh on the old bl? (or anyone that can figure out what went wrong on the logcat i posted a few posts above? had flashed the eos gapps .so file mentioned on p.1)
Sent from my LG-P990 using xda app-developers app

Here is my logcat of GTalk FC with suggested library http://pastebin.com/pX3hTBjB
UPD: seems i have fixed GTalk video...
You need to take from eos Talk.apk, libvideochat_jni.so, libvideochat_stabilize.so and check, if you have original /system/lib/hw/camera.tegra.so. If you experimented with ICS cam, camera.tegra.so possibly changed.

wfd said:
Here is my logcat of GTalk FC with suggested library http://pastebin.com/pX3hTBjB
UPD: seems i have fixed GTalk video...
You need to take from eos Talk.apk, libvideochat_jni.so, libvideochat_stabilize.so and check, if you have original /system/lib/hw/camera.tegra.so. If you experimented with ICS cam, camera.tegra.so possibly changed.
Click to expand...
Click to collapse
wow great news. Where did u push Talk.apk and libvideochat_stabilize.so? I havent flashed ICS cam, so i guess camera.tegra.so shouldn't need any changes.
EDIT: Nevermind, found them.

/system/app/Talk.apk
/system/lib/libvideochat_stabilize.so
Oh, and you should take libs from optional/noneon/lib folder in eos archive
Don't forget about permissions and owner (644 root:root)

wfd said:
/system/app/Talk.apk
/system/lib/libvideochat_stabilize.so
Oh, and you should take libs from optional/noneon/lib folder in eos archive
Don't forget about permissions and owner (644 root:root)
Click to expand...
Click to collapse
Sorry you've confused me a bit now. Take which libs from optional/noneon/lib folder? libvideochat_stabilize.so and libvideochat_jni.so only, isnt it? Because these files also exist in the EOS package in system/lib. And permissions/owner for which files?

Ximo F. Verde said:
Sorry you've confused me a bit now. Take which libs from optional/noneon/lib folder? libvideochat_stabilize.so and libvideochat_jni.so only, isnt it? Because these files also exist in the EOS package in system/lib. And permissions/owner for which files?
Click to expand...
Click to collapse
Cant seem to be able to change permissions/owner.. Can you tell me in detail how's you do that?

Download problems Xoom

OK I have been running team eos 3, build 155 fine for 2 months now. Lately I have started noticing that I can not save images, download files or some music in the stock browser or in chrome:crying:. If any of you guys could help me out with this, it would be great. Thanks. :good:

xda_biscuits said:
OK I have been running team eos 3, build 155 fine for 2 months now. Lately I have started noticing that I can not save images, download files or some music in the stock browser or in chrome:crying:. If any of you guys could help me out with this, it would be great. Thanks. :good:
Click to expand...
Click to collapse
Download a new image to you computer, copy it to a microsd card, boot to recovery, flash new image.

Thanks, but
mrmike328 said:
Download a new image to you computer, copy it to a microsd card, boot to recovery, flash new image.
Click to expand...
Click to collapse
Thank you for the reply, are you sure this is the only way and will I lose all my data.
PS: I'm kinda new at this so please don't mind all the questions.

xda_biscuits said:
OK I have been running team eos 3, build 155 fine for 2 months now. Lately I have started noticing that I can not save images, download files or some music in the stock browser or in chrome:crying:. If any of you guys could help me out with this, it would be great. Thanks. :good:
Click to expand...
Click to collapse
This is a really common problem on android. Happened with my xperia play and now happens with my RAZR m, and obviously on my Xoom too. I just go to "downloads" and keep "retry download" over and over until its successful.
Its just a pathetic bug in android I can't believe it still persists even on my brand new RAZR m. Such a joke.
Sent from my Xoom using xda app-developers app

I had the problem already, after a factory reset, it was back to normal

Thanks
Thanks everyone for all the reply's I really appreciate it.

[ROM[[P31XX] Stock 4.2.2 Debloated Deodexed Zipaligned

Removed

Reserved

Moar reserve

Screenshots

I'm gonna try this. Hope it works better. I'm not having any luck flashing the NEXT kernel and also have no phone audio using the "other" stock-based 4.2.2 (same problem as @ketut's Sammy-based 4.1.2)....

Ahhhh big job Luigi!! :beer:

Screenshots ?
I´ll hit "Thanks" tomorrow (Not able today: "Sorry, you are limited to 8 thanks per day")
You can also use https://www.file1.info/ for uploads.
Anonymous users can store files up to 1 GB and download files at a normal/slow speed. Registered users can store files up to 1.5 GB each, use 50 GB total and get higher speeds. Registration is free.
Click to expand...
Click to collapse

TabletUI patch?

rod555 said:
TabletUI patch?
Click to expand...
Click to collapse
Stock rom default is phablet ui ... btw maybe luigi help u ...
Sent from my GT-P3100 using xda premium

fooiskandar said:
Stock rom default is phablet ui ... btw maybe luigi help u ...
Sent from my GT-P3100 using xda premium
Click to expand...
Click to collapse
Not Tablet UI Patch yet.
Also @Android-Andi Screenshots! Yes! I forgot.
Edit: Screenshots added on post 4

Alright. I have a working phone remover. The deny signal is gone. The phone stuff is gone. Only problem is the device reboot when trying to bring up the power menu. So I guess we can't remove mobile data from the settings. Unless I or someone from here can figure something out. Anyways, now I''ll try to add flare effect and fix the mic and stuff.

Luigi2012SM64DS said:
Alright. I have a working phone remover. The deny signal is gone. The phone stuff is gone. Only problem is the device reboot when trying to bring up the power menu. So I guess we can't remove mobile data from the settings. Unless I or someone from here can figure something out. Anyways, now I''ll try to add flare effect and fix the mic and stuff.
Click to expand...
Click to collapse
Please try add ro.carrier=wifi-only to build.prop, NEXT kernel will stop 2 phone related daemon on boot.

Alright, I made my own version of the blackhawk 4 update annnnnnd... mic still doesn't work. @ketut.kumajaya. I think 4.2.2 uses some different files for mic.

Any error with sync app & calendar?

For me everything went well. Realy smooth and fast. But first time i tried to delete some of the things i don't use from system/apps(nothing that i don't usually delete) TW FCs....will try again with only freezing. Ty for your good work

Does swap sd work? thanks

Not working on 3100
on Booting the message "android.phone" has stopped and "android.gapps" has stopped pops every second. Cant even get through the setup process.
Procedure which i followed was from cm 10.1.2
Wipe data-> wipe cache->wipe dalvik->install rom->wipe cache->wipe dalvik and reboot.
going back to cm now.
Thanks.

I have the P3113 and simply go into systemui.apk and remove all signal icons. I also remove all the battery icons simply because I prefer the bat %. I know this does not remove the phone stuff itself but it does get rid of the icons in the Noti bar without any errors.
Not the best way but it works.

fast and smooth but i have an problem after flashing there is no gallery app

a1shakes said:
on Booting the message "android.phone" has stopped and "android.gapps" has stopped pops every second. Cant even get through the setup process.
Procedure which i followed was from cm 10.1.2
Wipe data-> wipe cache->wipe dalvik->install rom->wipe cache->wipe dalvik and reboot.
going back to cm now.
Thanks.
Click to expand...
Click to collapse
try formatting /system and /data before you flash the ROM (just be sure you have a nandroid backup, ofc ^_^)