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.
Related
Hi,
I have been in contact with Bertans through his LEANdroid thread and through private message and we have been working on a bit of a mod for LEANdroid. Basically people want OC/UC and the rest of the goodness from other roms.
It is a mod of LEANdroid 11.10.2 and has a few extra bits over and above that rom. Now has a kernel custom compiled by me from aorth's kernel source.
Includes:
LEANdroidMOD_6
-2.2.2 Thailand rom base, newer and has the mystical .2 instead of .1!
-NOMA kernel from before
-Custom Ubuntu and Jura fonts because they look better than the ugly android ones
-Not compatible with previous 2.2.1 releases (up to LDM 5)
-This is for testing, not sure if it is compelling enough as an upgrade over LDM5 as I am going to include fonts in LDM 5 too.
-Still has old market, but it will auto update, may update it in a future release.
-Has XDA anti malware patch set up in installer.
LEANdroidMOD_5
-Custom kernel based of NOMA source
-Very custom smartass cpu profile setup, seems fast and battery efficient
-24/12/12, now has Ubuntu and Jura fonts and XDA anti malware patch in installer
-Otherwise similar to before
Previous
-Android 2.2.1+ LEANdroid 11.10.2+
-OC/UC 30mhz to 691mhz. Defaults to 30mhz and 600mhz- Fusion Kernel.
-Smartass and interactive governers. Default is ondemand.
-164MB free space.
-Some custom sounds.
-Fusion kernel 122mhz and 600mhz by default.
-Busybox
-NOfrills cpu control installed by default.
-Tweaked memory management
Everything that worked on LEANdroid should still work up to LDM 5 but it has a more spicy kernel and a few more tweaks. Please backup first as I cant be responsible if it doesn't work or you lose stuff. As these builds are just LEANdroid with a different kernel and a tweak or two, you should be able to get away with just flashing it over your existing LEANdroid install and just wipe cache and dalvic cache.
Download:
LEANdroidMOD_6, 2.2.2 base with everything back in /system directory to see if wifi can work for people.
Download: http://www.mediafire.com/?x8avapvmqlr78y6
MD5: 231D186B7A39E4D0588881A441AAE91F
LEANdroidMOD_6, 2.2.2 base
Download: http://min.us/mbomINMMtE
MD5: 377C8B6E01504BCF054126029BA1C223
LEANdroidMOD_5, 2.2.1 LEANdroid base
Download: http://min.us/mC8N9JhJE
MD5: F70D5C4BCB3F5BF0900F80E0B0FCB97C
Original Thread: http://forum.xda-developers.com/showthread.php?t=987736
Install
Install procedure:
-I installed Clockwork Mod recovery from rom manager which is the 3.0.2.4 version.
http://forum.xda-developers.com/showthread.php?p=13264607
http://forum.xda-developers.com/showthread.php?p=12619750
Reboot after install and hold volume up and green call button then push the power button > hold vol up and green call until recovery menu comes up > wipe user data and cache as well as dalvic cache in advanced menu > choose install zip from SD card and select whichever LDM release you are using. Once it is installed, reboot the phone and you should have a shiny new LDM install.
Thanks
-Bertans for rom base and help
-Androcheck for task killer help
-Dsixda for Kitchen
-aorth for kernel source and answering my annoying questions!
-NOMA Kernel Thread: http://forum.xda-developers.com/showthread.php?t=1228715
Kernel:
Source: https://github.com/PaulMilbank/kernel_huawei_u8150
Hocaeit Kernel 691mhz: http://min.us/mYEQMfD42
Flashable kernel 691mhz: http://min.us/mQYYzixNJ
Flashable kernel 729mhz: http://min.us/mVebnFefs -have not tested yet.
http://www.mediafire.com/?j7fvexu9h1odq
Cheers,
Paul
Looks Good!
Great job - I'm excited - will try tomorrow. What keyboard and launcher is this running?
I will try it (I am excited about it).
Still dun understand why everyone say about abd driver in install procedure when all is done on phone and phone sdcard.
Is running standard android keyboard and launcher pro just like LEANdroid.
Think the adb part is just to get clockwork mod on there. You can also use rom manager if you want, although that seemed to be playing up last time I installed it. if you play a bit more you can also use fastboot, but I have not tried that yet. Im still running CWM 3 installed ages ago using rom manager.
Any idea how to get extended "Phone options" when i press power button.
Like reboot, etc not just the 3: Silent, Airplane, Power Off ??
Thx.
It is something to do with custom frameworks. Have not explored that much as yet. Trying to get the kernel good and fast for a start and then can look at custom looks for later.
Hangs at Android logo
I had just finished flashing LeanDroid when I noticed your (what I like to call) "LeanDroid on Steroids" (on Steroids due to being overclocked). I had been thinking if I were to right a ROM, this would be it...so...I was jazzed. I spent all day trying things over and over and can't get it installed. It just hangs at the "Android" screen. I had to install something so went back to regular LeanDroid and installed it again with no problems. I did everything you suggested including the wipe and the new CWM to no avail. Did anybody else get it installed?
Oh, ok... interesting. will have to do a wipe and flash and see what is going on at some stage. Have been developing it as I go on my phone, so possibly it works as I have been flashing kernels and such over existing builds.
Has anyone else had this problem?
Does CWM give any errors with installing?
Im guessing you are reasonable experienced with flashing, but how long did you leave it for on the android screen?
is this the android animation screen or the boot splash?
Does the MD5 hash match?
Thanks for helping test this, hopefully can get some more info and testing done to work out what is going on here.
heh, just flashed it from fresh and no dice, boot loop. trying to suss it now.
Going to upload a more basic build which is just leandroid+ kernel. Just tested on fresh install and it boots fine. Link will be updated in the first post.
Paul
Ok, take 2... try the new mod which is in the original post. It is straight LEANdroid+fusion kernel.
CWM gives no errors. Not heavy enough to know the meaning of "MD5 hash match" but also not fresh out of the box; I gave it at least 5 minutes on the "Android" screen (don't know if that's called the animation or boot splash); regular LeanDroid takes almost exactly 2 minutes so I thought 5 should be long enough. Will try the new one now. If doesn't work it will take me a little while to get back to you about it because I'll have to reinstall a working ROM so I can connect and reply. Here goes.
PS: I'm not doing this for fun; I just wanted a fast & lean ROM because I found myself demanding a lot of my little IDEOS and she was getting intolerably slow...am I'm really exhausted from trying to come up to speed on all this over the last few weeks...so...I want to be finished with this now...so...when you do any future updates (in gratitude for my help ) if it's even possible, could you please make sure it catches this LEANdroidMOD_2 so I don't have to do anything else to have your final version? I'd really appreciate it. Here goes. I'll let you know what happens.
OK. It loaded. Took 2 minutes just like plain LeanDroid. I went straight to the app drawer to play with NoFrills but it's not there. I realize you probably "lightened" this one as a troubleshooting tool to get her working. I just installed NoFrills and it does offer the 691MHz of the custom kernel. Sorry for asking you to educate me but:
1. Is it very advantageous to have NoFrills (or any desired apps) built in to the ROM instead of installed separately and if so, why?
2. Should I go 691, 122, ondemand, & deadline or what?
3. Should wait before I start heavily customizing my homescreens with postits, etc. because this prelim version won't be updated?
4. Is there a way to update to a more final version without losing my homepage customizations?
Thanks for the (I say best) ROM and any educating you give.
Hey Paulynator, thanks for your patience. Leandroidmod_2 was a very quick build to get things moving as I had to build something to get my phone working after the first rom didn't boot in testing! Will upload another build with busybox by default and a couple of small mods today. Problem came from data/app, so ditched that and put apps into /system/app.
Questions:
1)Not really, I just like it, others may prefer setcpu or something else instead.
2)You go with what you feel happy and doesnt crash your phone, try 652 and 60 first, then go higher and lower if it is working fine. Just leave apply on boot unchecked in nofrills until everything is working fine. Ondemand and deadline will be fine.
3)Updates should be able to be installed without a wipe.
4)Just install zip in CWM over your install, sorry, I cant promise anything though.
Thanks
Paul
Ok, take 3. everything from 2+busybox and some custom bits. Tested on my phone and it boots fine with a total wipe. Hopefully wont need to do a total wipe, but have not tested flashing over an existing install.
For question #1, I didn't mean NoFrills as opposed to SetCPU or something else; I'm asking if it's very advantageous to have desired apps built in to the ROM instead of installed separately and if so, why?
Paul,
Report on LEANdroidMOD_3 (a.k.a. LeanDroidOnSteroids, c'mon, it rhymes!) (or even "cleaner": SteroidLeanDroid. If I say so myself, awesome title for an awesome ROM...to me.)
Installed over version #2 w/o wipe seems to be ok...to the extent that I started the process of recluttering (restoring) my Ideos as though "she's a keeper", i.e. no more wiping; the records stay intact from now on.
Paul
---------- Post added at 05:55 PM ---------- Previous post was at 05:47 PM ----------
Sorry to hit you with 3 since your last but since we have a "hard"/permanent Home button right below the screen, is the redundant one at the bottom of the app drawer removable from a menu or would I have to mod the rom to remove it?
Paulynator said:
For question #1, I didn't mean NoFrills as opposed to SetCPU or something else; I'm asking if it's very advantageous to have desired apps built in to the ROM instead of installed separately and if so, why?
Click to expand...
Click to collapse
Doesnt matter one way or the other, I just liked it built in. Only possible advantage is that some apps in /system/app wont use space in /data/app, but this is lost the moment you update them as updates seem to install into /data/app. So my Leandroid with nofrills in /system/app still gives 164mb free space in data partition until things get updated.
Good work, thanks for the update that it can be installed over a previous install.
Home button is part of launcher pro. on the home screen, hit menu>preferences>appearance settings>uncheck home button on app drawer.
Paulynator said:
Paul,
Report on LEANdroidMOD_3 (a.k.a. LeanDroidOnSteroids, c'mon, it rhymes!) (or even "cleaner": SteroidLeanDroid. If I say so myself, awesome title for an awesome ROM...to me.)
Installed over version #2 w/o wipe seems to be ok...to the extent that I started the process of recluttering (restoring) my Ideos as though "she's a keeper", i.e. no more wiping; the records stay intact from now on.
Paul
---------- Post added at 05:55 PM ---------- Previous post was at 05:47 PM ----------
Sorry to hit you with 3 since your last but since we have a "hard"/permanent Home button right below the screen, is the redundant one at the bottom of the app drawer removable from a menu or would I have to mod the rom to remove it?
Click to expand...
Click to collapse
Just found a possible glitch. Don't know if it's the ROM so tried the obvious things to no avail. The camera app (any camera app; I tested the problem by downloading and trying others) won't access the gallery. In the stock app, the little preview window (that tapping opens the picture in the main window) won't open the picture. It gives an error message saying "app initialize failed. please download the app from the market". The app isn't in the market so I d/l'd 2 other camera apps and they both did the same. Using Root Explorer to try to open a picture also wouldn't work. Could you please try to access the gallery on a phone you've installed your ROM on and let me know if it works? I'd appreciate it. Thanks.
Works fine on mine. Try go to the market and update Quickpic. It does not like being in /system/app so if you update it, it should work. It was one of the reasons I tried to put it in a data/app from the start, but that caused bigger problems like the rom not booting.
I could also put the stock gallery back in alongside quickpic if needed but it does not have multitouch.
This is a snapshot of my work on bringing camera support to Tezet's Milestone2 ICS port.
This is continuation of this thread: http://forum.xda-developers.com/showthread.php?t=1520572
- it's based on CM9 snapshot from March 2nd
- it may contain more (or less) bugs from Tezet's builds. It's simply different, newer etc.
- it should be possible to load this without factory reset on top of Tezet's CM9 builds and the other way around, though the last time I've tried this was early February...
- there's no need to wipe dalvik cache - the update script does this
- the fix for SIM lock pin is not included
- there's no Torch and file manager app. Don't ask
Camera notes:
The work is based on Atrix ICS camera support, with added overlay emulation.
What is working:
live preview
zooming
flash
focus
exposure compensation etc
taking photos
some 3rd party apps (Pano, CameraFX, Barcode scanner)
doesn't crash when enterinng video/panorama mode
generally much more stable
... probably not much more
What is not working:
panorama mode
video recording
a lot more
Other stuff: (compared to previous version)
- bluetooth should be OK (please test)
- aGPS should work
I highly recommend to do a nandroid backup before trying it.
Latest version available at http://code.google.com/p/cm9-milestone2/downloads/list
If your phone is stuck on Google logo, it means you have chosen a wrong version and you need to recover your phone from the SBF file.
Repository:
repo init -u git://github.com/rondoval/android.git -b ics
All the credits go to:
- Tezet, for the Milestone2 port
- tpruvot, Quarx2k, for their tremendous efforts on Defy support (and thus Milestone2)
- whole Atrix-Dev-Team, Raviprasad V Mummidi, zivan56 for their tremendous work on the camera driver
Just backing up my MS2 now. Going to flash it over CM7 Tezet and see how it goes.
Cheers for the efforts
omg thanks ! download...
Sent from my MotoA953 using xda premium
mattyt_491 said:
Just backing up my MS2 now. Going to flash it over CM7 Tezet and see how it goes.
Cheers for the efforts
Click to expand...
Click to collapse
its for CM9....
devilbatghost said:
its for CM9....
Click to expand...
Click to collapse
Actually this would be a good test... I did that in december. I had some issues, bu I think that was mainly due to wrong version of gapps.
If you're still planning to try upgrading from CM7 to CM9: You may need to wipe telephony provider data and deskclock after upgrade.
/data/data/com.android.deskclock/databases/alarms.db
/data/data/com.android.providers.telephony/databases/telephony.db
Please tell us how did it go
hi, rondoval.
chrome beta don't work. can you try to fix it when you have free time? thx.
rondoval said:
Actually this would be a good test... I did that in december. I had some issues, bu I think that was mainly due to wrong version of gapps.
If you're still planning to try upgrading from CM7 to CM9: You may need to wipe telephony provider data and deskclock after upgrade.
/data/data/com.android.deskclock/databases/alarms.db
/data/data/com.android.providers.telephony/databases/telephony.db
Please tell us how did it go
Click to expand...
Click to collapse
I know it is CM9 I said I was flashing (upgarding) FROM CM7.
As per your advice I cleared alarms.db and telephony.db and was going well.
I also was unable to find the fix for the SIM PIN lock, so I just disabled it.
I haven't yet tried the gapps for ICS because the download through multiupload.com is not working (seems as though multiupload in general is down).
I can confirm that the camera works (photos only) and was able to upgrade from CM7 with no issues without wiping my data.
The ROM is smooth and seems to handle most tasks I have thrown at it. However, I am finding 3D performance a bit lesser than that experienced on CM7 (not a major issue).
Cheers.
Good work, thx! Glad to see we have one more dev working on our MS2.
This rom is awesome!!! =D
Someone can upload the Gapps 4.0.3 please ? because the link on the other post is dead.
Thanks in advance
tony_the_unik said:
This rom is awesome!!! =D
Someone can upload the Gapps 4.0.3 please ? because the link on the other post is dead.
Thanks in advance
Click to expand...
Click to collapse
Here's the link to gapps http://goo.gl/krVg1
Thanks for the gapps link.
Out of interest is there a fix for the Sim pin code yet?
Sent from my MotoA953 using XDA
Some news:
First 5sec 480p video recorded.
Going to cinema now, so don't expect a build today.
New patch for 1% step battery counter on this build
rondoval said:
Some news:
First 5sec 480p video recorded.
Going to cinema now, so don't expect a build today.
Click to expand...
Click to collapse
thank you. I am glad to see the video recording fixed
Is there any bug for the touch?
Since when I am touching and holding on the screen, it displays I'm swiping horizontally instead of holding it (I enabled "Show touches" in Development Tools)
I believe i might have run into a bug, Im not sure if anyone has note this bug or not. In the apps menu, if you hold a application, you can drag it to Remove which will uninstall the app normally, however at the moment, dragging it to Remove does nothing. Does anyone have a idea whats wrong?
i have a huge problem. when my phone is booting up, it only shows the google logo, and.. nothing happend. only a black screen with backlights.
if i try the X factory reset, the screen with an exclamation mark pops up -
but if i press the @ key, nothing happen.
if i try to the connect my phone with RSD lite, the bootloader is loading but shows 'battery low
cannot program'
when i was trying to load the ROM my battery was ~50%...
what should i do?
after a few times failing with the @ - it works.. one time..pressed the factory reset - booted up - still bugged with the google boot up logo...
hi, aznsniper
i have the same problem,i have no idea to solve it. sorry... maybe rondoval will fix it in next build.
@jimbo0815
Did you factory wipe, cache wipe and dalvik wipe before installing the rom? If you did, is it possible that you installed the wrong version? Just my 2 cents worth.
aznsniper said:
I believe i might have run into a bug, Im not sure if anyone has note this bug or not. In the apps menu, if you hold a application, you can drag it to Remove which will uninstall the app normally, however at the moment, dragging it to Remove does nothing. Does anyone have a idea whats wrong?
Click to expand...
Click to collapse
ylqiu said:
hi, aznsniper
i have the same problem,i have no idea to solve it. sorry... maybe rondoval will fix it in next build.
Click to expand...
Click to collapse
that's a problem of trebuchet, the launcher. so it has to be fixed there.
but i think should be like that.
Sent from my MB525 using XDA App
{
"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"
}
This is an ongoing developer project to make way for a modification that will entirely transform your device, but retain the aesthetics and the experience of your phone. I know you've seen tablet mode roms before, they change two lines in your build.prop file which you could easily edit yourself in seconds and maybe throw a keyboard in there to make it work better. It's a start, but this ain't enough. This thing has potential, but it is wasted the moment you try to stuff a full blown tablet into your poor phone. Yet we all know our high res phones can very well handle more than silly 1-column layouts. So the magic must be in between somewhere, a place that Google must have overlooked and left blank. Yes, this rom strives to drop your device into tablet mode, but it won't stop there, it will reshape and redefine ICS to make it all a usefull addition and not just a cute novelty. we're calling it: Hybrid Mode, best of both worlds.
Donate to Cyanogenmod: http://forum.cyanogenmod.com/donate
Donate to molesarecoming: http://forum.xda-developers.com/donatetome.php?u=4491046
Donate to D4rKn3sSyS: http://forum.xda-developers.com/donatetome.php?u=3484876
Wipe data/factory reset
Wipe dalvik cache
Install ROM: http://beta.androidfilehost.com/?fid=9390062577138008170 FULL WIPE! FIX PERMISSSIONS!
Install HYBRID Gapps: http://goo.im/gapps
Requested kernel source: CM10 kernel source
FAQ & Help - Read before asking!
Go to Settings, System, Font size, set it to NORMAL
Launcher Settings: margins: SMALL (If youre using Apex / Nova), show permanent searchbar: YES, Grid: 5x4, resize all widgets: YES, Wallpaper scrolling: OFF
Themes and other goodies you can find here: http://forum.xda-developers.com/showthread.php?t=1646034
If you have an issue and you want to call our attention, here's what you do:
1. Try everything you can, find solutions for yourself. Wipe caches, revert all your settings you have made, go back to your stock Kernel, factory reset if you have to or reflash the rom. Assume that the issue is on your side and try your best to isolate it.
2. Search this thread and Cyanogenmods aswell (its our base) for possible reoccurences of your issue and hopefully solutions that may have come up.
3. If you think the issue is important enough that we should cease our work and look into it, post your issue, BUT ...
... stay friendly, do not demand anything, do not threaten
... explain your issue as precise as you can, name the exact apps and conditions that cause trouble, help us to replicate the issue right away. If we can't there's no way we can fix it and your post will simply clutter the thread
... collect evidence, keep in mind this is a developer thread so even if you are not one, do us the favor and research how to record logcat. logcat is the single most important help you can give us to resolve your issue.
The ParanoidAndroid Team - For ParanoidAndroid
molesarecoming - For letting me port
Cyanogenmod - For everything they do
PureMotive - Galaxy S3 porter and maintainer
no
20120819v1.991
Maintenance update, bugfixes and patches.
20120810v1.9.8alpha
Project butter recents in tabUI (2/2)
Quick access hybrid properties by longpressing a recent app
More refined hybrid algorithm to reveal more layout containers
TabletUI toggles
All recent cm merges (Trebuchet, googles 4.1.1 r4 with a whole bunch of fixes for memory leaks, etc)
20120806v1.9.7alpha
New option: "large" to trick an app thinking the device has a real big screen. some need it, like amazon kindle to jump into tabUI. some even react on it, gdrive will slightly adapt its layout - makes only sense if you give it a small dpi though.
The algorithm to extract the actual layout containers from apk files works more precise and can reveal more than before. there will still be a few apps left who do that layout stuff in java - we will add an override button for that, but in the meantime you can edit /system/etc/paranoid/properties.conf .layout=360 for phone-like UI, 600 for phablet, 720 = tablet, 1280 = super huge tablet
Several bugfixes from us and cm
CDMA SIM
20120723v1.9.5a - On Page 23
Finally hardware accelerated recents in TabUI, as fluid as ever. The ugly gradient is gone aswell
A clean backup properties file is shipped, you can make a full reset in the panel in case you lost it with all the settings you made
Force option can be activated in the panel, good for widget scaling
The DPI sliders in the panel read min/max props from properties.conf, define them as you like
TabUI Recents are back to a bigger size, this is temporary, i'll look for ways to port the phone implementation as project butter skipped the tabUI code
Cyanogenmod fixes
New GApps
20120723v1.9a / 1.9.1a - My edits are in RED
Newest CM10 patches (powertoggles for phoneUI, lockscreen options, etc,)
Definable number of notifications for navbar shaping
Hide clock wont cut it out of the notification center aswell
Lockscreen tutorial overlap *should* be fixed
Notificationcenter in TabUI has a draghandle like phablet and phone have
New GApps
Camera (very rough fix)
Panorama
Video Recording
Video Playback
YouTube (very rough fix) - I suggest starting out in landscape mode
Phone number
Do I flash this using ODIN?
No. Use the custom recovery that's linked.
I still don't know how to install the ROM
Download the ROM, GApps, and recovery.img from the OP
Download and open the EZ recovery app from HERE
Select custom, then select the box with 3 dots... find the d2vzw_recovery.img you downloaded in step 1 part B., select flash, then Reboot Recovery
From CWM recovery, Perform a nandroid backup from the backup/restore menu
Wipe data/factory reset
Select install .zip from sd and install the rom you downloaded in step 1 part A.
Select install .zip from sd and install the gapps package you downloaded in step 1 part B.
Reboot
Thanks droidstyle
I'm in a bootloop. Help!
This is normal for now. The phone will reboot multiple times, but will get to the bootanimation and eventually boot up. Do not freak out.
Something went wrong! Can you help me?
I'd love to help you, but I need a little more information about your issue. You should provide us with information regarding what your issue causes and what you did before the issue started. However, before asking me and the community, ask yourself two simple questions:
Can I reproduce the error?
Have I looked for a solution?
If you answered "yes" to both of these questions and came up empty handed, then post it in the thread and it will be addressed. Even more helpful would be if you got a logcat. Like so:
Code:
adb logcat > logcat.txt
OR (the better way so we dont have to keep downloading logs)
Code:
adb logcat
Paste the terminal output here (you don't need to register): http://pastebin.com/
Click "submit"
Share your link/logcat
When I use the camera the phone freezes and I have to do a battery pull...I thought it was fixed? (1.9.1a)
It is fixed. It's just a pretty hacky fix. To take a picture, you will have to tap the screen to focus the camera BEFORE taking the picture. If you just press the camera button, the phone will freeze.
Can you add *this* to the ROM?
Although I'm not obligated to add anything and everything to the ROM, I will do our best to supply your desires and live up to your expectations. Do not mistake this for a guarantee. I would like to do everything, but I may not be able to.
I'm experiencing some force closes, what gives?
Boot into recovery and fix permissions. Reboot.
Where can I go for information about the latest updates?
You can follow me on Twitter
Omgz, on-screen buttons! Can't wait to ditch this physical home key.
This Rom looks Awesome!!! Thank you for all the hard work. I am a noob when it comes to ADB , does anyone have a video that shows how to install this recovery and rom. Thanks in advance.
drbveb88 said:
This Rom looks Awesome!!! Thank you for all the hard work. I am a noob when it comes to ADB , does anyone have a video that shows how to install this recovery and rom. Thanks in advance.
Click to expand...
Click to collapse
Hopefully you already have adb installed (I'm assuming you do). You are going to want to download the recovery.img beanstown106/Team Epic has provided us with and then move it into the directory where you have adb installed (usually in "platform-tools" or "tools" in the android-sdk). Then cd to that directory using terminal or cmd (depending on your OS).
It should look something like:
Code:
cd .../Desktop/android-sdk/platform-tools
Once you do that, then enter each of the above commands (in the OP) in descending order. When it finishes, you're done.
:highfive:
Im guessing we will have the same issues we are having with cm9/cm10? like camera and possible imei disappearing?
drbveb88 said:
This Rom looks Awesome!!! Thank you for all the hard work. I am a noob when it comes to ADB , does anyone have a video that shows how to install this recovery and rom. Thanks in advance.
Click to expand...
Click to collapse
Use section 5 of my guide in sig...just replace links with this rom and gapps.
PureMotive, thanks alot for this! If you like copy my section 5 instructions to your op...it uses mmmeff's EZ recovery app to install recovery. I believe this will keep the "how do i install this" questions at bay since most dont understand adb. Thanks again for your work!!
suzook said:
Im guessing we will have the same issues we are having with cm9/cm10? like camera and possible imei disappearing?
Click to expand...
Click to collapse
Normal camera doesn't work, but panorama and the video recorder do.
droidstyle said:
Use section 5 of my guide in sig...just replace links with this rom and gapps.
PureMotive, thanks alot for this! If you like copy my section 5 instructions to your op...it uses mmmeff's EZ recovery app to install recovery. I believe this will keep the "how do i install this" questions at bay since most dont understand adb. Thanks again for your work!!
Click to expand...
Click to collapse
Will do
looks ok, noticed that ex-sdcard doesnt show and data keeps cutting out..other than that looks pretty cool
I am so excited to see this here! Thanks for developing.
For more exposure, shouldn't this be in the original android development section? Just a suggestion.
Sent from my SCH-I535 using Tapatalk 2
Holy crap, this looks AMAZING! Thanks for what looks like amazing work on this. Downloading and and preparing to make a Nandoid.
Ran this on my nexus and loved it. Can't wait to give it a shot. I'm going to wait till I have time to learn more about the IMEI deal before I flash but I can't wait. Nice work.
Sent from my SCH-I535 using xda app-developers app
This looks really cool. On my todo list. Also, :good: on the logo
Nevermind
Very cool boot animation. 4G is working really well for me. Very smooth rom. I have not experienced any bugs as of yet, but then again I've only been up for less than a hour.
Rom is running awsome so far!!
can someone check the camera and also wifi tether.
Basically this Rom will try to convert your phone into tablet and ended up getting tiny fonts!
Sent from my S3 using xda premium
The fonts are not really small on this by default. I kept the default setup and the fonts are close to stock size.
The camera froze on me after one picture. I got an "gallery not responding" error. I thought I read there was a fix if the gallery.apk was replaced.
I used the ROM from here. (LG Optimus T (P509): January 8: Build 7/Final)
I have no Google Play store icon anywhere. I see the Google Play process running in the background.
but have no way to get it to show up. This on a fresh ROM, all User data, Cache, and all that cleared.
Any help on this would be nice.
Would of asked on that post where I got the ROM. but I don't have the patience to or any thoughts about other post to make to meet the requirements to even post there.
Tried without flashing the Google Apps and with the google apps they list there.
Flashing Google Apps just crashes things like the browser. it wont even open.
Not flashing Google Apps I can use the browser just fine. but I still see "Google Play Services" Running. So that tells me google play is installed.
So don't have to flash it. but cant open it even if i did or not. no Icon anywhere no matter what I try. I been wanting to use CM10. but this issue keeps me going back to CM7.
Thanks in advance to the person with the answer.
TroyFoxxin said:
I used the ROM from here. (LG Optimus T (P509): January 8: Build 7/Final)
I have no Google Play store icon anywhere. I see the Google Play process running in the background.
but have no way to get it to show up. This on a fresh ROM, all User data, Cache, and all that cleared.
Any help on this would be nice.
Would of asked on that post where I got the ROM. but I don't have the patience to or any thoughts about other post to make to meet the requirements to even post there.
Tried without flashing the Google Apps and with the google apps they list there.
Flashing Google Apps just crashes things like the browser. it wont even open.
Not flashing Google Apps I can use the browser just fine. but I still see "Google Play Services" Running. So that tells me google play is installed.
So don't have to flash it. but cant open it even if i did or not. no Icon anywhere no matter what I try. I been wanting to use CM10. but this issue keeps me going back to CM7.
Thanks in advance to the person with the answer.
Click to expand...
Click to collapse
Are you sure you are using the right GApps package? That's Rasheds ROM you're referring to using. Build 7 is Android 4.1.2. Check this link here. And some of the problems you may be experiencing could be due to a faulty installation because of limited system space. You may want to review the LG Optimus One FAQ too.
shinobisoft said:
Are you sure you are using the right GApps package? That's Rasheds ROM you're referring to using. Build 7 is Android 4.1.2. Check this link here. And some of the problems you may be experiencing could be due to a faulty installation because of limited system space. You may want to review the LG Optimus One FAQ too.
Click to expand...
Click to collapse
There is more then enough internal space. (150MB Free after Gapps Flashed).
I tried again with the Gapps for 4.1.2. At the time my post I re flashed the ROM but left it out. I didn't flash it.
When I tried again. I got the Updating Android. but still no Play Store Icon. However it did not break my home or other buttons.
and browser still working. but again. no Play Store icon.
I checked the FAQ. Currently i see nothing there to give hints. I got more then enough free space. I've flashed ROMs on this phone dozens of times so I know the whole wiping of cache and data and all that between each ROM.
TroyFoxxin said:
There is more then enough internal space. (150MB Free after Gapps Flashed).
I tried again with the Gapps for 4.1.2. At the time my post I re flashed the ROM but left it out. I didn't flash it.
When I tried again. I got the Updating Android. but still no Play Store Icon. However it did not break my home or other buttons.
and browser still working. but again. no Play Store icon.
I checked the FAQ. Currently i see nothing there to give hints. I got more then enough free space. I've flashed ROMs on this phone dozens of times so I know the whole wiping of cache and data and all that between each ROM.
Click to expand...
Click to collapse
You have to trim the Rom, there's not enough SYSTEM space for the Rom and Gapps..this has been discussed time and time again on rashed thread(cm10)..There's a tool ( Oone Rom editor that will help you do this) This is why you have the bugs that your facing.
3ncrypt3d_Droid said:
You have to trim the Rom, there's not enough SYSTEM space for the Rom and Gapps..this has been discussed time and time again on rashed thread(cm10)..There's a tool ( Oone Rom editor that will help you do this) This is why you have the bugs that your facing.
Click to expand...
Click to collapse
I used that program already. looking at all that it would only show.
the math dont even come to half of what the phone memory is.
TroyFoxxin said:
I used that program already. looking at all that it would only show.
the math dont even come to half of what the phone memory is.
Click to expand...
Click to collapse
The system partition has nothing to do with the devices memory. These devices have a 190 MB system partition, this is where Android gets installed. What you are referring to is the user data partition which is 200 MB, while the device has 415 MB+- RAM ( memory ). Unless you are using Android 4.2.2, the only way to see how much space is on the system partition is with a third party app, with ADB, or with a Terminal Emulator app on the device. The math isn't adding up because you don't understand it, that's why I pointed you to the FAQ thread.
I wrote OOne ROM Editor. I haven't put hundreds, yes hundreds, of hours in to it's development just for general pleasure. It was written for a specific purpose, to trim ICS and newer ROMs for devices with small or limited system partitions.
shinobisoft said:
The system partition has nothing to do with the devices memory. These devices have a 190 MB system partition, this is where Android gets installed. What you are referring to is the user data partition which is 200 MB, while the device has 415 MB+- RAM ( memory ). Unless you are using Android 4.2.2, the only way to see how much space is on the system partition is with a third party app, with ADB, or with a Terminal Emulator app on the device. The math isn't adding up because you don't understand it, that's why I pointed you to the FAQ thread.
I wrote OOne ROM Editor. I haven't put hundreds, yes hundreds, of hours in to it's development just for general pleasure. It was written for a specific purpose, to trim ICS and newer ROMs for devices with small or limited system partitions.
Click to expand...
Click to collapse
I dont know what to try to trim with that program. i dont know what half them apps do.
Like Exchange2.apk. I don't know what that is. Which are some of the key things i can trim?
Also, Telling me how many hours you put into a program and that i dont understand something not going to be on my good side. So i missed something, big deal. I just got off a anxiety attack. and i was needing was a simple answer. doing a search for "LG P509 No Playstore Icon" was getting me no where and i didnt want to have to search page by page of the 487 pages of the ROMs post to find clues.
TroyFoxxin said:
I dont know what to try to trim with that program. i dont know what half them apps do.
Like Exchange2.apk. I don't know what that is. Which are some of the key things i can trim?
Click to expand...
Click to collapse
The help docs in OOne ROM Editor's thread list some of the known files that can be removed from and or moved around, ie; converted to user app, in the ROM.
shinobisoft said:
The help docs in OOne ROM Editor's thread list some of the known files that can be removed from and or moved around, ie; converted to user app, in the ROM.
Click to expand...
Click to collapse
just never mind. i dont need the stress right now, ill just stay with CM7.
Every time i try to Build the ROM and put it on the phone CWM just says its bad.
TroyFoxxin said:
just never mind. i dont need the stress right now, ill just stay with CM7.
Every time i try to Build the ROM and put it on the phone CWM just says its bad.
Click to expand...
Click to collapse
Are you getting an "assert() failed" message? If you are using CWM 5.0.2.7 Touch, it will only allow you to install P500 ROMs. OOne ROM Editor has the ability to remove the "assert()" statement from the ROM's updater-script to prevent that particular error from happening. Before building the ROM, go to the Tools->Build submenu and select the Build Options command. Check the checkbox for "Remove updater-script 'assert()' statement". Then build the ROM.
And stress... You call editing a ROM stress? Try writing the code for OOne ROM Editor Or better yet, play with live electricity :silly: - oh wait I do that already since I am an electrician... DOn't get frustrated by it. Sit back relax and soak in some of the knowledge around here.
shinobisoft said:
Are you getting an "assert() failed" message? If you are using CWM 5.0.2.7 Touch, it will only allow you to install P500 ROMs. OOne ROM Editor has the ability to remove the "assert()" statement from the ROM's updater-script to prevent that particular error from happening. Before building the ROM, go to the Tools->Build submenu and select the Build Options command. Check the checkbox for "Remove updater-script 'assert()' statement". Then build the ROM.
And stress... You call editing a ROM stress? Try writing the code for OOne ROM Editor Or better yet, play with live electricity :silly: - oh wait I do that already since I am an electrician... DOn't get frustrated by it. Sit back relax and soak in some of the knowledge around here.
Click to expand...
Click to collapse
Again bad, day. had a Anxiety attack. haven't slept. I havent played with Android as often as other things. I am also a Electronic person. Soldering Caps and so on on motherboards all the time. So please dont talk like that to people you dont know. they may have plenty of knowledge. but maybe having whats called a short fuse kinda day.
Also I did do "Remove updater-script 'assert()' statement". And i get no error from OOne ROM Editor it was in CWM it would just say it was bad, or say nothing at it would just restart CWM. Ill try again when Im better. Right now my phone has CWM 5.0.2.0, So ill change that as well when i try again.
but right im turning in for the night.
TroyFoxxin said:
Again bad, day. had a Anxiety attack. haven't slept. I havent played with Android as often as other things. I am also a Electronic person. Soldering Caps and so on on motherboards all the time. So please dont talk like that to people you dont know. they may have plenty of knowledge. but maybe having whats called a short fuse kinda day.
Also I did do "Remove updater-script 'assert()' statement". And i get no error from OOne ROM Editor it was in CWM it would just say it was bad, or say nothing at it would just restart CWM. Ill try again when Im better. Right now my phone has CWM 5.0.2.0, So ill change that as well when i try again.
but right im turning in for the night.
Click to expand...
Click to collapse
Sorry you're having a bad day. Rest assured, if I was talking down to you, there wouldn't be any smilies. I was just expressing that you weren't the only one out there with stress in their life, and some of us have loads of it. On that note, I'm not one of the many teenagers around here. So I'm not talking down to you, but out of experience. My teenage years were gone 23 years ago. Apparently it was take outta context, Sorry.
I think the issue I mentioned for CWM 5.0.2.7 is a shared issue with CWM 5.0.2.0, but I can't say for sure as I don't recall ever using CWM 5.0.2.0. I wasn't suggesting changing to the CWM I mentioned, was asking if that was the one you were/are using, which you've now stated you aren't. There error I was referring to would have been from CWM after flashing or trying to flash a ROM.
shinobisoft said:
Sorry you're having a bad day. Rest assured, if I was talking down to you, there wouldn't be any smilies. I was just expressing that you weren't the only one out there with stress in their life, and some of us have loads of it. On that note, I'm not one of the many teenagers around here. So I'm not talking down to you, but out of experience. My teenage years were gone 23 years ago. Apparently it was take outta context, Sorry.
I think the issue I mentioned for CWM 5.0.2.7 is a shared issue with CWM 5.0.2.0, but I can't say for sure as I don't recall ever using CWM 5.0.2.0. I wasn't suggesting changing to the CWM I mentioned, was asking if that was the one you were/are using, which you've now stated you aren't. There error I was referring to would have been from CWM after flashing or trying to flash a ROM.
Click to expand...
Click to collapse
Can that program add apps? If so or not. maybe I can edit the zip directly. but is it possible to port the old music player in Gingerbread to JB. I don't like Apollo. or would it just be better to remove Apollo and find something I like in Play store when i make this work?
And should i try to use CWM 5.0.2.7 instead, and try again?
EDIT: Says I have the latest according to this.
EDIT 2: just ROM Manger being a butt. going to the site directly. I see CWM 5.0.2.7 as the latest.
TroyFoxxin said:
Can that program add apps? If so or not. maybe I can edit the zip directly. but is it possible to port the old music player in Gingerbread to JB. I don't like Apollo. or would it just be better to remove Apollo and find something I like in Play store when i make this work?
And should i try to use CWM 5.0.2.7 instead, and try again?
EDIT: Says I have the latest according to this.
EDIT 2: just ROM Manger being a butt. going to the site directly. I see CWM 5.0.2.7 as the latest.
Click to expand...
Click to collapse
Yes apps can be added, but only as User Apps. Select "User Apps" in the treeview on the left. Then right click on the listview on the right and select the "Add apps" command item. A file dialog will appear. Multiple file selection is allowed.
You can remove Apollo. I prefer Google Play Music myself.
For your recovery. CWM 5.0.2.7 will only allow installing P500 ROMs. I do prefer the touch version of CWM, and since P509 is identical to P500, it's really not an issue other than baseband which is solved with a flashable patch. I really cannot recommend a recovery as we all have different likes/dislikes/usage patterns. I would recommend not using ROM Manager to install a recovery. It's been known to be faulty with our devices. Theres always ADB and fastboot or another one of my tools, Android Flash Recovery. There are several other apps around XDA that can do this also.
shinobisoft said:
Yes apps can be added, but only as User Apps. Select "User Apps" in the treeview on the left. Then right click on the listview on the right and select the "Add apps" command item. A file dialog will appear. Multiple file selection is allowed.
You can remove Apollo. I prefer Google Play Music myself.
For your recovery. CWM 5.0.2.7 will only allow installing P500 ROMs. I do prefer the touch version of CWM, and since P509 is identical to P500, it's really not an issue other than baseband which is solved with a flashable patch. I really cannot recommend a recovery as we all have different likes/dislikes/usage patterns. I would recommend not using ROM Manager to install a recovery. It's been known to be faulty with our devices. Theres always ADB and fastboot or another one of my tools, Android Flash Recovery. There are several other apps around XDA that can do this also.
Click to expand...
Click to collapse
Ill just leave it be then. Its always worked for me. if there was a problem it was with the ROM.
I haven't tried Google Play music before. but is it possible to port the music player from Gingerbread to JB?
but I'm getting the jiffs of that program. I just need to play with it. some things I converted to User apps never loaded at all.
So I need to play with what I can put in User data that will still work. but none the less i been getting the builds to install.
And even show Play Store again.
Just need to mess with what works and dont in User data.
-Edit-
I tried to Make LatinIME Smaller and convert it to Userdata in the build options but every build has no keyboard support.
TroyFoxxin said:
Ill just leave it be then. Its always worked for me. if there was a problem it was with the ROM.
I haven't tried Google Play music before. but is it possible to port the music player from Gingerbread to JB?
but I'm getting the jiffs of that program. I just need to play with it. some things I converted to User apps never loaded at all.
So I need to play with what I can put in User data that will still work. but none the less i been getting the builds to install.
And even show Play Store again.
Just need to mess with what works and dont in User data.
-Edit-
I tried to Make LatinIME Smaller and convert it to Userdata in the build options but every build has no keyboard support.
Click to expand...
Click to collapse
Is there anyway you can post the updater-scipt from one of the builds you've made with OOne ROM Editor where you've modified the LatinIME.apk and specified to install as a User App? The updater-script is located in the /META-INF/com/google/android folder in the output/build ROM.
One thing to note tho, build options are reset after every build.
shinobisoft said:
Is there anyway you can post the updater-scipt from one of the builds you've made with OOne ROM Editor where you've modified the LatinIME.apk and specified to install as a User App? The updater-script is located in the /META-INF/com/google/android folder in the output/build ROM.
One thing to note tho, build options are reset after every build.
Click to expand...
Click to collapse
I noticed that it resets everytime. so i been ontop of that. I check both boxes in the build options before I build them.
I did read also not to delete LatinME.apk. and use the editor. But i know the LatinME is a nice chunk of Memory.
So to make it smaller and usable in User apps is plus to make the important things I need working.
-Edit-
I haven't been saving the bad builds. that attachment was for a new build I haven't tried yet.
and I just did. now keyboard working. But I think that build I didn't tell it to put Latin in User apps that time.
But I did use the editor. So I don't know.
TroyFoxxin said:
I noticed that it resets everytime. so i been ontop of that. I check both boxes in the build options before I build them.
I did read also not to delete LatinME.apk. and use the editor. But i know the LatinME is a nice chunk of Memory.
So to make it smaller and usable in User apps is plus to make the important things I need working.
-Edit-
I haven't been saving the bad builds. that attachment was for a new build I haven't tried yet.
and I just did. now keyboard working. But I think that build I didn't tell it to put Latin in User apps that time.
But I did use the editor. So I don't know.
Click to expand...
Click to collapse
I can't tell what you installed as user apps from the updater-script, but there were apps installed to the user ( data ) partition. And the assert() statement is missing from the script, so I know that option was checked in the Build Options.
The reason I say not to manually move it is because the LatinIME Keyboard Editor should be used to edit it's dictionaries. Once you press the "Apply" button in the LatinIME Keyboard Editor, it removes the LatinIME.apk from System Apps and actually puts it in the apps Recycle Bin. I use the list of files in the Recycle Bin as a filter of files not to include when building the ROM. LatinIME Keyboard Editor also looks in the Recycle Bin for the LatinIME.apk if it can't find it in System Apps but it assumes that it's deleted so it won't do anything.
I am actually working on OOne ROM Editor right now. So you can be on the lookout for an update
shinobisoft said:
I can't tell what you installed as user apps from the updater-script, but there were apps installed to the user ( data ) partition. And the assert() statement is missing from the script, so I know that option was checked in the Build Options.
The reason I say not to manually move it is because the LatinIME Keyboard Editor should be used to edit it's dictionaries. Once you press the "Apply" button in the LatinIME Keyboard Editor, it removes the LatinIME.apk from System Apps and actually puts it in the apps Recycle Bin. I use the list of files in the Recycle Bin as a filter of files not to include when building the ROM. LatinIME Keyboard Editor also looks in the Recycle Bin for the LatinIME.apk if it can't find it in System Apps but it assumes that it's deleted so it won't do anything.
I am actually working on OOne ROM Editor right now. So you can be on the lookout for an update
Click to expand...
Click to collapse
Well I got everything to work. Keyboard, Play Store, etc. But not sure ill stick with trying to put JB on the phone.
Its really slow. Unless more free space on the system partition would allow it to run faster.
Would your OOne ROOM Editor work on Any rom Like a CM7 Rom? or just JB ones? if not would you consider support for other roms?
I haven't tried, but figure I would ask.
TroyFoxxin said:
Well I got everything to work. Keyboard, Play Store, etc. But not sure ill stick with trying to put JB on the phone.
Its really slow. Unless more free space on the system partition would allow it to run faster.
Would your OOne ROOM Editor work on Any rom Like a CM7 Rom? or just JB ones? if not would you consider support for other roms?
I haven't tried, but figure I would ask.
Click to expand...
Click to collapse
OOne ROM Editor is just for ICS and JB ROMs. It's really not needed for Android versions prior to 4.0.
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