[FIX] Wake Issue (Android OS) - Combination of Radio/PRI/NV/Wimax/GPS !Solved!

[FIX] Wake Issue (Android OS) - Combination of Radio/PRI/NV/Wimax/GPS !Solved! - EVO 4G Android Development

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thread has shed some light on new issues and some other fantastic developers have chimed in with a lot more insight into this issue than I had originally anticipated when I started this thread. Please read the below post in FULL, and skip to page 31 for where this discussion picks up. ~> http://forum.xda-developers.com/showthread.php?t=1128135&page=31
DaKlown said:
First I would like the thank the OP for bringing some attention to the issue. This thread seems to have started going in the wrong direction so I will make an attempt to clear some things up and shed some light on the situation with my findings. In my tests so far I cannot really find a combination of radios and pri to solve any of the problems mentioned in this thread. All my findings are using and testing aosp roms. Cm7 really but most aosp roms are based off of cm so this post should be helpful if you use an aosp rom and are having a unreleased pokelock caused by the dialer and/or high android system in the battery usage after phone calls. If you use a sense rom I do not recommend any of these fixes for you. If you use these on a sense rom you will probably mess something up and/or experience boot loops and lots of other problems. That being said lets get started:
Problem 1: The pokelock not being released after a phone call is made or received. This problem comes from the phone app and not the radios as far as I can tell from my tests.
Solution: http://www.mediafire.com/?xzw0zhonmnjw1xs
This file is a flashable zip of a new phone app that releases the wakelock after making a phone call the way its supposed to. I take no credit for this new phone app. It was made by Scott Brady (The same dev that fixed the mms problems on the evo in the cm nightlies about a month ago). I just got this from him. We haven't thoroughly tested it yet so please FLASH AT YOUR OWN RISK. Make a nandroid. I will say this though. In my current tests I have made about 40 calls with no pokelock and it seems to work wonderfully. The only reason I'm posting it early is because if you're like me and you know something is wrong then you want an immediate fix. Also using the killall command in terminal emulator or adb after every call can get tiresome... I have also tested with multiple radios In case anyone was wondering.
Problem 2: Android system spikes in the battery use in settings after a phone call is made or received.
Solution: I'm close but not finished yet...
Please read what I am about to say all the way through. What I have found is that the current proximity drivers for the evo are causing the android system in the battery use to go bonkers. I'm not really sure how much it affects your battery because it seems that it causes all your apps to not even show up in your battery stats. Proof? I have supplied two files in a zip:
http://www.mediafire.com/?mxks9k60shlckk5
THIS IS NOT A FLASHABLE ZIP. USE AT YOUR OWN RISK. One file is "sensors.supersonic.so" where I edited it so that android cannot find the drivers for your proximity sensor so it never comes on. The second file is "sensors.supersonic.so.bak" which is a backup of the original .so file that you can use if you want to turn your proximity back on. When I edited my sensors.supersonic.so file so the proximity wouldn't come on android system no longer spiked in my battery stats after a phone call!!! Also I tried to add a command to the build.prop first to disable the proximity sensor which would have been better practice but the command didn't work. Not sure if that's because cm overrides it or what. I can pretty much guarantee that this is an aosp problem and not a sense problem so if you use a sense rom you don't even need to worry about this. I doubt HTC has faulty proximity drivers on a stock rom... I could be wrong but I doubt it, they have screwed up in the past...
So what now? Well if you're on an aosp rom and the current proximity drivers work for you then you know what they say, "If it ain't broke don't try to fix it." For the rest of us I am in the process of trying to find some proximity drivers that don't make battery stats go haywire. Lets try to keep the thread relevant to findings so that we as a community can come closer to a fix instead of all the repetitive questions and things that don't help us get closer to a true fix... Don't forget the thanks button if you found this useful =P
Thanks for your time.
Edit: I would also like to add that I am on the most current radios, nv, and pri with no wakelock or spike in my android stats. And If you flashed the combo from the Calkulin thread you are probably missing the newest NV file because its not in there.
Click to expand...
Click to collapse
I have left the previous OP in-tact so if you would like to follow from the beginning you may. At this time, I can no longer recommend the below steps!!!, but I can still let you know that the GPS driver files below are pretty damned awesome.
~J
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
I believe I have FINALLY figured out how to solve the infamous "Wake-Lock" or "Keep Awake" of Android OS that seems to drain the battery on end. It took several hours of reading forum posts, several DAYS of testing on 5 different EVO's (I work at Sprint) and have tested the fix across a multitude of ROM's, including Sense.
I will post a short history of the issue as I know it here for those of you hitting this thread for the first time, skip below for the solution I have found.
Requirements:
-Radio S-OFF
-AmonRA Custom Recovery
-Android System always at or near the top in your battery usage
History
To the best of my knowledge the issue first started to appear in AOSP ROMS when the Cyanogen team stopped using HTC Blobs to control the driver for the GPS, As a great many custom roms utilize cyanogen for many of their own enhancements and fixes the problem began to propagate out to the community at an alarming rate. Restoring your system back was a hit or miss on if it actually solved the issue or not, and more RADIO files were getting leaked/posted online and many people were flashing a multitude of firmwares to their handset making the issue confusing and seemingly with no correlation on handsets with the people having issues.
I came across ViRuS Kingdom ROM and read about 1000 pages of posts and the conclusion from their team was that the PRI needed to be downgraded to 1.77 and behold, it worked......(mostly)......
I wondered how the PRI had anything to do with the fix, and mixed that with many, many other forums I have read on the issue realized myself that there was a correlative cause and that we all did indeed have something in common. Everyone was on a different radio/pri/nv/wimax combination. I decided to run some tests myself as I have access to ****loads of handsets being a Sprint employee and here is what I have found.
I have found exactly 1 combination that has fixed the issue on every single handset I have tried it on, hands down across the board on a great cross-section of ROMS.
-Cyanogen
-Kingdom
-MIUI
-SavagedZen
-Synergy
-Mik's
-Sense 3.7 build
-Sense 4.22 build
-FreshEVO 3.5
-FreshEVO 4.1
______________________________________________________________
THE FIX!
The fix is a combination of...
Radio: 2.15.00.05.02
PRI: 1.77_003
NV: 1.90_003
WiMAX: 27243
GPS: HTC VISION GPS ".so" file
-Download the below PC36IMG.zip It is a custom Combo Radio installation I created that will set your Radio/Pri/NV/WiMAX to the above settings
-Move the PC36IMG.zip file to the root of your SD-Card and reboot the phone into bootloader. It will load the file and prompt you for an update, you will see on the left 3 items that will be upgraded on your handset. Hit volume up to accept
-Reboot the phone after the Radio update, go ahead and remove the PC36IMG.zip file from the sd-card and put it in a safe place
-Download "GPS_FIX_Flashable_Vision.zip" and put on your SD-Card
-Reboot into Recovery (I highly recommend AmonRA 2.3)
-Wipe Cache & Dalvik Cache. Now wipe them again just to be safe
-Choose "Install zip file from SDCard"
-Navigate to GPS_FIX_Flashable_Vision.zip and choose install
-Once installed go down to "Other" and "Fix UID mismatches"
-Reboot the phone
______________________________________________________________
Now heres the weird and tricky part so listen closely. At this time you will still see the Android System in your battery stats. This is normal. To see the fix, you need to charge your phone fully to 100%.... and honestly give it an extra 10-15m on the charger after it says its full. Now..... REBOOT the phone when you pull it off the charger. Use the phone a little bit, make a phone call... it may still pop up around 5%.... again this is normal..... after 2-3 hours however it will be gone, completely and utterly gone... it will never show up again.
I have tested this on 5 handsets hardware revision 0002 0003 & 0004, and about 6-7 ROMS both AOSP & Sense and have yet to see Android OS re-appear. This is not to say that it will work for everyone, but I think that after my testing, there's an excellent chance that this will work for you.
Please leave feedback if this works or does not work for you please so that everyone can benefit from your experience, either good or bad. Please, please please, follow the final instructions carefully, it does literally take a few hours to test and get the old stat to wipe from the battery history, that is why I started this, literally 2 weeks ago, and am just posting now. I tried TONS of combination's and this is the one that struck gold, then I needed to test this combination on all of the phones I had sitting in the back for this. If mirrors are needed please let me know, and I will upload.
Good Luck!
PC36IMG.zip
Radio: 2.15.00.05.02
PRI: 1.77_003
NV: 1.90_003
WiMAX: 27243
http://www.multiupload.com/HJOWHOLW4G
Qualcomm Vision GPS Driver
Sense GPS Driver File from Qualcomm Vision
http://www.multiupload.com/11IWQ99VKH
EDIT:
A few reports on certain ROMS of excessive CPU usage after Android OS has dropped off the list
Please use one of the two below GPS drivers if you experience 100% CPU usage (Source: http://forum.xda-developers.com/showthread.php?t=1132412 )
~>AOSP<~
CyanogenMOD 7 Nightly 39 GPS Driver (HTC Blob File Compiled)
http://www.multiupload.com/NIJEKWGDEQ
~>SENSE<~
KingdomROM GPS Driver FIX
Sense GPS Driver File from EVO 3D aka "Kingdom"
http://www.multiupload.com/ZMOXSDJBOE
EDIT: It has come to my attention from a few members in PM, that the issue doesn't always "take" right away. People have reported that it can take 2 or 3 attempts, and 9 different people have reported that they have run the 1.77_003 NV after flashing the radio, and then running the GPS to resolve the issue.
---------------If the above fails for you after a 2nd attempt. Please follow these Modified Instructions
-Download the below PC36IMG.zip It is a custom Combo Radio installation I created that will set your Radio/Pri/NV/WiMAX to the above settings
-Move the PC36IMG.zip file to the root of your SD-Card and reboot the phone into bootloader. It will load the file and prompt you for an update, you will see on the left 3 items that will be upgraded on your handset. Hit volume up to accept
-Reboot the phone after the Radio update, go ahead and remove the PC36IMG.zip file from the sd-card and put it in a safe place
-Download "GPS_FIX_Flashable_Vision.zip" and put on your SD-Card
--MODIFIED STEP-- Download "EVO_NV_1.77_003" ~> http://www.mediafire.com/file/i1p436188iw0iqb/EVO_NV_1.77_003.zip (source: http://forum.xda-developers.com/showthread.php?t=715485) & put the file on your SD-Card
-Reboot into Recovery (I highly recommend AmonRA 2.3)
-Wipe Cache & Dalvik Cache. Now wipe them again just to be safe
-Choose "Install zip file from SDCard"
--MODIFIED STEP-- Navigate to EVO_NV_1.77_003.zip and choose install, once installed you will see a note at the bottom to reboot the phone. Choose the "Reboot Phone" option in AmonRA and let the phone reboot
-You will see the screen blink, go into recovery and hang, this is completely normal, just wait about 30 seconds and the phone will Automatically put you back into your recovery
-Choose option Flash zip file from SD-Card
-Navigate to GPS_FIX_Flashable_Vision.zip and choose install
-Once installed go down to "Other" and "Fix UID mismatches"
-Reboot the phone
Pickup the rest of the steps from above. PLEASE REPORT back your experience!
++++++++++++++++++++++++++++

wow sounds like it could work but im too busy with work...hopefully this thread will get more people to try this fix and see if it works for them....my fingers are definitely crossed!

thanks for this.. i will try it out.. i currently allready have the 1.77 on my phone.. dont know bout the radios.. last time i tried to flash radios i had net closing issues..

dgrobe2112 said:
thanks for this.. i will try it out.. i currently allready have the 1.77 on my phone.. dont know bout the radios.. last time i tried to flash radios i had net closing issues..
Click to expand...
Click to collapse
I have had issues like this as well, but only when I do the radio's through the recovery partition. That is why I enclosed it as a PC36IMG.zip file so that it could be done by the "official" HTC update method. I have had no issues doing it this way. Good luck, looking forward to hearing that your issue is resolved.

Fails to install Can't find update script... any ideas??
CM7.0.3.1

JBabey said:
I have had issues like this as well, but only when I do the radio's through the recovery partition. That is why I enclosed it as a PC36IMG.zip file so that it could be done by the "official" HTC update method. I have had no issues doing it this way. Good luck, looking forward to hearing that your issue is resolved.
Click to expand...
Click to collapse
i dont have to reflash my rom do i?

downloading now, should i clear battery stats?

glennpettit said:
Fails to install Can't find update script... any ideas??
CM7.0.3.1
Click to expand...
Click to collapse
Use AmonRA, the update script is not in EDIFY (I may have to fix that later)
downloading now, should i clear battery stats?
Click to expand...
Click to collapse
You shouldn't need to. If you are clearing your battery stats, do that for the reasons its intended, and make sure you follow the top off/drain instructions when doing so or it could lead to false readings.
i dont have to reflash my rom do i?
Click to expand...
Click to collapse
No, you are only updating your radio and thus will not lose your data or have to reflash your ROM. Please remember to follow the short instructions at the end for charging/reboot/2 hours before reporting back here please.

flash the virus gps fix even if your not on the kingdom rom ?

I am using RA.

might give this a shot later, don't have high android OS, but might be interesting none the less

glennpettit said:
I am using RA.
Click to expand...
Click to collapse
I re-uploaded the zip file, please redownload and lemme know if this one works for you.
Thanks!
might give this a shot later, don't have high android OS, but might be interesting none the less
Click to expand...
Click to collapse
If it aint broke..... lol (granted this will put you on the latest radio)
And.. I have found my GPS locks to be instantaneous on this driver.
flash the virus gps fix even if your not on the kingdom rom ?
Click to expand...
Click to collapse
I personally use CyanogenMOD Nightly 100 at the moment and it works like gangbusters on this ROM.

CheesyNutz said:
flash the virus gps fix even if your not on the kingdom rom ?
Click to expand...
Click to collapse
I used the GPS drivers provided by Vaelpak...and it worked! I'm using Salvage-Mod v1.2.1 GB 2.3.3 and my GPS pickup is now instant!
And to the OP, I haven't had this issue...but great work!!!

What is acceptable for Android System usage? I'm at 23% right now and it's third on my list behind Cell Standby and Phone Idle. Is 23% high? I know I've seen it higher before. I am interested to hear more feedback on this fix.

I assume when flashing a new nightly, I would need to reflash the GPS driver again?

That's not even the problem for me, I'm on hardware 4 and with any of the 2.3.3 Roms the highest thing draining my battery is the display any ideas on how to reduce that. It's between 50%-right now at 86%. I have turned off auto display and notifications. Thanks in advance for any help.
Sent from my PC36100 using XDA Premium App

I had major issues with bat life and wake (android system) after flashing calkulins radiosfrom the ota 4.2.2 release. I downgraded radios to
Baseband 11.19
Pri 1.77
NV 1.77
Wimax 27167
Still have issues though. Is it safe to flash radios that many times. I have heard it can scree stuff up so should I flash your combo. Also my GPS works fine using cm 7.0.3.1 do I stool need to flash your GPS fix.
Cm 7.0.3.1
Sz 2.1.0 Cfs havs sbc
V0003

I did this for the hell of it even though I wasn't having too many issues on Virus revo 1.3 however this fixed my intermittent wifi issue and seems to have improved my battery too. Thanks a lot

Flashing it now while I'm at work (its slow today)

i am finished with the install of the zips, and rebooting now.. you said 2 hours.. i will post back my findings.. to let you know what is going on..
also.. as others have mentioned.. i havent been having any issues with the kingdom revo 1.3 rom.. other than battery drainage.. i dont have wake issues.. but wanted to see if this fixes anything.. will give updates..

Related

[ROM] MghtyMax 1.9.1 "WHAT A FEELING!"

MghtyMax 1.9.1 "What a Feeling"
SIGNED VERSION NOW LIVE!!!!
THIS IS A CUPCAKE HERO ROM. AT PRESENT 1.9.1 IS STILL THE LATEST VERSION OF MGHTYMAX. IN MY OPINION, STILL THE FASTEST, MOST STABLE HERO ROM ON THE PLANET.
***NEWS***
I may be developing a "Legacy Edition" of MghtyMax, considering we are reaching the end of the road for the G1. It would essentially be 1.9.1 with minor tweeks, some graphical improvements, and some special goodies to celebrate life of a great phone. Kind of in the "feeling out interest" phase right now, so if this is something you would like to see, please respond. I'd also like to talk to some folks who are good with custom desktop wallpapers. Please contact me on Twitter if interested in working on this project.
Changelog:
1.9.1 - Added Flash support
1.9 Altered user.conf. Turned off Compache and went to straight linux-swap. Swappiness set at 60. This may be the FASTEST HERO ROM EVER.
Recommended linux-swap partition sizes:
G1: 128 MB Linux Swap
MT3G: 96 MB Linux Swap* (Not tested. If running laggy after rom settles try 128MB as well)
If you get the blurries on MT3G, use the blurries fix:
http://twistedumbrella.slackdev.com/Deport-1.0.zip
After the system settles, and everything is running nice and smoothly, shut down, reboot into recovery and flash this as a ROM. Don't wipe, don't remove partitions. Just flash the zip. Reboot, and no more blurries!
1.8:
*This IS Maxisma 1.8 with the following changes:
Brought back PEEP due to popular demand (as is in Maxisma's roms)
Include Backup for Root & Missed Calls apps, and a few added sounds.
Modded build.prop to allow use of T-Mo apps (My Account, My Faves)
1.7.1a:
Removed HeroLED. All LED's will work natively on MT3G, and on G1 all will work except *missed call notifications. Thanks to Maxisma's build.prop
*Included Anon's Missed Call. Allows for custom LED color and frequency for incoming/missed call notification, and missed call notification sounds. This app will be in your app draw, and it must be run and set up for missed call notification LEDs to work. MT3G users do not need to use this app.
Included Blackgin's "Backup for Root Users" (This version works with HERO rom's)
Added lots of sound files for Ringtones, Notifications, and Alarm.
This version has an edited build.prop so that the phone's model number displays as T-Mobile G1 for apps like T-Mobile's "My Account" Although this has not been tested on MT3G it should not cause any issues. Please report if there are and I will release a MT3G version of this rom.
Replaced boot sound and image files.
Removed HTC PEEP. (was causing problems for me, lots of FC)
Thanks go out to Maxisma of course for compiling the rom that I basically just tweeked a bit, and for allowing me to share it with all of you. Anon for his Missed Call app, Blackgin for "Backup for Root Users", HTCPedia and Rapidshare for hosting, everyone at XDA and the T-Mobile forums, JackCrackerMan for pointing me to the blurry fix, and of course all of you, the Android community at large.
***BEFORE INSTALLING PLEASE***
***THESE INSTRUCTIONS MUST BE FOLLOWED TO THE LETTER OR MGHTYMAX WILL NOT WORK!!!***
-If using "Backup for Root" uninstall any heroled app you may be currently running before backing up.
-Before flashing this rom, WIPE PHONE/FACTORY DATA RESET, WIPE/REPARTITION EXT AND LINUX-SWAP in parted.(I recommend ext4 for best performance, 128MB Linux Swap for G1, 96 MB Linux Swap for MT3G)
-After repartition and upgrade of ext partition, exit parted and PULL BATTERY. Make sure device is not charging or hooked up to USB and put battery back in and boot to recovery.
-WIPE/FDR Phone AGAIN FOR SAFETY. Too many people having issues with remnants of old roms interfering with new ones. PLEASE follow this procedure exactly.
- Flash Rom.
-When the new rom boots and you get to the homescreen, allow some time for the apps2sd to catch up.
- IMPORTANT!!! Run Market. Accept the ToS. Exit Market.
- Run "Backup for root users" (also in app tray) if you ran it prior to flashing this rom, and restore your files.
- Wait. Wait. Wait. Sit and watch the apps pop up in the tray. Wait some more. Look, they're dancing! They keep moving! Wait. Wait. Wait. Grass growing? Wait. Wait Wait. Wait some more and when they finally stop moving around for good, close the app tray and reopen it. If it scrolls like butter, it's done. If it's laggy, wait, wait, wait. DO NOT RUN **ANYTHING** During this process!!! You may get FC's, load screens, and just may end up doing a wipe and reflash. Give it time. It will take a while, but you'll be glad when it's done.
- Run "Missed Calls" app in the app tray and set up your led notifications for missed/incoming calls.
Feedback/suggestions appreciated!
*As with any rom, you flash this at your own risk, neither I, Maxisma, these forums, your wireless carrier, or any being, living or dead in the known universe (except for you) will be held responsible should your damage or destroy your device in an attempt to flash/use this rom in any way.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
MghtyMax 1.9.1 "What a Feeling!" ---> http://htcpedia.com/forum/showthread.php?t=918
Just in case folks prefer the RAMHack for some reason, 1.7.1a is still available for download.
MghtyMax 1.7.1a --->http://htcpedia.com/forum/showthread.php?t=918
"Just when I thought I was out... THEY PULL ME BACK IN!!!"
I just couldn't let 1.8 be it, with the problems I was seeing with lag. I am very proud of 1.9, and think it just may be the fastest Hero Rom setup yet. I hope you think so too. Thank you again for your support!
Please share your thoughts/comments on this topic here, or to my twitter at http://twitter.com/mghtyred
Thank you all again for enjoying this ROM!

Finally My First Post!!!!
This Seems Amazing, I'll Try This Out

anybody try it out yet? how is it?

going to give this a try brb

Since its a hero rom im guessing we will need a class 6 sd card right?

[email protected]@ said:
Since its a hero rom im guessing we will need a class 6 sd card right?
Click to expand...
Click to collapse
Because of the memhack Maxisma is using in the rom, no it's not required since linux-swap isn't really used, but recommended for faster app loading in apps2sd.

Working Great for me so far!
No FC's at all on the Mytouch.
Only one FC i got so far was the one when you search for a Contact, but mighty is already aware of that.
Other than that no problems so far.

Using it on the G1 and it blazing fast and holy sh** the LEDS work amazing!
Way to go Maxisma and Mighty!

If I'm coming from Max 1.7.1 do I need to wipe before flashing on my mt3g?

i followed directions and it boots up to mighty max screen and keeps booting to that same page. what next?

rizoh66 said:
If I'm coming from Max 1.7.1 do I need to wipe before flashing on my mt3g?
Click to expand...
Click to collapse
Absolutely. Follow the instructions to the T.

badaphooko01 said:
i followed directions and it boots up to mighty max screen and keeps booting to that same page. what next?
Click to expand...
Click to collapse
Clarification needed:
Are you getting a boot loop? Hero->HTC->MghtyMax->Hero->HTC->MghtyMax- etc,etc?
Or are you stuck on the MghtyMax screen?

mghtyred said:
Clarification needed:
Are you getting a boot loop? Hero->HTC->MghtyMax->Hero->HTC->MghtyMax- etc,etc?
Or are you stuck on the MghtyMax screen?
Click to expand...
Click to collapse
im sorry yes, its a boot loop

im wiping again and reflashing

Make all of this fit in 90 MB (death spl system) and I'll be impressed. I'll give it a try, though, maybe this one's worth my while, but the back of my mind is saying "Meh, another hero...)...

ok, let me tell you what steps i took before i flashed.
1.using Ra recovery. I wiped ext2 part
2. wiped/reset
3.repartioned fat/ext2/linux swap
4.upgraded to ext3
5.rebooted to g1 screen
6.pulled battery and removed sd card
7.copied rom to sd card
8.booted into recovery
9.wiped again
10.flashed rom
11.stuck in "might max" boot loop

mghtyred said:
Absolutely. Follow the instructions to the T.
Click to expand...
Click to collapse
Im sorry, I have one more question. Do I still need to partition my sd if im on the mt3g?

badaphooko01 said:
ok, let me tell you what steps i took before i flashed.
1.using Ra recovery. I wiped ext2 part
2. wiped/reset
3.repartioned fat/ext2/linux swap
4.upgraded to ext3
5.rebooted to g1 screen
6.pulled battery and removed sd card
7.copied rom to sd card
8.booted into recovery
9.wiped again
10.flashed rom
11.stuck in "might max" boot loop
Click to expand...
Click to collapse
Wow. That's your problem. Try it again using my EXACT process. I mean EXACT. If you do it EXACTLY as I posted it, you will have no problems. Start from the beginning and do it again.

rizoh66 said:
Im sorry, I have one more question. Do I still need to partition my sd if im on the mt3g?
Click to expand...
Click to collapse
As mentioned previously in the first post, in order for this rom to work on your phone, you need to follow the instructions I posted TO THE LETTER.
Yes you still need to partition your SD.
Read above to see what happens when you don't do exactly what is posted.

I have an extra 1GB class 2 or 4? SD card that I can use for this. And I want
to try it but I'm wondering.. is it good to be used as a daily driver? Is it as fast
or almost as fast as CM?

CM7MTD 06/20 Release - [Mesmerize]

I've made a few edits to jt1134's 06/20 build of fascinate CM7MTD (which has working GPS!!) to get it working on our radio (EE19 or EC10, your choice) and have uploaded this for others to use. I'm not going to create a release thread of any kind yet as jt is working on getting all 3 of our phones supported officially by CM after he finishes a painstaking process of rewriting sensor drivers (that will mean all hardware will be working, then mms will be looked at). And lmartin92/jt will be able to get us native builds after that happens.
Please visit this thread to make sure you click his thanks and/or throw jt a little money, if it weren't for him alone we would probably never see the merging into mainline CM7!
This release is as is and we're not needing any bug reports at this time.
Note: It will also say Verizon wireless as your service provider, but that's just because I didn't edit the eri.xml file within framework-res.apk
jt1134 said:
Here is a test build/preview of the 2.6.35 MTD CM7 port for Fascinate. It is built off the work of TeamHacksung, and is very different from earlier CM7 builds. At this point it is very functional, but still in very much of an ALPHA state.
Working:
Calls!!
Bluetooth!!
3G data
WiFi
SMS
Camera/Camcorder
USB mass storage / sdcard
Sensors (accelerometer / compass)
GPS!!
Not Working:
MMS
light and proximity sensors
Included in the package is the base ROM and kernel. GAPPS must be flashed separately. Link below. You may also use nemesis2all's kernel here : http://forum.xda-developers.com/showthread.php?t=1119169
When flashed the first time, your filesystems will be converted to MTD (yaffs2/ext4). Do not try to flash any other ROMs via cwm at that point, and do not try to get into recovery via the 3 button method. Use adb reboot recovery or the reboot recovery option from the power menu. To revert, and switch to another ROM, flash a full Odin/Heimdall package (like DL09).
Since your filesystems are being fully converted, there is no need for Voodoo or any other lagfix. DO NOT TRY TO INSTALL ANY KIND OF LAGFIX ON THIS ROM!!! Voodoo sound capability is however included in the kernel.
To install, boot into cwm recovery, wipe data, and flash the ROM. It will reboot and the do the actual install. If you are on a previous version, you can simply flash it over your curren install. If you have problems, try wiping data first. The ROM will work whether you are on rfs or ext4.
*** Update 06/09 ***
fixed in-call audio
fixed bluetooth in-call audio
*** Update 06/20 ***
fixed GPS
re-enabled backlight notifications (you DO NOT need BLN control app)
disabled (broken) auto-brightness
other misc changes, see my github
This is a WiP, and meant as more of a preview than anything else. If you enjoy it, click the Thanks button. Enjoy
http://goo-inside.me/gapps/gapps-gb-20110613-signed.zip - GAPPS
Click to expand...
Click to collapse
Download link: Click Here

bd, shouldn't this thread be in the development forum for the Mes???

Snyperx said:
bd, shouldn't this thread be in the development forum for the Mes???
Click to expand...
Click to collapse
Could be, but I don't consider it development since this build is temporary until we get a native one built. (I didn't want to post another thread in there since lmartin already has one started and would simply update it once it's done.)

When you say native. Does that mean a build done specificly for mesmerize. In which most everything will be working. Sorry just trying to make sure I understand the lingo
Tap-a-Talked from my Mesmerize

Is this only for the Mes or is it safe for Showcase?

scarmon25 said:
When you say native. Does that mean a build done specificly for mesmerize. In which most everything will be working. Sorry just trying to make sure I understand the lingo
Tap-a-Talked from my Mesmerize
Click to expand...
Click to collapse
When I say native build, I mean that it's built from source with the appropriate uscc/cellular south edits made pre-build - instead of making a few edits post-build like I've done here with this release. Jt has repos on github for both the mesmerize and showcase but they weren't updated yet so we couldn't build it. When he does (after he get's sensor drivers rewritten) then he will either build it or lmartin92 willl and we'll update the thread in the dev forum. This is just to hold people over until then Regardless of whether it's built native or kang'd like I did here, it's still as functional as listed in the OP - but building natively is the better practice and guarantee of no bugs.
StuckinMemphis said:
Is this only for the Mes or is it safe for Showcase?
Click to expand...
Click to collapse
No sorry, I still have yet to learn exactly what changes are required to make it work for CS, so this is only for the mesmerize.

Cool deal. Thanks for clearing that up for me. Man I wish I had your guys inteligence when it comes to this stuff. It amazes me how you do what you do. I will be lookin for it as honestly that has been my reason for holding off on cyanogen. Waiting for it to get more functional which looks like it is now thanks to JT and the others. You all rock and thanks for all you guys do.
Tap-a-Talked from my Mesmerize

scarmon25 said:
Cool deal. Thanks for clearing that up for me. Man I wish I had your guys inteligence when it comes to this stuff. It amazes me how you do what you do. I will be lookin for it as honestly that has been my reason for holding off on cyanogen. Waiting for it to get more functional which looks like it is now thanks to JT and the others. You all rock and thanks for all you guys do.
Tap-a-Talked from my Mesmerize
Click to expand...
Click to collapse
No problem, glad to share knowledge when I can . At first I felt the same way, it was very overwhelming and I never thought I'd be able to actually get involved with bringing things to the community, but the more you hang out in IRC the more brave you get and once you start cracking open .apk's and get the basics down, it becomes fairly easy to learn and progress . Especially when you have brains to pick like jt1134/phidelt82/jamezelle (to name only a few)!

Alright, so I tried to flash this on CWM 3 (I was on Heinz 57 EE19 build before this), and I got an error almost immediately, saying "asset failed", along with a bunch of stuff regarding the Fascinate. I did wipe data and all that, so I'm wondering what I'm doing wrong. I would really like to try this out!

btoast777 said:
Alright, so I tried to flash this on CWM 3 (I was on Heinz 57 EE19 build before this), and I got an error almost immediately, saying "asset failed", along with a bunch of stuff regarding the Fascinate. I did wipe data and all that, so I'm wondering what I'm doing wrong. I would really like to try this out!
Click to expand...
Click to collapse
Can you be more specific on the "stuff regarding the Fascinate" ? I haven't come a crossed this issue, basically it should reboot as soon as you hit "install .zip" to a CM7 splash screen and then it'll go right back into CWM, finish the install then reboot a few more times before it actually boots up.
EDIT:
Okay someone else just had this happen, he was in EE19 H57 as you were, so I'm thinking that's the cause - I went from EE19 PNP to Cm7MTD with no issue. I'm looking into it further but for now it seems you need to be coming from a rom other than H57.
Here is a screenshot;
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Okay, here's what it says (and sorry, I meant assert ).
assert failed: getprop("ro.product.device") =="aries"|| getprop("ro.build.product") =="aries"||getprop("ro.product.board") =="aries"||
These lines are repeated 3 more times, but instead of "aries", it is "fascinate", "fascinatemtd", and then "SCH-I500".
By the way, this is all on the recovery screen, it doesn't reboot at all.
EDIT: Just read your edit, haha. Alright, so I just flash some other ROM like PnP first and I'm all good? Cool, I'll try it and let you know

btoast777 said:
Okay, here's what it says (and sorry, I meant assert ).
assert failed: getprop("ro.product.device") =="aries"|| getprop("ro.build.product") =="aries"||getprop("ro.product.board") =="aries"||
These lines are repeated 3 more times, but instead of "aries", it is "fascinate", "fascinatemtd", and then "SCH-I500".
By the way, this is all on the recovery screen, it doesn't reboot at all.
EDIT: Just read your edit, haha. Alright, so I just flash some other ROM like PnP first and I'm all good? Cool, I'll try it and let you know
Click to expand...
Click to collapse
I would think you could flash pnp then go from there but to be safe you might just want to flash full EE19 stock then CM7
EDIT: Okay, scratch that last. I'm re uploading with a working version (same link). It should finish in 10 minutes or so.

Yeah, just flashed PnP and then tried CM7, but I got the same error...well, looks like I'll have to wait until I get back home to my computer this weekend and ODIN back to stock and try again.
EDIT: Wow, I have to stop posting before your edits, haha. Sounds good, I'll try the updated one in a few, then!

btoast777 said:
Yeah, just flashed PnP and then tried CM7, but I got the same error...well, looks like I'll have to wait until I get back home to my computer this weekend and ODIN back to stock and try again.
EDIT: Wow, I have to stop posting before your edits, haha. Sounds good, I'll try the updated one in a few, then!
Click to expand...
Click to collapse
No worries , please let me know how it goes! (it's all uploaded and available now)

bdemartino said:
No worries , please let me know how it goes! (it's all uploaded and available now)
Click to expand...
Click to collapse
So I clicked the download link and I get a notice saying the "content is not supported for the phone", the file is called Unknown and it won't download. Do I need to download from a PC now?

btoast777 said:
So I clicked the download link and I get a notice saying the "content is not supported for the phone", the file is called Unknown and it won't download. Do I need to download from a PC now?
Click to expand...
Click to collapse
I just deleted the old one and reuploaded with the same name, so it should be fine.
try going to http://olvisfoundation.com/xdadump/bdemartino/
Then click on the CM7.zip there

So, turns out I had to re-download the Dolphin browser in order to download it. Good news, CM7 installed successfully on my phone! However, later when I rebooted in order to add the GAPPS, I lost service; my phone couldn't even identify what network it was on and all that. So, I had to borrow a friend's computer and I ODIN-ed back to stock EE19. I'll try it again and see if I can get data working, but if you know anything about that, let me know! I'm getting closer...
EDIT: Alright, so I tried to flash again after getting back to stock, and this time when I rebooted to install the GAPPS, I got stuck in a boot loop with the CyanogenMod animation. So, I've restored my backup and am back on Heinz 57 for now. So I don't know if I'm just not supposed to flash the google apps or if this version only wants to run one time before something happens :/. Do you have any idea?

I had lost data too, so I pulled the battery and rebooted it's been good since.

Ya I had an issue with signal at one point, I toggled airplane mode on and off and it fixed it right up haven't had issues since, but haven't had any issues with data.
You do need gapps, so I'm not sure what the issue is - make sure you download the ones from jt's post.

Yeah, I don't know what was going on...I'm going to try flashing it again, and I'll see what happens.

[ROM] Alien Stock ★ UCLE2 ★ Deodex/Zipalign/Busybox/Root ★ 5/18

Coming soon (its stock, what do you expect?)

Changelog:
Alien Stock UCLE2
Updated to UCLE2 leak.
Alien Stock UCLD2 re-release
Fixed busybox. No one told me it was broken.
Properly format /system, /data and /cache using Samsung provided tools.
Alien Stock UCLD2
Updated to the UCLD2 leak.
Few minor bugs fixed. I don't think they affected ROM usage, but never hurts to be thorough.
Alien Stock UCALC4
Initial ICS leak.
Known issues:
The home button has a slight delay. This is common in ICS (check SGS2 for example).
[*]Messages crashes if you delete a thread from the list view. This is a problem with the leak. Maybe I'll fix it if I get time.
Anything else that has been common with ICS from Odin (I really haven't noticed hardly anything to be honest).
If installed properly, this will not have the lag, data connection issues, etc of other CWM stock releases.
Some people have noticed weirdness when coming from GB related to the Home/Search keys. This appears to be related to updating from GB only (perhaps files on the SD card). Flashing the ROM a few times and booting into it between each flash seems to clear this up. Alternately, try backing up your internal SD card to your PC and then formatting it.
Miscellaneous:
If you want to enable "Preferred install location" in Settings -> Applications, run the following through an ADB shell and reboot:
Code:
sqlite3 /data/data/com.android.providers.settings/databases/settings.db 'update system set value="1" where name="set_install_location";'

I love you.

nice!!!!!!

Nice, been waiting for this one. Screen shots are coming I assume? Can this be used on 727R's (Rogers)?

veebomb said:
Nice, been waiting for this one. Screen shots are coming I assume? Can this be used on 727R's (Rogers)?
Click to expand...
Click to collapse
Granted, I was still fleshing out the post, so maybe it wasn't there yet. But please check Help in the first post.
Short answer, I don't know. I'm an AT&T subscriber But if the ICS leak worked on Rogers, then this should too. The beauty of this release is really in the updater-script

I got an aborted install...Im gonna try to download again and flash.

mossination said:
I got an aborted install...Im gonna try to download again and flash.
Click to expand...
Click to collapse
MD5 should be 3764ce5059fd5174e4840960b0fa43cd

Downloading now
Munching on Ice Cream with XDA Premium

Installed fine. Need me to take screens, just ask. Thanks so much for this.

The Vol Down + Power has yet to work for me (for screenshots)... Nvm, you have to hold the buttons down.
ROM is good though. May I suggest adding the dictionary fix for the next go-'round?

MokujinX5 said:
The Vol Down + Power has yet to work for me (for screenshots)... Nvm, you have to hold the buttons down.
ROM is good though. May I suggest adding the dictionary fix for the next go-'round?
Click to expand...
Click to collapse
I'd say save that for Alien ICS, we need a good base around here. i Remember the first Alien back in November..first ROM i used.
EDIT: Donated...thanks romracer.

In case you need them.

So far so good. Smoother than the others so far. Had the home button bug. Reflashed and all is good. Thanks for all the work

mossination said:
In case you need them.
Click to expand...
Click to collapse
Thanks, I'll put them up in the morning. One of my dogs ripped the skin off her lower jaw ("degloved the lower mandible") shortly after I posted this. Been a long night; surgery in the morning. Thanks for taking those SS.

First, I hope your dog is OK, I am a dog lover as well.
Ok, this might be a bit lengthy, but I've just spent 10 + hours trying different things and I want to let you know what all happened in hopes that the info can be used to help make Alien ICS one of the greatest ICS ROMS ever. Alot of this is already known, but I'll cover it anyway. And, of course, this is the experience I had with my phone...others may differ.
Background. I ODIN'd the ICS leak already, but found it buggy, bad connectivity, and a battery hog, so I went back to ALien 6 (GB).
I saw this posted and decided to give it another go. I followed the directions and didn't have any trouble with the actual install precedures themselves. However:
The first time I flashed the ROM, I found that I had the problem with the "Home an search" keys not working as well as the "shutdown and reboot" hanging. I tried to do a factory reset in the settings, but it wouldn't work. So I did another clean install of the ROM using the superwipe script this time as well.
The 2nd install fixed the "Home and Search" buttons, but I still had the "shutdown and reboot" hang. I fixed permissions, re-downloaded busybox and installed your insecure kernel and the 14 toggle mod. Nothing fixed it. SO, I did a 3rd clean install.
The 3rd time seemed to do the trick. Home and search buttons work,shutdown and reboot works, the 14 toggle mod works, etc. and, this time around everything seems alot more responsive and snappy.
Here is what I noticed:
All three install attempts (and the ODIN leak install) acted different in some ways that were suttle and others obvious. It appears to be hit or miss on any install and any method that is based on the ICS leak. I'm not sure why this is. But I am certain that reguardless of install method, it might take the way it is supposed to the first time, it might take 3 flashes or it might take 10 or more tries. It's just the luck of the draw. The fixes that people have reported as working are only temporary. That's why they work for some and not for others. It might make a certain aspect work (ie. installing a program makes shutdown work) but your ROM will still not be installed correctly. The only way to get it to work right is to keep trying until it installs with everything working, otherwise there will still be problems.
It will take of couple of days for me to test the connectivity and battery life.
So, people, as for now, if it isn't working for you the only real fix on this ROM or any based on the ICS leak is to keep reflashing until it finally works all the way.
I can't wait for you (romracer) to start baking the mods into this and if I can help let me know. I'll post back here when I get more results from this last flash. Thanks.

Is it safe to apply this over Alien #6 (GB)? Just follow the instructions in the OP?

gravyplaya said:
Is it safe to apply this over Alien #6 (GB)? Just follow the instructions in the OP?
Click to expand...
Click to collapse
That's exactly what I did. Make sure you make a nandroid of 6 before you do it...just in case you want to go back. And follow the directions completely. Make sure you flash the modem first. And understand that even if you follow the directions exactly you might still need to flash this more than one time to get everything working. Just make sure you check for any of the known glitches right after you flash and before you start personalizing it. That way if something isn't working correctly and you need to reflash a time or two or more, you will not have wasted any extra time in the process. When you finally get it the way you want it and feel it is installed correctly (glitch free) do another nandroid so you'll have a point to jump to if you want to try something else and then go back again. Good luck.

Hi Romracer
can you please enable internet call settings under Settings>Call.....

[ROM] Jelly Bean / CyanogenMod 10 on HTC ChaCha

Hello everyone,
This thread contains the developing/porting stages for the Jelly Bean / CyanogenMod 10 ROM, brought to you by adlx.xda. Therefore all the credits regarding this should go to him. Thanks man for making this device better for each one of us!
Please note that the 2nd post is reserved by adlx for future use. Keep an eye out there. In the meantime I will manage the QA and provide assistance as much as possible.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Disclaimer: Any complaints about "damaging your phone", "stuff X doesn't work and I haven't put in it the known issues list and now my phone doesn't work as I want it to work and I'm crying like a little girl", and similar observations will not be tolerated. Flash this ROM at your own risk, you have been warned.
NOTE: This ROM is far from stable, it's still under high development by the CM team. Please report all of your findings in the thread as suggested below.
2nd NOTE: Please keep the thread clean of off-topic. Questions like "when is the next release?","When is the front camera fixed?" and so on will not be tolerated.
Release: DOWNLOAD
Google Apps: DOWNLOAD
Release notes:
relnotes in progress.
Reboot Into CWM Recovery
Wipe data, wipe cache
Flash ROM .zip file
Flash Google Apps
Google Apps seem not have enough space to flash correctly - Under investigation.
Text messages do not give notifications(even after going into the settings of the messaging application and making sure that "Notifications" is checked) - Reflash ROM with data/cache wipe.
Home button does not bring you home. - Under investigation.
Search button does not seem to do work.
Camera crashes.
Web Browser seems to just flash white on the screen for a second, then disappears and nothing happens. - Reflash ROM with data/cache wipe.
Dial pad in Phone application needs slight resizing, the left side of each number is slightly cut off.
During a call, the screen is rotated counter-clockwise 90 degrees.
Apollo is rotated counter-clockwise 90 degrees, except it's settings menu.
Calculator crashes on startup.
Movie Studio crashes on startup.
Lock screen isn't showing when locking - Reflash ROM with data/cache wipe.

OP+1
Useful Stuff that apply to that rom
Trim CM10 of not so useful apks and install Google Apps Lite, by Atrix4g18
lgCamera, free from the Market work! (pictures & videos). Only back camera
Install Google Now on this Rom by ethancottier
Wifi-Tethering, by ethancottier
Help to avoid lost wifi connections: Use the WiFix-Manager to set the correct country (tip by Flexmaen)
Int2Ext+ works great:
http://forum.xda-developers.com/showthread.php?t=1716124
Some apps still have orientation issues (Apollo...), try the app named Ultimate Rotation Control v 4.8.2 (works fine for Apollo for example), Tip by GragonV
Click to expand...
Click to collapse
ASN/Modpunk from the Wildfire S development, as I massively kanged his JB sources as a starting point and I xalso use his msm-7x27 common sources.
Recognized Contributor Alex C. for this official thread OP maintenance
CyanogenMod and all the people contributing to it for the main sources
SuperTeam for their help
Click to expand...
Click to collapse
Sources:
Linux Kernel (GPL): https://github.com/adumont/htc-kernel-msm7227/
Device tree: https://github.com/adumont/android_device_htc_chacha/
Vendor tree: https://github.com/adumont/android_vendor_htc_chacha/
Click to expand...
Click to collapse

Deleted, Sorry all.

I realize that there are going to be bugs, and that you likely know of many, but I thought I should contribute with a list of bugs I've found so far.
-First of all, I can't seem to get gapps(google apps) to install. in CWM it says that it completes, but none of the applications show up, I did try a few of the latest builds, so perhaps we need to use a specific older one.
-Text messages do not give notifications(even after going into the settings of the messaging application and making sure that "Notifications" is checked)
-Home button does not bring you home(or do much of anything) even if you go and set up what it's actions do in the settings.
-Search button does not seem to do anything either.
-Camera crashes(however it says "Gallery has stopped." so I imagine it's the usual top right image preview that's the culprit, although gallery itself works fine)
-Web Browser seems to just flash white on the screen for a second, then disappears and nothing happens.(assuming crash, but it's not actually saying anything)
-Dial pad in Phone application needs slight resizing(this was also present in CM9) the left side of each number is slightly cut off.
-During a call, the screen is rotated counter-clockwise 90 degrees.
-Apollo is rotated counter-clockwise 90 degrees, except it's settings menu(this was also present in CM9)
-Calculator crashes on startup
-Movie Studio crashes on startup
-Lock screen isn't showing when locking
(some of these may be just me, because I did change a few settings. I'll have to reinstall the rom and test all of these issues again. but at least it's something to go on in the meantime. I'll also try and get a logcat when I do.)
In general, the rom is -very- fast. The first boot was extremely slow/long, but after that, rebooting is much faster. The freezing is seemingly totally gone.

GAPPS doesn't install fully because the System space is to small for gapps. I removed a load of system apps to fit all of the Gapps in. Made about 30MB free to install.

kronflux said:
I realize that there are going to be bugs, and that you likely know of many, but I thought I should contribute with a list of bugs I've found so far.
-...
(some of these may be just me, because I did change a few settings. I'll have to reinstall the rom and test all of these issues again. but at least it's something to go on in the meantime. I'll also try and get a logcat when I do.)
In general, the rom is -very- fast. The first boot was extremely slow/long, but after that, rebooting is much faster. The freezing is seemingly totally gone.
Click to expand...
Click to collapse
Thanks a lot for the testing. Although I have been able to reproduce some of them, there are some of them that won't happen to me.
For example, home button is working fine for me, as the stock Web browser (tested on wifi). Also, when I lock the phone, it does go to the lock screen fine (with some delay though).
Cam is crashing also here, as well as Calc.
Sent from my Galaxy Nexus

adlx.xda said:
Thanks a lot for the testing. Although I have been able to reproduce some of them, there are some of them that won't happen to me.
For example, home button is working fine for me, as the stock Web browser (tested on wifi). Also, when I lock the phone, it does go to the lock screen fine (with some delay though).
Cam is crashing also here, as well as Calc.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Naturally after changing most settings(as I usually do when I install a new rom, I go through every setting and get a custom experience from the start), things are bound to be different. I'm going to PM you the logcat(I warn you, it's long, but I stuck it on pastebin) hopefully it will help out a bit. if I can help in any other way, let me know.
I'll reinstall the rom in a few hours and make sure everything works properly with "out of the box" settings, and post my results.

kronflux said:
Naturally after changing most settings(as I usually do when I install a new rom, I go through every setting and get a custom experience from the start), things are bound to be different. I'm going to PM you the logcat(I warn you, it's long, but I stuck it on pastebin) hopefully it will help out a bit. if I can help in any other way, let me know.
I'll reinstall the rom in a few hours and make sure everything works properly with "out of the box" settings, and post my results.
Click to expand...
Click to collapse
thanks, but what bug did you reproduce in this particular logcat?
Some hints about capturing a logcat per bug:
You can clean the logcat with:
adb logcat -c
Then, reproduce a bug, and then dump only that to file:
adb logcat -d > bug_ANameSoWeCanUnderstand.txt
Pastebin that .txt file, with a description of the bug .
Logcat isn't very intuitive (to me at least), so imagine reviewing a logcat with a lot of posibly unrelated bug, and no idea of what bug is supposed to be reproduced in it

adlx.xda said:
thanks, but what bug did you reproduce in this particular logcat?
Some hints about capturing a logcat per bug:
You can clean the logcat with:
adb logcat -c
Then, reproduce a bug, and then dump only that to file:
adb logcat -d > bug_ANameSoWeCanUnderstand.txt
Pastebin that .txt file, with a description of the bug .
Logcat isn't very intuitive (to me at least), so imagine reviewing a logcat with a lot of posibly unrelated bug, and no idea of what bug is supposed to be reproduced in it
Click to expand...
Click to collapse
terribly sorry that was literally just a logcat from the time I installed the rom, till the time I sent it - I'm kind of new to this xD
I'll see if I encounter any major issues during my next install and if I do, I'll send you more clean, specific logcats
---------- Post added at 12:26 AM ---------- Previous post was at 12:07 AM ----------
lucasarran said:
GAPPS doesn't install fully because the System space is to small for gapps. I removed a load of system apps to fit all of the Gapps in. Made about 30MB free to install.
Click to expand...
Click to collapse
any chance you could make a list of what you removed from where?
I'd like to try myself, but I don't want to delete anything needed.

System folder issue
Just on side note: I have quick question on how CWM install works.
Why do we see difference in behavior, like here some people see Home key not working, while others are fine. Seems like after flashing some partitions have different data. While flashing in CWM we take care of erasing /data and /cache. So I think those partitions should not differ from person to person. What about /system ? What is done while installing zip? Is the /system cleaned first and then zip contains is copied? Or just copied straight away?
This question is in my mind for some time now. I have seen fresh installs of OS also showing different behavior on my Phone. So please help with answer. Thanks.
Sorry for diversion from topic. But I thought it is just relevant at this juncture. Thanks a lot.

mobilepgk said:
Just on side note: I have quick question on how CWM install works.
Why do we see difference in behavior, like here some people see Home key not working, while others are fine. Seems like after flashing some partitions have different data. While flashing in CWM we take care of erasing /data and /cache. So I think those partitions should not differ from person to person. What about /system ? What is done while installing zip? Is the /system cleaned first and then zip contains is copied? Or just copied straight away?
This question is in my mind for some time now. I have seen fresh installs of OS also showing different behavior on my Phone. So please help with answer. Thanks.
Sorry for diversion from topic. But I thought it is just relevant at this juncture. Thanks a lot.
Click to expand...
Click to collapse
This isn't really the right thread for asking generic CWM or Android questions. There are "General" forums on XDA, and google is your friend.
On that note, I can't tell you what does what(because I don't know a lot of it myself), but if you search google for "/system /boot /cache android" or similar, I'm sure you'll find a list of what's stored where.
Personally, everytime I install a new Rom, I double check to make sure it has a boot.img, then upon using CWM to install it, I first do the following(some of them are redundant, but I do so for good measure):
wipe data/factory reset
wipe cache partition
advanced > Wipe Dalvik Cache
advanced > Wipe Battery Stats
mounts and storage > unmount cache
(If the rom had a boot.img) mounts and storage > format /boot
mounts and storage > format /cache
mounts and storage > format /data
mounts and storage > format /system
-then- I install the rom zip, and if I want gapps, I flash those afterward. then reboot.
This ensures that -all- data is gone, and it will not allow for unique bugs caused by remaining data from a previous rom.
In my case with the home key not working, I think I figured out what was causing most of the problems that I had, but adlx didn't have - After trying to flash GApps, and it not installing properly, it seems to have broken something.
After flashing the rom again(after clearing all those things) I'm now not experiencing those.
Notifications are working again, home key works, lock screen works, browser works, etc.

kronflux said:
In my case with the home key not working, I think I figured out what was causing most of the problems that I had, but adlx didn't have - After trying to flash GApps, and it not installing properly, it seems to have broken something.
After flashing the rom again(after clearing all those things) I'm now not experiencing those.
Notifications are working again, home key works, lock screen works, browser works, etc.
Click to expand...
Click to collapse
Confirming the lock screen issue. At first install it did not work. Now I reflashed, booted the ROM, restarted to CWM and afterwards flashed gapps. Now it works properly.
What we need to focus on at the moment, which is very important:
- gapps flashing 100%.
- camera working 50%.
- keyboard buttons and softkeys availability.
This is my high prio list, anything else is currently not that important; I have yet to find a person that will tell me he cannot live without the calculator app for example.

Alex C. said:
Confirming the lock screen issue. At first install it did not work. Now I reflashed, booted the ROM, restarted to CWM and afterwards flashed gapps. Now it works properly.
What we need to focus on at the moment, which is very important:
- gapps flashing 100%.
- camera working 50%.
- keyboard buttons and softkeys availability.
This is my high prio list, anything else is currently not that important; I have yet to find a person that will tell me he cannot live without the calculator app for example.
Click to expand...
Click to collapse
No Calculator?! We're all going to die! D:
but on a more serious note - something that struck my high interest when exploring this rom is that there is a Hardware Keys section under System in the Settings.
Granted, the only ones that are in there currently are Menu, Home and Search(screen "buttons"), but I wonder if we can maybe add a new one in there, and have it configurable so we can open apps with it.
It might be difficult, but it also might be worth pursuing for the Facebook button.

more n00b questions
First, I too look forward to getting the list/method of uninstalling some of the bundled apps to make way for gapps.
When I flashed JB, I had no unexpected problems (ie camera wasn't working, but pretty much everything else was). I downloaded titanium and deleted calculator only, then was getting bugs with TB, where it was getting stuck in some sort of superuser loop (I had told it to sort apps by total size, in readiness for deleting the biggest non-essential ones).
I rebooted, then tried flashing the gapps zip, and did not see any errors - but when I rebooted, I could only see the gmail app - no google play app. Could it be that gapps silently failed to fully flash, or is gmail the only extra app I should see?
Last, is there a recommended / confirmed working app for moving apps/data to the SD card? With CM7 I am using link2sd and there are a multitude of others. Is JB pretty much the same, or are some apps going to work better with JB?
I am very impressed with the smoothness of the system, particularly the browser. Really great work. It is so close to being usable already.

lucasarran said:
Made about 30MB free to install.
Click to expand...
Click to collapse
30MB free only?
Hmm... is it possible to integrate some features from SuperOSR? When I had SuperOSR based on CM7 I didn't have any problems with the RAM, but with CM9 and Link2SD the RAM fills up mach faster than with SuperOSR. Don't know why but I guess CM10 with SuperOSR features would be great!

Flexmaen said:
30MB free only?
Hmm... is it possible to integrate some features from SuperOSR? When I had SuperOSR based on CM7 I didn't have any problems with the RAM, but with CM9 and Link2SD the RAM fills up mach faster than with SuperOSR. Don't know why but I guess CM10 with SuperOSR features would be great!
Click to expand...
Click to collapse
It's because Link2SD will only move apks to Sdcard, but all app data, and dalvik cache will stay on /data, AFAIK.
You would need to use another mechanism of App ti SD that moves everything, like App2SD. I haven't tried it in CM9 nor CM10 though. Anyone?
Sent from my Galaxy Nexus

adlx.xda said:
It's because Link2SD will only move apks to Sdcard, but all app data, and dalvik cache will stay on /data, AFAIK.
Click to expand...
Click to collapse
No, it can move the dalvik cache as well as app data. However for some reason it will leave more garbage behind than the version of App2SD included in SuperOSR. Also the function "relink all application files" won't really help. Sometimes I even found installation files left on /data.

adlx.xda said:
You would need to use another mechanism of App ti SD that moves everything, like App2SD. I haven't tried it in CM9 nor CM10 though. Anyone?
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
i use INT2EXT with CM9 it works great!

adlx.xda said:
Reserved for future use.
In the meantime, go to http://goo.im/devs/adlx/chacha/cm10/
Click to expand...
Click to collapse
Alex C. said:
Hello everyone,
Click to expand...
Click to collapse
Thanks guys. This is really cracking.
In the meanwhile, I had a question about the CM7/9 ROMs you guys had uploaded earlier.
In the OEM ROM / StockPlus by Hexgore, the moment I type anything, it opens up the dialer. However, in CMROMS, any words I type open up the google universal search box - which is pathetically slow and doesnt solve my purpose. Often its just a number I am entering to call, not a string!
How can we remind android that its a phone first and a smart device later?
Many thanks in advance!!
PS: Why do CM ROMs have the CM camera and not the OEM one? the OEM camera is quite decent in and of itself, no?

phone search tool
hitanshu said:
In the OEM ROM / StockPlus by Hexgore, the moment I type anything, it opens up the dialer.
Click to expand...
Click to collapse
yes, I liked that quick fast dialer too. If you just flash CM10 without Gapps, you will see that there is nice Search tool, which searches your phone contacts, apps, web (I disable this anyway). It looks neat and tidy.
So after installing Gapps, we have to somehow disable google search/google now and enable this old search tool.
[UPDATE]:
In order to get default phone search working.
- Uninstall Google Search. Alternately remove/rename system/app/QuickSearchBox.apk. Check this file is about 4MB in size.
- From CM10 zip package, extract and install the QuickSearchBox.apk. Note this is just less than 1MB in size.
This search just works for Web/Contacts/Apps and can serve as temporary fix till we get the Google Search/Now FC issue fixed.

AOSP 5.0.2 D2303 Work in Progress

AOSP 5.0.2 Barebones for D2303
Hi all.
This is my first run of compiling a barebones AOSP 5.0.2 for our D2303's. I got sick of all the failed ports and wanted to make my own from scratch. Here you have my first launch. You can not get as barebones as this. This ROM was made using the guides on Sony Developer website and should be the same result if anybody else follows the same steps.
I have made ZERO modifications to this ROM. I have changed no code, made no patches or even themed it with a custom name. This ROM is as-is if you built it following the same guides on Sony's site. I just saved you the time.
**This ROM works!**
Data / Calls / SMS / NFC / Bluetooth / GPS/GloNAS / Wifi all work!
Camera does not. It might, but I broke mine and doesn't even work after stock restore!
No lag!
Clean, basic, no-frills, xPosed ready!
Unlock your bootloader!
Be running either a modem from a 4.4.2 ROM or a 4.3 ROM!
This ROM is provided as-is. The sources are freely availble following Sony's guides. You use it purely at you own risk!
Let's clear some confusion with this device, which I am shocked top developers have missed!
* You **have* to be running either 4.3 or 4.4.2 MODEM! If you are running a 4.4.4 ROM, use Flashtool to drop back to 4.4.2 or 4.3 first
* You will not be able to boot ANY 5.x ROM with a 4.4.4 modem, it **HAS** to be 4.4.2 or 4.3 MODEM!
There are guides on how to revert back on this forum and I will not detail that here. But in essence, it is only the modem you need to revert back.
This ROM I would say is usable.
* Camera doesn't work on mine, but I broke it to the point it wont work in stock ROM
* Calls / SMS / Data / Wifi / GPS / NFC / Bluetooth all appear to work as they should
* Sensors appear to all be working as they should (at least compass and light)
* No lag or FCs
This is a totally unmodified ROM using the AOSP & Sony sources provided in Sony guides. I did not develop or make any of the code or scripts. I simply compiled it, flashed it and now using it. All credit to the software that made this ROM goes to all those involved in making, patching and taking the time to make this work.
I do not want any donations. If you wish to donate, donate to FXP/CM12/Omni/PAC/TWRP and the persons that created what I have simply bundled here.
Download via magnet/bittorrent only for now. For trackers, please use OBT trackers. Issue with previous download! I somehow crossed an .img from another project as the boot.img for this. I have recitified this issue and the correct boot.img has been added. Apologies for this & thankyou to all whom spotted it.
Magnet Link
magnet:?xt=urn:btih:44d710f71b92adb9e64475994b5ab905d665af7d&dn=AOSP-5.0.2-D2303.tgz&tr=udp%3A%2F%2Fopen.demonii.com%3A1337
Mega Link
https://mega.co.nz/#!HZUUCCJS!AgjmKr4Nx4NMWPKxVXIGfp72m9JyMMlsF0pvzuGBrg8
Sorry for the bad link effort, since I am new to contributions I'm stuck until I make the relevant posts.
I have no idea if this will work on any of the variants of this device. You are welcome to try, but don't blame me if you break it. This ROM comes as is, is provided under the same licenses as AOSP and Sony Development.
Tricks & Tips:
* Download the .zip for Omni ROM 4.4.4 for our D2303's. Extract the boot.img and keep it safe. This boot.img holds a reliable TWRP which we can use to ''fastboot boot'' instead of flash and even make a reliable backup of a stock ROM. When you put device into fastboot/bootloader (hold power up when plug in data ready cable), execute ''fastboot boot boot.img'' which will boot that kernel w/o modifiying anything. Now keep hitting volume down when you see Sony logo. TWRP should load!
* Use this for all your backing up, flashing zips, ROMs etc. Do NOT flash it. Just fastboot boot it instead. This can even be used AFTER we install Lollipop for the same reasons.
* Flashing this ROM requires you to use the above TWRP to wipe all partitions, System, Data, Cache etc. It's best to start afresh (I actually wiped everything except since I wanted a totally clean slate, wiping external storage isn't necessary but wiping internal is recommended.)
* Extract the tarball with the .img files
* Put the device into fastboot mode again!
* execute the following commands:
* fastboot flash boot boot.img
* fastboot flash system system.img
* fastboot flash userdata userdata.img
Make sure all processes complete successfully!
Unplug cable, wait a second or two and power up your device! (I prefer this to fastboot reboot as the data cable can hang the device in a weird, red led stays on mode that has bootlooped me a few times).
Give it a while to boot. Whalla, Lollipop!
If you want gapps, using the fastboot boot method above with our Omni 4.4.4 boot.img and TWRP.. Download CM's gapps for Lollipop and flash/install it. This does not lag the device. However, you will get a black screen for a while after first boot of installing any system/ZIP flashable (it wont show updating apps, just blank screen). BE PATIENT! The same applies if you do anything that triggers that "Updating App X of X.." Android is updating effort.
xPosed requires you to follow the instructions for flashing the ZIP then installing APK. Use the same method above for installing the ZIP.
To get root, just download the latest SuperSU-2.x.zip and flash the same way as above.
**Issues**
* With a 4.3 Modem, the Bluetooth is slow coming to life. Take about 5 mins when turned on from off. 4.4.2 modem doesn't seem to have this issue
* Location services will forget a change to Accurate on a 4.3 Modem. On 4.4.2 Modem doesn't seem to do this.
* My loudspeaker during calls is tempremental, sometimes it works sometimes it doesn't.
* Some OTG devices work, some dont. I had one or two pendrives that did, some that didn't & a 3G modem (with PPP widget's help) that did & another that didn't!
* Screencasting initially didn't work. Enabling Developer Mode and disable HDCP checks seemed to allow some functionality for me.
* Data icon always said 3G for me, even when on HSPA(+) - I use OSM which showed varying network types. GPRS/EDGE shows as 2G. I do not know for 4G as my carrier isn't 4G enabled yet.
* No hardware accelleration (using VLC & MX Player as guides) for video playback, however it can playback a 1080 MKV over wifi no problem.
* Same applies to screen-recording software. I can't seem to get native Lollipop one to work at all, but SCR Free works.
* 3D Performance is a little smoother than in stock ROM (IMPO playing Ingress).
* GravityBox for Lollipop works. However!! On some instances it can cause a softboot on a boot up (when it goes for PIN entry). For me it comes back after they next cycle. Not pinned it down to what in GB doing it though.
* Compass, proximity & light sensors all work. There is some screen flicker once so often when using dynamic brightness.
* No way to force use of 5Ghz or 2.4Ghz wifi (or leave it to select auto) as there is in stock ROM.
* Battery life when using the device as I do is as the same as stock, the device is however faster in general. I can sit it for 29 hours idling, providing not too many calls. The powersaving modes built-in can extend on this but I haven't properly tested.
I only mention these as some people may care to know. If the camera worked, I would actually be totally happy with this ROM minus it's few pitfalls.
MD5's for the paranoid:
2c053445ab096e813afc2a02079aba85 boot.img
af636c1558e8d6651f211dbd2042443f system.img
adbb0b8d0b5eee98186a71a00d8352a4 userdata.img

Good job, please, compile an AOSP 4.4.4
Sent from my D2303 using XDA Free mobile app

What if I told you I did the same as you and it is EXACTLY the same build you can find on FXP's blog (but files are not straight uploaded, so build can be a little bit outdated). Developers around here are working on sources, and changes are on Xperia Developers Github.
As you can see there are things jerpelea (FXP) has pushed.
https://github.com/sonyxperiadev/device-sony-eagle
Only untouched sources are for Nexus, all other devices need to be patched, and sometimes rewritten from scratch (for example camera wrapper).

If I install this rom, and when I back to stock rom, i won't be able to use camera?
Is that right?

Um ok but why there is no seeding?;/ and why dont u give an alternative link?? haw we supposed to try this rom mate?
who can confirm if camera works or not ?

Update
I will work on a 4.4.4 AOSP eventually. Thanks for the tip, I'd also be curious on this.
I do not doubt that developers that are working on Omni/PAC/CM/FXP have submitted code, that's probably why the barebones is working sweet. I did try FXP but ran into different issues on different versions (all already documented). I built this on a whim as I just got fed up.
With the camera, that is exactly how I killed mine, and I also lost the original backup I made with Flashtool/Companion as well as from TWRP. So I have no hope. If you keep/make a backup upon successful bootloader unlock (companion/flashtool), you should be OK if you do a stock revert that is documented on this forum.
For the download link, sorry about this. I used transmission and it went into meltdown last night from another seed. I believe mega is a method people use here, is there any other suggestions. I will do this when I get back home and check back here.
** I am uploading this to Mega now, I will add the download link to the OP. **

Thank you for uploading this rom Dutch.
I ll test this rom, correct it where i can and send you pm as soon as possible with some fixes plus solution about your camera
cross your fingers to not break mine lol
Best regards
Vampirian

Thanks
If you do make some patches, can you please put them as flashable ZIPs? I really don't want to go and start tampering with a somewhat stable base. I bless whoever made that boot.img for the Omni 4.4.4 - I would like to try and get that working here, but again tampering.. Just means needing a PC or tablet to make mods to your phone each time.
I may have a bash at a custom kernel with a recovery for this, but I'm not rushing into that idea just yet.
** Update **
I got curious about the FOTA partition I saw using Flashtool and see there are already ports of custom recoveries (with custom boot kernels with elf extract support). I am overly curious about this now as I would love to have this TWRP from Omni's boot.img for my internal recovery. I have already made a custom kernel for my device and it seems to not effect anything (not changed a thing mind). I may now start to tinker!!

Has anybody tested this rom?
---------- Post added at 03:37 PM ---------- Previous post was at 02:53 PM ----------
I have the problem with boot.img
It says, failed: this is not a boot image

Bug list same as the omni one

Can You explain that boot.img is over 400MB Large!!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Which download did you use? That is so not right!! boot. img should only be about 6/7 mb. are the md5s matching on system and userdata? i will look into this asap
Sent from my Xperia M2 (AOSP) using XDA Free mobile app

The mega download is shot. It has become corrupted and I will remove the link from the OP. DO NOT USE IT!
The magnet link is still fine and extracts properly.. Just be patient as there are only 3 peers at present.
I am still using this ROM and there are some issues.
I failed to get Wifi tethering to actually route. It would run, give dhcp and even resolve DNS, but it is as-if the the nat forwarding rule has been missed and everything blackholes.
Camera is a total no go for me, I fooked mine in other ways though.
For how I use my phone (calls/sms/Ingress/HO/G+/Whatsapp/Maps/Wifi location mapping (OSM/Mozilla stumbler/Wigle) / Skymaps) it does just fine. Battery life isnt impressive vs. stock overall (doing same as above). xPosed allows tweaking, but this is where instability occurs.
GB works quite well, but avoid things that dont have direct L support (xPrivacy/Lightningwall etc.).
What I want to do is submit my phone into submission and try to get my camera working in a stock again, then give this another bash. It is a usable ROM if you just want a clean fast phone with no thrills (or camera).
Sent from my Xperia M2 (AOSP) using XDA Free mobile app

Magnet link not working
The magnet link you posted doesn't seem to work for me. I get "unable to parse magnet URI!" error

There is a space in the magnet part of the URI when you C&P. The forum did this. I should be able to post proper links soon.
Sent from my Xperia M2 (AOSP) using XDA Free mobile app

Nice for giving so much info on AOSP experiences and "prerequisites" (like 4.4.2).
I'm using a AOSP 5.1 build I made myself, and have to say the only issue with the latest build/kernel is battery drain (and camera, but "they" are working on it).
I Hope nobody will call you a troll because you share your builds and experiences with everybody

I got a massive lag when using browser or while using a few apps at once, also installing apps and turning on bluetooth take alot more time.
The things I do like is that it is pretty stable....

Thanks to all that have and are testing.
The tether issue was my tablets fault and does actually work. As does BT tethering.
All of the sensors work (i went out of my way to try each one (magnet sensors are always fun)).
The slow Bluetooth I found only happens when using a 4.3 modem. I dont get it now using a 4.4.2 modem.
There is no call record ability in this ROM. CM11/12 have enabled this feature, I believe its a small. xml patch, can anyone confirm please?
I do experience slowness with lots of open apps, i also notice if you have a lot in frequents its a pain to clear all (fixed with gravitybox mind). They also seem to come back even after a reboot. I do find myself regularly clearing the frequents which does sort it.
And thanks for the tips. I find trolls arent entirely too common here. Ive been reading from XDA for years and my sole idea was to demonstrate that its is doable and quite easy. I am still using this ROM everyday and Im quite happy with it. I do still prefer Kitkat though
I do want to play with 5.1.x (and nicer the camera works) - but i went 5.0.2 simply because of xposed support. Nothing else
There is a battery drain which I noticed "out-of-the-box" so to speak. This happens when there are issues with "qdoverlay" which i noticed sometimes occurs on bootup, then will savage your cpu. I spotted this in logcat and didnt find a direct fix (other than sleep the screen when the phone starts lagging, wait a second or two then wake it back up. Location type also counts, oddly high precision seems to give me more life. However, there is an "Over-Counted" cropping up in battery stats, which I cant pin is for what, as its usually a high figure at the bottom.
Can anyone confirm a working camera on this ROM? Opencamera or Googles should work if one doesnt show up.
Thanks again everyone
Sent from my Xperia M2 (AOSP) using XDA Free mobile app

Dutch Burdock said:
Thanks to all that have and are testing.
The tether issue was my tablets fault and does actually work. As does BT tethering.
All of the sensors work (i went out of my way to try each one (magnet sensors are always fun)).
The slow Bluetooth I found only happens when using a 4.3 modem. I dont get it now using a 4.4.2 modem.
There is no call record ability in this ROM. CM11/12 have enabled this feature, I believe its a small. xml patch, can anyone confirm please?
I do experience slowness with lots of open apps, i also notice if you have a lot in frequents its a pain to clear all (fixed with gravitybox mind). They also seem to come back even after a reboot. I do find myself regularly clearing the frequents which does sort it.
And thanks for the tips. I find trolls arent entirely too common here. Ive been reading from XDA for years and my sole idea was to demonstrate that its is doable and quite easy. I am still using this ROM everyday and Im quite happy with it. I do still prefer Kitkat though
I do want to play with 5.1.x (and nicer the camera works) - but i went 5.0.2 simply because of xposed support. Nothing else
There is a battery drain which I noticed "out-of-the-box" so to speak. This happens when there are issues with "qdoverlay" which i noticed sometimes occurs on bootup, then will savage your cpu. I spotted this in logcat and didnt find a direct fix (other than sleep the screen when the phone starts lagging, wait a second or two then wake it back up. Location type also counts, oddly high precision seems to give me more life. However, there is an "Over-Counted" cropping up in battery stats, which I cant pin is for what, as its usually a high figure at the bottom.
Can anyone confirm a working camera on this ROM? Opencamera or Googles should work if one doesnt show up.
Thanks again everyone
Sent from my Xperia M2 (AOSP) using XDA Free mobile app
Click to expand...
Click to collapse
Camera is not working

Dang. Thank you.
Sent from my Xperia M2 (AOSP) using XDA Free mobile app

Database Info

welcome