Unfortunately the hoster where my build server is located raised the fees and i had no way to download a backup of my data... As i can't afford it now i had to delete everything. With a heavy heart I have to discontinue this great ROM for a great phone..
- first of all, thanks to @tdm for his tremendous effort to have us all enjoy LineageOS in the first place, without his contribution this thread would never exist. Also thanks for tdm's Lineage 14.1 where I took this post's layout from -
{
"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"
}
Gentlemen,
The time has come to share what's due to be shared.
Supported devices
* US model running 7.1.1 b14 firmware
* EU model running 7.1.1 b12 firmware
Pre-requisites
Make sure to have at least this TWRP version installed
Patience as first start takes a while
First time install Instructions
Use these instructions when coming from any other ROM (stock, AOKP, LineageOS 15.1, etc.)
Download ROM.
Download GAPPS if desired.
Boot into recovery.
Backup your current data.
Format/Wipe 'Dalvik/ART Cache', 'System', 'Data' and 'Cache'
Flash ROM.
Flash GAPPS if desired.
Reboot.
Upgrade instructions
Use these instructions when upgrading from a previous Lineage 16.0 build.
Download ROM.
Boot into recovery.
Backup your current data.
Flash ROM.
Reboot.
Flashing instructions
There are two main ways to flash files onto your phone: local and sideload. Most people are only familiar with local, but sideload is much quicker and easier if you are at a PC.
Sideload
Download the ZIP file(s) to your PC. In TWRP, select advanced and then sideload. Swipe the slider to begin, then on your PC run "adb sideload <filename>".
Local
Download and/or copy the ZIP file(s) to your phone. Note whether they are on internal storage (the default) or the sdcard. In TWRP, select install, find your file, and select it.
Status
This is currently stable quality
Known issues
Very minor graphical glitches
sometimes videos don't play, you have to remove the relevant all from your recent app list and restart (e.g. WhatsApp)
AKM DAC is not supported
Selinux permissive
To Do list
Implement Camera2 API Thanks for customizing libraries and not sharing any code or insight ZTE
Get DSP to kick in for high quality audio again
Download
Google Drive
* works well with open gapps
Sources
Device tree
Kernel
Vendor
Note: please refrain from requesting other Android distributions from me, like AOKP, AOSP, etc - this is most likely not going to happen from my end. As I provided all my sources you can fork the stuff yourself and try to build
Special thanks
@R3bornD4rth for having provided me an axon 7 mini for my testing/debugging, which is heavily in use and doing great so far
@tdm for his original work on this
@armandop_ for his ZMAX Pro Repo and help getting LiveDisplay to work (flawlessly, thanks mate)
intervigilium aka Ethan Chen for his work on HTC One A9 (hiae) (which shares the same chipset as our phones)
Thanks for this rom, there's a way to make work the camera API 2 (in the future)?
jose_777.mx said:
Thanks for this rom, there's a way to make work the camera API 2 (in the future)?
Click to expand...
Click to collapse
Good question, no clue if I will be making it to work somehow I can try to get some pointers if there are just some drivers to be altered or whatever is needed to have this done
I installed magisc 19.1, and dolby for better sound.Now it is my dayly driver,
Thanks Man!
bius88 said:
I installed magisc 19.1, and dolby for better sound.Now it is my dayly driver,
Thanks Man!
Click to expand...
Click to collapse
Cool!
Would be better if GPS and Cam would work though I am working on GPS right now, will soon test my latest build, so fingers crossed
Working well with open gapps 9 micro.
Play store works
Pixel launcher fc.
Camera works. The app doesn't. Download any other camera and you're good.
Looking great so far
Thanks
Holyoblation said:
Working well with open gapps 9 micro.
Play store works
Pixel launcher fc.
Camera works. The app doesn't. Download any other camera and you're good.
Looking great so far
Thanks
Click to expand...
Click to collapse
What? The camera really works? Then I shall replace the camera app with another one maybe ?
Works great with opengapps pico too i am using this for a day and there is not a big issue i will share if any unexpected issue happens. Thx for your effort
EDIT: I think there is still a problem with camera. i tried it with 2 applications and one game.
I have problem with instagram videos i cant play them.
Cant open flashlight from quick settings.
koktey14 said:
Works great with opengapps pico too i am using this for a day and there is not a big issue i will share if any unexpected issue happens. Thx for your effort
EDIT: I think there is still a problem with camera. i tried it with 2 applications and one game.
I have problem with instagram videos i cant play them.
Cant open flashlight from quick settings.
Click to expand...
Click to collapse
I see 2 issues here to be fixed. first with the video playing will be added to my known bugs post, the flashlight thing is related to the camera not working (pretty sure at least)
Small update: unfortunately I can't find a reason why GPS is not working on LOS16, but worked in LOS15.1, even just taking the files from 15.1 and placing them in 16 didn't help. The error messages in the log are not disclosing enough information what exactly the issue could be, just getting loads of invalid handle errors. Comparing with other msm8952 chipsets I don't really see any differences, so I am clueless now
TheSSJ said:
Small update: unfortunately I can't find a reason why GPS is not working on LOS16, but worked in LOS15.1, even just taking the files from 15.1 and placing them in 16 didn't help. The error messages in the log are not disclosing enough information what exactly the issue could be, just getting loads of invalid handle errors. Comparing with other msm8952 chipsets I don't really see any differences, so I am clueless now
Click to expand...
Click to collapse
Can there be a chain problem with sim card, graphics or camera maybe
koktey14 said:
Can there be a chain problem with sim card, graphics or camera maybe
Click to expand...
Click to collapse
Well, this really looks like it - I reverted back to the state where I took over from tdm and applied just the modifications to make nfc, wifi, bt, radio to work. Now GPS works, but wifi went back to sometimes fail to start where you have to reboot to make it actually work again.. it seems something I added along the lines fixed the issue with wifi and another one broke GPS
I am trying to fix wifi now somehow to make it behave stable again, then we can enjoy even a fixed GPS phone
Next stop is camera (after I repaired wifi)
TheSSJ said:
Well, this really looks like it - I reverted back to the state where I took over from tdm and applied just the modifications to make nfc, wifi, bt, radio to work. Now GPS works, but wifi went back to sometimes fail to start where you have to reboot to make it actually work again.. it seems something I added along the lines fixed the issue with wifi and another one broke GPS
I am trying to fix wifi now somehow to make it behave stable again, then we can enjoy even a fixed GPS phone
Next stop is camera (after I repaired wifi)
Click to expand...
Click to collapse
Apparently I fixed wifi I rebooted 15 times to be sure and it always turned on, GPS still functioning as well!
I will update the OP and proceed with cam (which is so broken that not even 3rd party apps work at the moment)
EDIT: Notification lights fixed as well
@TheSSJ -Great Work man!
Will try it out as soon as I get a chance
edit - is the TWRP version the same as Oreo or a newer one ?
edit 2 - Are you building an Aokp version ?
Hi, thanks for the hard work. Does the firmware support fast charging?
BAPK said:
Hi, thanks for the hard work. Does the firmware support fast charging?
Click to expand...
Click to collapse
Yes, as this is setup on kernel side the stock settings have been just kept
k500zm;79544339 [user=2388665 said:
@TheSSJ[/user] -Great Work man!
Will try it out as soon as I get a chance
edit - is the TWRP version the same as Oreo or a newer one ?
edit 2 - Are you building an Aokp version ?
Click to expand...
Click to collapse
Twrp is the same with oreo i installed it.
I was thinking about aokp too but didnt want to put pressure on you. you are already busy. @TheSSJ what do you think about this?
Once I fixed all issues with LOS16, compiling aokp should not be too hard, but I can't promise it
Now i installed the new build but i have a problem. First i made an update but i wasnt able to open get through lock screen after that i made a clean install but now it is too laggy always freezing. Its too difficult to use this build.
koktey14 said:
Now i installed the new build but i have a problem. First i made an update but i wasnt able to open get through lock screen after that i made a clean install but now it is too laggy always freezing. Its too difficult to use this build.
Click to expand...
Click to collapse
Strange,i just clean installed and it is working really fast
Can you provide dmesg and logcat please, then I can check
Related
{
"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"
}
Minidoudou is available online! There is still work to do, but it is already fully functional and you can try it on to configure your own mod of CyanogenMod 6.1.0 for HTC Dream / Sapphire.
Try it on here: http://minidoudou.joelcogen.com
and let me know what you think!
Todo (in the order it will be done, probably)
- Connect to an external storage provider (sendspace)
- Make it pretty
- Fix IE UI issues
- Add system/data option, with a nice drag&drop
- Add advanced mode, with moving of any APK in the ROM
- Display "hand" cursor on draggable elements
- Check /system size
- Fix changes application order
- Add deprecation to APKs
- Users management for contributors
- Select field for mutually exclusive packages (kernel)
- Fix double upload issue
- Whatever you suggest below
There has already been some discussion about how much control to include, so here is a first poll: How much control would you like when using Minidoudou?
I'm not sure if it's the rom or my phone,
But I've used your rom, and ir worked great.
When I walked trough the city that evening
I was looking for wifi (without passwords) when I found one,
I tried to connect, but it only said, getting IP adress, connecting and again getting IP,...
Even on my home wifi I had this problem. So i did a full wipe and reinstalled the minimou Final version.
Can you please tell me if this is rom based or just bad luck with the wifi on my phone?
And you are doing a great job, I also tried smoki rom, but it had some lag on the UI.
It would be nice aswell if we could put custom icons (of the topbar) and custom battery Icon
milowke said:
I was looking for wifi (without passwords) when I found one,
I tried to connect, but it only said, getting IP adress, connecting and again getting IP,...
Even on my home wifi I had this problem. So i did a full wipe and reinstalled the minimou Final version.
Click to expand...
Click to collapse
Hi,
You're the first to report wifi problems, so I'll look into it.
As for the icons, it might be hard because that means customizing the theme, something I don't have a lot of luck with. I'm keeping it in mind, and once it is stable and has most of its functionnalities regarding packages, I'll look into it or for a contributor with theming experience.
Thanks for your feedback!
jojotm said:
Hi,
You're the first to report wifi problems, so I'll look into it.
As for the icons, it might be hard because that means customizing the theme, something I don't have a lot of luck with. I'm keeping it in mind, and once it is stable and has most of its functionnalities regarding packages, I'll look into it or for a contributor with theming experience.
Thanks for your feedback!
Click to expand...
Click to collapse
Your welcome,
And Thank you for your work on this lovely rom.
I have made a new package on your website, and i'm going to use it again.
I'll report any issues I have
Not sure if I'm allowed to do this double post thing.
But when I tried to download the rom I found an issue.
Wen you click on download you get the link like this
http://minidoudou.joelcogen.com/download/MDD_HTC_Sapphire_CyanogenMod_610_RC1_Milow_Testingzip
So when you save it, it's just a file, no zip file
So you have to put a dot in front of the zip yourself
NOt sure if you noticed it
milowke said:
Wen you click on download you get the link like this
http://minidoudou.joelcogen.com/download/MDD_HTC_Sapphire_CyanogenMod_610_RC1_Milow_Testingzip
Click to expand...
Click to collapse
Didn't notice that. It's fixed.
Sent from my HTC Magic using XDA App
Hi
I have done a clean install of minimou final, and after it I did the install of
the minidoudou. But it seems to have an endless boot up
It's stuck on the Proximus logo for 15 minutes now.
I have the following things in my minidoudou:
Advanced Task Killer 1.9.3
Browser CM6.1.0-RC1
StopWatch & Timer 1.15
aNetShare (wireless tethering) 2.30
Twitter 1.0.5
XDA developers 1.3.2
Gapps MDPI MDD 2010.10.20
Facebook 1.4.0
Sapphire 32A kernel - Brian Crook Nightly 231
Barcode Scanner 3.5
LauncherPro 0.8.1.1
Email CM6.1.0-RC1
I have the same SPL, RADIO, HBOOT as you I only use another recovery
RA magic v1.7.0.1
Whats wrong on this ?
*EDIT*
I will try to do just a clean install of minidoudou, without extra apps
But i'm wondering, Do I need to install minimou final and than install the minidoudou?
OK I did a full wipe
and I installed the minidoudou,
this package:
Gapps MDPI MDD 2010.10.20
Sapphire 32A kernel - Brian Crook Nightly 231
LauncherPro 0.8.1.1
On the wizard, I had to connect to WIFI for the google account.
Well It found my wifi, typed in the password, but it was the same
Retrieving IP adress
remember
Connecting
and it keeps repeating.
I installed minimou Final again, cause I realy need WIFI.
I'll try again if it's fixed.
milowke said:
I have done a clean install of minimou final, and after it I did the install of
the minidoudou. But it seems to have an endless boot up
It's stuck on the Proximus logo for 15 minutes now.
I will try to do just a clean install of minidoudou, without extra apps
But i'm wondering, Do I need to install minimou final and than install the minidoudou?
Click to expand...
Click to collapse
Hi again,
I just tried your config over a Minimou-final install (already with several of packages) and it seems to work.
It might be a LauncherPro problem, I remember it gave me trouble when building Minimou-final, so maybe flashing a non-upgraded Minimou with MDD causes the problem. Try fully upgrading your Minimou, then flashing MDD.
If it still doesn't work, the best solution is usually to do an 'adb logcat' (from the android sdk tools) to see the phone's log and look up the error message, or post the result here.
MDD is a separate project from Minimou, they're only link is me, so you don't need Minimou to flash, you can wipe from the recovery and then flash and it should work fine.
On the sidenote, in the future it would be easier if you just post your config name rather than the set of packages. It makes for shorter posts and it's easier to find (I compare the list to download your config).
Ok I did installed minimou final, and did the wizard thing,
Since launcher pro was expired I had to download the newest version.
When it was installed everything was working fine.
So I disabled wifi and let my phone forget my wifi settings.
After it I flashed MDD (Clean_without_Launcher(UPGRADE))
It took about 5-7 Minutes to boot,
I tried wifi, and it worked
I hope this info was helpfull for you.
Great! This LauncherPro problem is a real *****, I don't know why upgrading is such a problem.
The WiFi is stranger. I still have to look into it, I'll see if I can reproduce it.
jojotm said:
Great! This LauncherPro problem is a real *****, I don't know why upgrading is such a problem.
The WiFi is stranger. I still have to look into it, I'll see if I can reproduce it.
Click to expand...
Click to collapse
OKi, thnx.
Maybe it's just your launcherpro apk?
cause when I installed minimou final, installed launcherpro from the maker his website, and upgraded to MDD (without extra apps (no launcher as well), it worked fine, when I did the same but with launcher in the MDD package it failed at the wifi connection.
Even a clean install of MDD with launcher (cause you need one) failed so.
NOt sure if it's the same with the AWD launcher.
Anyone happen to have problems with gps? 2 of my apps (Sygic and iGO) are crashing after moving to RC1. I don't blame minidoudou but just wanted to see if i'm the only one. I'm running bcrooks kernel.
saibot64 said:
Anyone happen to have problems with gps? 2 of my apps (Sygic and iGO) are crashing after moving to RC1. I don't blame minidoudou but just wanted to see if i'm the only one. I'm running bcrooks kernel.
Click to expand...
Click to collapse
Uhm, I didn't tried the GPS yet.
Do they crash when you open the app or when you are using it for a couple minutes?
Sygic freezes when i want to create a rather long (1k KM) route.. so i think it's Sygic's fault. It might not be compatible with 2.2.1. I'll try some other software as 'gps essentials' appears to be working fine.
On another note i cannot install brut's google maps... tried removing the original google maps, they're SapphireMaps package?
Thanks in advance for any help.
saibot64 said:
Sygic freezes when i want to create a rather long (1k KM) route.. so i think it's Sygic's fault. It might not be compatible with 2.2.1. I'll try some other software as 'gps essentials' appears to be working fine.
On another note i cannot install brut's google maps... tried removing the original google maps, they're SapphireMaps package?
Thanks in advance for any help.
Click to expand...
Click to collapse
Well I tried Navigon and it worked fine, couldn't try Sygic's GPS cause it needed 3D acceleration.
You can't remove the original google maps indeed. they are in the package.
As for the brut's google maps, you should look over here
http://forum.xda-developers.com/showthread.php?t=630887
try this one: maps4.6.0.4686-brut-renamed.apk
Same here, I only tried Google Navigation and it worked fine.
Regarding Maps, you can't remove them because they are in /system, but I'll add the option to install in /data to MDD soon. I remember having trouble updating it in the past, but I don't see why, because other /system packages can usually be updated just fine....
Hello, i tried to cook a rom yesterday using minidoudou but it still says "Pending" along with some others!
Also when i press on "x packages" to see what packages other roms include, i get an error with firefox 3.6.12. With chrome there is no such problem.
Thanks again for the great work.
I like this idea a lot. Kudos to the developer(s).
Can we add different devices? Per say the G1?
{
"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.
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.
These builds are unofficial, unsupported by the LiquidSmooth team. Do not file bug reports to the Liquidsmooth devs -- instead please post them in this thread.
What is LiquidSmooth? Find more information here: Official LiquidSmooth G+ Community
Installation instructions:
Backup what is precious to you
Wipe system, data and cache
Flash ROM (link below)
Flash gapps (link below)
Reboot and wait for welcome screen
Downloads:
Liquid-JB-v2.37-UNOFFICIAL-20131106-ovation.zip - 105.01 MB
Standard Gapps: Goo.im - gapps-jb-20130813-signed.zip
Slim Gapps (compatible with "Dark Liquid" switch): Slim Gapps download page
Banks's basic Gapps (absolute minimal gapps install): XDA thread
Known issues/bugs
Text strings in the UI are a bit wonky, especially those for Wi-Fi and Bluetooth (i.e. "deny" instead of "connect" when adding a new Wi-Fi network)
Bluetooth tethering does not work. Fixed in 2013-11-06
Potentially there can be some rotation bugs. LMK if you identify any
There is not Tablet UI available, and auto-patcher does not support LiquidSmooth at this point
Generic screenshot showing LS features
{
"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"
}
Interesting...
Sent from my Nook HD+ using xda app-developers app
It looks nice is trim disabled?
Sent from my PC36100 using xda app-developers app
jpisini said:
It looks nice is trim disabled?
Sent from my PC36100 using xda app-developers app
Click to expand...
Click to collapse
+1.... would like to try if it's disabled (I have the chip that can be potentially bricked by trim).
320flyboy320 said:
+1.... would like to try if it's disabled (I have the chip that can be potentially bricked by trim).
Click to expand...
Click to collapse
Trim is disabled.
TY!! but wifi doesn't work for me
------------------------------------------------------------
oh, it woks after fixing permission @twrp. TY again!
Looks good. I will try to flash this this weekend.
Sent from my LG-LS855 using Tapatalk 2
Just noticed on the settings screen, and if you tap on BATTERY, settings crashes. Other than that, it's working good so far...:good:
320flyboy320 said:
Just noticed on the settings screen, and if you tap on BATTERY, settings crashes. Other than that, it's working good so far...:good:
Click to expand...
Click to collapse
flyboy,
As the other poster mentioned, I too can't get WiFi to work. How did you get past the initial start up settings procedure? Setup won't let me skip logging into a network so I'm stuck.
smithmal
Edit - figured it out. When setting up tablet on the "Wifi Select" screen, for some reason when adding a network, network settings cannot be saved (seeing this when manually adding a SSID as I have mine hidden). Click "Skip" and then click "Cancel" and then setup will finish.
Still cannot manually add my hidden SSID though so I can't connect to my WiFi network.
Ya WiFi is for sure screwed up. I did manage to add my hidden SSID after trying a few times. Although as with the APPS in SETTINGS the button names seem to be messed up. If I try to uninstall an app, I only get the option to either INSTALL or SDCARD...bit weird...:silly:
Could you please in the next release, switch the release flag here to false, this makes it so the build is Unofficial.
I really like the boot animation on the ROM!
Sent from my LG-LS855 using Tapatalk 2
320flyboy320 said:
Ya WiFi is for sure screwed up. I did manage to add my hidden SSID after trying a few times. Although as with the APPS in SETTINGS the button names seem to be messed up. If I try to uninstall an app, I only get the option to either INSTALL or SDCARD...bit weird...:silly:
Click to expand...
Click to collapse
I'll have a look at these issues (starting with Wi-Fi) and try to fix them next week.
deadman96385 said:
Could you please in the next release, switch the release flag here to false, this makes it so the build is Unofficial.
Click to expand...
Click to collapse
Will do.
jisoo said:
I'll have a look at these issues (starting with Wi-Fi) and try to fix them next week.
Will do.
Click to expand...
Click to collapse
I. Noticed something odd with the WiFi this weekend. I flashed the ROM on Friday,, and then yesterday I messed something up while restoring some stuff so I did another clean flash. This time I used the "minimal gapps" and when I tried setting up, it would not even show any of the 4or 5 access points nearby. And nothing I tried would produce any results.
So,, I went back and flashed the AIO gapps and then all the AP's showed up and I was able to log on to it.
Just thought I'd share. I think it's kinda odd that the gapps would make a difference in being able to see wifi.
Sent from my Nook HD+ with unofficial LiquidSmooth on emmc using Tapatalk 4
bpaulien said:
I. Noticed something odd with the WiFi this weekend. I flashed the ROM on Friday,, and then yesterday I messed something up while restoring some stuff so I did another clean flash. This time I used the "minimal gapps" and when I tried setting up, it would not even show any of the 4or 5 access points nearby. And nothing I tried would produce any results.
So,, I went back and flashed the AIO gapps and then all the AP's showed up and I was able to log on to it.
Just thought I'd share. I think it's kinda odd that the gapps would make a difference in being able to see wifi.
Sent from my Nook HD+ with unofficial LiquidSmooth on emmc using Tapatalk 4
Click to expand...
Click to collapse
Interesting. Are you refering to the AIO gapps listed for Slimbean (see here) or full CM listed 4.3 gapps (08/13/2013 gapps). I've tried this with the Slimbean AIO gapps and it didn't work (re-flashed it a couple time to make sure). I wonder if going from minimal gapps to AIO gapps is the trick?
Also, after getting all your APs to show up is LiquidSmooth supporting BT? As I recalled BT worked, I just couldn't connect to my AP.
Edit: Tried installing with minimal first and then re-flash AIO and I can't save password for my AP. Once password is entered I only have two options: "Failed to save network" and "Deny"
smithmal
Guys,
Sorry about the WiFi problems. I tested this build with no gapps and it worked ok for me, so I didn't know about the issues.
I'm a bit busy at work right now, but I will get back to this at the end of the week and try to put up a better working build.
I have no issues with WiFi
Sent from my BN NookHD+ using XDA Premium 4 mobile app
smithmal said:
Interesting. Are you refering to the AIO gapps listed for Slimbean (see here) or full CM listed 4.3 gapps (08/13/2013 gapps). I've tried this with the Slimbean AIO gapps and it didn't work (re-flashed it a couple time to make sure). I wonder if going from minimal gapps to AIO gapps is the trick?
Also, after getting all your APs to show up is LiquidSmooth supporting BT? As I recalled BT worked, I just couldn't connect to my AP.
Edit: Tried installing with minimal first and then re-flash AIO and I can't save password for my AP. Once password is entered I only have two options: "Failed to save network" and "Deny"
smithmal
Click to expand...
Click to collapse
I was referring to the SlimBean AIO.
The very first time I flashed it, I used the one (can't remember its name) that pulls up the interface where you can pick and choose the gapps you want to install. That worked for me.
Then when I re-flashed (clean) I just wanted to get going, and didn't really care what was on it, so did the minimal gapps. That's when I couldn't see any WiFi Access Points. But since I knew I had gotten access to WiFi the first time, I figured there had to be something different between my 2 flashes. But not wanting to go through and select things again, I just flashed the AIO gapps over everything. That time WiFi worked.
I can't answer about BT. I'm not using any BT connections with my Nook at this time.
And as to your edit, I think I got some kind of error message too, but when I got to the next part, where you log into your google account, it had access and everything worked. So despite the error message regarding WiFi, I was able to continue, and haven't really had any WiFi issues with it.
So I've uploaded a new build for v2.37.
I tested Wi-Fi, and although the text strings in the UI are wrong (for instance it says "deny" where it should say "connect"), Wi-Fi and BT tethering now work as far as I can test.
I also merged all of the bug fixes and cleanups the LiquidSmooth team has added since the last build, but these are quite minor. There does not seem to be any new features coming into the 4.3/JB3 branch. This is the case for more or less all ROMs, as everyone is busy rebasing and merging functionality into the 4.4 branches.
The new build is also properly marked as unofficial, as requested by the LiquidSmooth devs.
jisoo,
Thanks for this ROM, your work porting this to the HD+ is much appreciated. I loaded this up and took it for a spin earlier today. WiFi connection is still a bit dicey. It took me three or four times before it would connect (using WPA2 security on my network), but the tablet did finally connect. It seemed my signal strength was a bit lower than other ROMs, but I don't have any hard data to support that.
The ROM seemed snappy enough (coming from the Slimbean ROM which is very responsive). BT turned on when selecting it, but I haven't gotten a chance to test it yet so that's on my list.
I will do some more tests on DL speeds/UL speeds/WiFi strength later tonight and let you know.
smithmal
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