Related
Highly experimental stuff:
Release candidates and nightly builds available via Rom-Manager.
Description:
CyanogenMod has nightly builds for Legend since Sept. 30 2010 as it's become an officially supported device. I will provide experimental builds (for public beta testing) here from time to time. No files available for the moment.
Please adhere to a few rules when discussing builds in here.
Read and search before you post.
Do not request help. This is the development board.
Requests for builds, features, fixes or apps to include will be ignored.
Do not report broken or not installable apps from the Market (we can't fix them).
Do not expect bugs to be fixed.
Credits:
Thanks go out to the whole CM team for their great work!
Beer / Coffee:
Additional stuff:
Some people experience GPS issues. To help us debug, flash that verbose module and get a full log via adb:
gps-test.zip (gps.legend.so)
EDIT.
Got it.
differences beetween azure and dark azure?
screenshots will be appreciated
thanks for your work
It will be same as Azure 1.0 , but with a Dark Theme , and some bug fixes.
This, Ali Ba, is a really neat idea.
rajasyaitan said:
What is this exactly? An Azure mod?
Click to expand...
Click to collapse
Lostpassword said:
differences beetween azure and dark azure?
Click to expand...
Click to collapse
dhanu007 said:
It will be same as Azure 1.0 , but with a Dark Theme , and some bug changes.
Click to expand...
Click to collapse
You really did not read the first post. Not even the second sentence.
dhanu007 said:
...and some bug changes.
Click to expand...
Click to collapse
As a software developer I like that wording - much more accurate than "bug fixes"
Need idea love having Android in black...
TCarlsen said:
Need idea love having Android in black...
Click to expand...
Click to collapse
Bloody hell, who wrote this was a mod? Does anyone of you even understand what "nightly build" means?
What is this board here? Kindergarten?
You made my day, thank you!
Message removed
So what is a nighty build then ? I know m a Noob
dhanu007 said:
So what is a nighty build then ? I know m a Noob
Click to expand...
Click to collapse
"Nightly builds are daily compiled builds from the source, therefore have the latest features & tweaks, but will are mostly likely to break due being fresh, not fully tested code. "
Great idea, but dangerous! Like, I almost choked on my coffee while starting to laugh over the comments in this thread!!
<irony>But finally we can have a black themed ROM ! * </irony> lol This thread made my day, seriously!
Edit: Don't want to spam the thread with useless comments, sorry bout that, but this was too hilarious!!
Good start.
No, but seriously, dont let the kids make you nervous.
Carry on with the good work.
Poor Ali Ba, wrestling with incompetent fools. But we were all there. I'm still there. But at least I understood what he mean by nightly builds I suppose...
Thanks, ali ba. Would you consider automating the builds, or do the patches you apply to CM for Legend support break frequently?
I've always been curious of why you haven't submitted your patches upstream to CM, but that's for another discussion.
Ah, nightly builds I love em!
I work in a game studio, nightly builds cause me nothing but pain as an animator ;D
pfak said:
Thanks, ali ba. Would you consider automating the builds, or do the patches you apply to CM for Legend support break frequently?
Click to expand...
Click to collapse
Nope, no automated builds planned. Thus inverted commas in "nightly" builds.
pfak said:
I've always been curious of why you haven't submitted your patches upstream to CM, but that's for another discussion.
Click to expand...
Click to collapse
I submitted all that were useful enough and not breaking anything else.
The most critical one being the lights patch because CM code is still written as if every device had a trackball RGB light. Will most likely never submit that one.
09/07 online.
It seems in almost all the jelly bean roms the problems of loss of ringtones & Notification sounds etc. and FCing of certain apps persists. I read all the threads of the JB roms but no solution found. The threads are flooded with these complaints. I would request everyone to discuss this problem here. This is a request to Developers to please help us solve this problem. People with solutions please post.
Thanx in Advance
alokcool13 said:
It seems in almost all the jelly bean roms the problems of loss of ringtones & Notification sounds etc. and FCing of certain apps persists. I read all the threads of the JB roms but no solution found. The threads are flooded with these complaints. I would request everyone to discuss this problem here. This is a request to Developers to please help us solve this problem. People with solutions please post.
Thanx in Advance
Click to expand...
Click to collapse
Check how much free space you have in /datadata.
CM9 had checks in place to monitor the state of /datadata, but these early JB ROMs don't. If its getting filled it may be causing problems with the media scanner.
alokcool13 said:
It seems in almost all the jelly bean roms the problems of loss of ringtones & Notification sounds etc. and FCing of certain apps persists. I read all the threads of the JB roms but no solution found. The threads are flooded with these complaints. I would request everyone to discuss this problem here. This is a request to Developers to please help us solve this problem. People with solutions please post.
Thanx in Advance
Click to expand...
Click to collapse
Wrong Section!!! This discussion doesnt belong here... and one more thing... JB for SGS is still in its early period of development so dont expect everything to work perfectly... there might be some hiccups... jus follow the instructions of developers in OP of respective threads and u will not run into problems...
Oh ya me tooooooo it is really annoying
Sent from my GT-I9000 using xda premium
just copy the system/media/audio from cm9 and the problem should be fixed but you might not have enough space for it (thats why it was deleted)
alokcool13 said:
It seems in almost all the jelly bean roms the problems of loss of ringtones & Notification sounds etc. and FCing of certain apps persists. I read all the threads of the JB roms but no solution found. The threads are flooded with these complaints. I would request everyone to discuss this problem here. This is a request to Developers to please help us solve this problem. People with solutions please post.
Thanx in Advance
Click to expand...
Click to collapse
Come on, it's Alpha - state.....
wait at least for the rom to be Beta and advance towards RC, devs have a lot to take care about right now and I'm sure the media-related problems are part of their work for future releases.
Stick to OPs of the roms if you'd like to try them out this soon or wait for Beta and follow the respective thread before flashing to get the current status of known bugs and workarounds.
my opinion
hassanalip21 said:
Oh ya me tooooooo it is really annoying
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
do you know what's really annoying ....
People with those big F**king banners in there signature
alokcool13 said:
It seems in almost all the jelly bean roms the problems of loss of ringtones & Notification sounds etc. and FCing of certain apps persists. I read all the threads of the JB roms but no solution found. The threads are flooded with these complaints. I would request everyone to discuss this problem here. This is a request to Developers to please help us solve this problem. People with solutions please post.
Thanx in Advance
Click to expand...
Click to collapse
And what do you think devs on the ALPHA builds of JellyBean are doing??? OMG really?!?! Do you know that ALPHA isn't even a BETA?!?!? that means that some stuff just will not work like on regular GB / ICS builds!!
Want stability and no bugs? go to GB or ICS, there are plenty of very stable GB and ICS roms around here!!!
-m3ta- said:
And what do you think devs on the ALPHA builds of JellyBean are doing??? OMG really?!?! Do you know that ALPHA isn't even a BETA?!?!? that means that some stuff just will not work like on regular GB / ICS builds!!
Want stability and no bugs? go to GB or ICS, there are plenty of very stable GB and ICS roms around here!!!
Click to expand...
Click to collapse
If you didn't have any solution then u shouldn't have posted. XDA is community site and everyone has right to ask whatever he wants. And by this threat I m not complaining to any developers ! Read the op again ! It is not a complain ! I just opened this so people could find the solution which can be included in future updates of the ROM. I know I shouldn't open a threat for every problem but this problem was not so minor ! Do u understand that ?! I don't know why some people just like to criticize others initiative. I very well know its alpha built and errors are bound to happen. Its not always that the developers have to solve all the problems alone for their rom, we can initiate too! Together !
Sent from my GT-I9000 using xda premium
rajeshbabushrestha said:
Wrong Section!!! This discussion doesnt belong here... and one more thing... JB for SGS is still in its early period of development so dont expect everything to work perfectly... there might be some hiccups... jus follow the instructions of developers in OP of respective threads and u will not run into problems...
Click to expand...
Click to collapse
Is it wrong for people to find solutions for bugs in alpha builds ? If no one tries to fix bugs saying that this is alpha, we would never have a better rom than! The development stops !
I apologize for putting in wrong section.
Sent from my GT-I9000 using xda premium
alokcool13 said:
Is it wrong for people to find solutions for bugs in alpha builds ? If no one tries to fix bugs saying that this is alpha, we would never have a better rom than! The development stops !
I apologize for putting in wrong section.
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
No need to apologize bro... ur intention is good but u should know better that posting queries in development section is always equal to getting flamed from fellow xda users... anyways moderators will move this thread to QnA/general... u can also request the moderators to move this thread to general section. abt ur concern regarding bugfixes... pawitp has set up bug reporting system in his cm10 thread... here we can submit bug reports with logcat and he will try to fix them... even we can try to fix the bugs and submit code in cyanogenmod gerrit for reviews and if verified then it will be merged into cm code... hence profit.
My fix: copy the entire audio folder from /system/media to /sdcard/media.
This way all your sounds will exist twice (although you will only see them once), but after the media scanner finishes scanning, they won't disappear anymore.
Ringtones are back.
MrMagic said:
My fix: copy the entire audio folder from /system/media to /sdcard/media.
This way all your sounds will exist twice (although you will only see them once), but after the media scanner finishes scanning, they won't disappear anymore.
Click to expand...
Click to collapse
Thank you.. :good:
I did and it worked.
Only that I like the old classic ring tone. Had to listen and found 'Pyxis' is what i am looking for..
I copied (using Solid Explorer) folder system\audio (Jump option at the bottom, Device/System root took me to where system folder is. Then scrolled to \system\media, long press the audio folder and clicked on copy, again jump/device/internal memory and scrolled to media folder, long pressed on media folder and chose paste. done..
Ringtones are back.
raf33k said:
Thank you.. :good:
I did and it worked.
Only that I like the old classic ring tone. Had to listen and found 'Pyxis' is what i am looking for..
I copied (using Solid Explorer) folder system\audio (Jump option at the bottom, Device/System root took me to where system folder is. Then scrolled to \system\media, long press the audio folder and clicked on copy, again jump/device/internal memory and scrolled to media folder, long pressed on media folder and chose paste. done..
Click to expand...
Click to collapse
ignore if you already got solution
For ringtone problem,
1. install root explorer app
2. go to System-> Media -> Audio
3. Mount as R/w, ignore if already mounted in R/w
4. Long press on folder(Ringtones folder,Notifications folder) and go to permissions
5. Set RW-R-R style.
6. Reboot the mobile.
by this you can see all the ringtones avail in your mobile but cant listen while setting them, but will work as it should.
Regards,
Praveen.
alokcool13 said:
It seems in almost all the jelly bean roms the problems of loss of ringtones & Notification sounds etc. and FCing of certain apps persists. I read all the threads of the JB roms but no solution found. The threads are flooded with these complaints. I would request everyone to discuss this problem here. This is a request to Developers to please help us solve this problem. People with solutions please post.
Thanx in Advance
Click to expand...
Click to collapse
The latest Building of the cm10 nightly (08/08/12) doesn't have this issue, i'm running it and have all my ringtones and notification sounds
Who has this problem , and who was able to solve it and how??
my info :
Smallbandversion : S6500DXXMD1
Kernel : 2.6.38.6- thewhisp
CM version : 10.1-20130707
Build number : 142053 test-keys
Any version higher : White screen bug after CM setup.
what's the point of creating a new thread about it everyday?
TheWhisp said:
what's the point of creating a new thread about it everyday?
Click to expand...
Click to collapse
Hoping to get it solved , or sort out why certain people have this problem? Its not because the DEV doesn't have this problem others are in the same situation. We like your work but we would also like to use the latest rom version. thats why i created this ticket.
it's been discussed in all of the dev threads, discussions threads, github + "million" other topics have been created. Isn't that enough? I've already posted a test boot.img. If the people with "white screen" issue don't want to test it, it's not my problem
TheWhisp said:
it's been discussed in all of the dev threads, discussions threads, github + "million" other topics have been created. Isn't that enough? I've already posted a test boot.img. If the people with "white screen" issue don't want to test it, it's not my problem
Click to expand...
Click to collapse
I have been trying to follow all the topics / replies regarding the whitescreen bug , I saw once you typed about the boot.img and a couple people tested didn't work , u created a new version didn't work either and then no newer versions anymore to test
I posted a new boot.img just before you created this thread...
TheWhisp said:
I posted a new boot.img just before you created this thread...
Click to expand...
Click to collapse
Hi TheWhisp i test the boot.img and the result in the dev page
Discontinued.
Awaiting for thread deletion.
Thanks...Nice work after your miui 5 ROM
Help please..
Need someone who can risk his device by testing this ROM......
Happy holi.....
Happy holi my friends...
May this holi bring lots of Colors in your life!! and in mine too.
Kunal Gautam said:
Need someone who can risk his device by testing this ROM......
Click to expand...
Click to collapse
I tried to install but it gives error 7 i think update.script should be rechecked.
Deep_dhimaan said:
I tried to install but it gives error 7 i think update.script should be rechecked.
Click to expand...
Click to collapse
Thank you very much, i've understood whats the problem( as a pm by ashkineeeeee).
New update coming soon. Stay tuned.
Hey bros...
so there were some problem with permissions, it seems that it is fixed now..
Flash the ROM and review here....
----------------------edit 1---------------------
dont flash the rom now!!!
Some files are missing in boot.img
how stupid i am!!
------------------------edit 2-----------------------
Flash it now!
Last build not installed,error 7.
mels01 said:
Last build not installed,error 7.
Click to expand...
Click to collapse
Logs,screenshots?
Try installing from internal storage... Or update your recovery to the latest one by android andi...
Thanks!
Hey, I would like to help out, can I have the link to the ROM?
theportal2 said:
Hey, I would like to help out, can I have the link to the ROM?
Click to expand...
Click to collapse
I agree this message is a bit long but it is worth reading.
- Thanks, but sorry. Even if I give you the links and even if spend your precious time you would only be able to fix the error 7.
- Actually I've already fixed that(or know what's the issue atleast). There are files that are missing from the directories that are listed in the updater script. They cannot be deleted as the original base ROM I compiled was from UA(unlegacy android) that are based on the newer sources.
- Some files that are required for MIUI are also missing.
- Boot.img is incomplete. Which will result in bootloop even if I upload the error 7 fixed ROM.
- I am giving my board exams that are one of the biggest exams in India. And I cannot afford to score less in these.
- All I need is a older base ROM ,CyanogenMod 11 made around may of 2016. And also it must support init.d because the port ROM requires that.
- I've taken permissions from the maker of the port ROM. He has allowed me to proceed.
- All I need is permission from Android-Andi, as only he has older CM ROMs.
- I cannot compile because older sources are not available or maybe I am not known to them
Hope you understand. Thank you.
P.S. - Android-Andi if you read this please reply. You are the only one who can help me(by providing me permissions to use your ROM as a base).
With best regards,
Kunal Gautam
Links
Kunal Gautam said:
I agree this message is a bit long but it is worth reading.
- Thanks, but sorry. Even if I give you the links and even if spend your precious time you would only be able to fix the error 7.
- Actually I've already fixed that(or know what's the issue atleast). There are files that are missing from the directories that are listed in the updater script. They cannot be deleted as the original base ROM I compiled was from UA(unlegacy android) that are based on the newer sources.
- Some files that are required for MIUI are also missing.
- Boot.img is incomplete. Which will result in bootloop even if I upload the error 7 fixed ROM.
- I am giving my board exams that are one of the biggest exams in India. And I cannot afford to score less in these.
- All I need is a older base ROM ,CyanogenMod 11 made around may of 2016. And also it must support init.d because the port ROM requires that.
- I've taken permissions from the maker of the port ROM. He has allowed me to proceed.
- All I need is permission from Android-Andi, as only he has older CM ROMs.
- I cannot compile because older sources are not available or maybe I am not known to them
Hope you understand. Thank you.
P.S. - Android-Andi if you read this please reply. You are the only one who can help me(by providing me permissions to use your ROM as a base).
With best regards,
Kunal Gautam
Click to expand...
Click to collapse
Have you seen this CM 11? https://forum.xda-developers.com/galaxy-tab-2/7-inch-development/rom-cm-11-0-galaxy-tab-2-t3737392
Just made last month by @Deltadroid
Links are removed because *the ROM is not complete yet*.
Thanks, but I need to confirm a few things before I could use a ROM(includes init.d support and a bunch of other things). Also, it is very important that deltadroid provide me permission to use his ROM.
Thank you!
Regards,
KG
-----_edit_--------
I just saw deltadroid's thread, the title clearly says that the ROM is for p3110. I want to make a unified one. I need a ROM made with unified device tree.
If I do port, it will only work on p3110 and maybe on every 7" device. I don't want do this.
Sorry, but yeah thanks!
Just wait till 3 april 2018. Most probably I will upload.
Edit 2
Or I must say it an update. 75 percent of the work is done. Somehow I managed to get a base ROM(only I know how). Only build.prop editing and Updater script editing work left(these are the most difficult BTW).
Update coming soon. Stay tuned.
I've updated the links. I've uploaded the new ROM. I've done with porting(i guess). I've used a lot of time.
Flash and review!
Kunal Gautam said:
I've updated the links. I've uploaded the new ROM. I've done with porting(i guess). I've used a lot of time.
Flash and review!
Click to expand...
Click to collapse
No wonder the ROM doesn't work.... Security patch is in a wrong format.
"ro.build.version.security_patch=2080-17-March"
It should be, "ro.build.version.security_patch=2018-03-01"
or,
"ro.build.version.security_patch=2018-03-05"
And this, hardly doubt this will work, but idk.
"ro.build.date.utc=999999999999"
Mistakes....................
EDIT**** Build id should be the app id: example lets say the id is 678, on build.prop, it would say 678.
you have, "ro.build.id=KUNAL"
secretwolf98 said:
No wonder the ROM doesn't work.... Security patch is in a wrong format.
"ro.build.version.security_patch=2080-17-March"
It should be, "ro.build.version.security_patch=2018-03-01"
or,
"ro.build.version.security_patch=2018-03-05"
And this, hardly doubt this will work, but idk.
"ro.build.date.utc=999999999999"
Mistakes....................
EDIT**** Build id should be the app id: example lets say the id is 678, on build.prop, it would say 678.
you have, "ro.build.id=KUNAL"
Click to expand...
Click to collapse
You, sir, definitely have a lot to offer. I am afraid that this is not the actual problem. By now, I surely understand the importance of logs. Would be very helpful if someone could arrange me them.
And about your post it seemed really rude, raw, insulting and manipulating to me. But however, helpful. It makes it really hard to continue developing for a 6 years old Tab, with hardware that has nothing to offer in 2018. At least, I am trying.
Since, this was an Alpha build(because I moved sources) these problems are sure to arise. I did the same(build.prop things) with my kinda successful ROM MIUI 5(see it in the 7" forums).
I guess you haven't tasted port ROMs yet. They are hard to build. Alike your compiling ones, you have source, type some commands, turn your computer on for about 5 hours, when done upload it.
I am sure you must have did trail and error (in chemistry and math) porting ROMs is just the same. I am sure, that as a developer, you must know what logs actually mean.
But whatever, thank you for you review(insult I guess).
Kunal Gautam said:
You, sir, definitely have a lot to offer. I am afraid that this is not the actual problem. By now, I surely understand the importance of logs. Would be very helpful if someone could arrange me them.
And about your post it seemed really rude, raw, insulting and manipulating to me. But however, helpful. It makes it really hard to continue developing for a 6 years old Tab, with hardware that has nothing to offer in 2018. At least, I am trying.
Since, this was an Alpha build(because I moved sources) these problems are sure to arise. I did the same(build.prop things) with my kinda successful ROM MIUI 5(see it in the 7" forums).
I guess you haven't tasted port ROMs yet. They are hard to build. Alike your compiling ones, you have source, type some commands, turn your computer on for about 5 hours, when done upload it.
I am sure you must have did trail and error (in chemistry and math) porting ROMs is just the same. I am sure, that as a developer, you must know what logs actually mean.
But whatever, thank you for you review(insult I guess).
Click to expand...
Click to collapse
FYI, I port ROMs. It was pointers what to fix, if you wanted to get this ROM better, than it is already.
Kunal Gautam said:
(...)
P.S. - Android-Andi if you read this please reply. You are the only one who can help me(by providing me permissions to use your ROM as a base).
With best regards,
Kunal Gautam
Click to expand...
Click to collapse
Sorry, I won't give permissions after different people used my ROMs as base in the past without permissions. Hope there is a learning affect....
Since i love OpenSource: Sources are available on every official GitHub (slim, Omni, Lineage, UA) and up to date (note: I wouldn't have to do this, I could keep all device trees private but I am updating them for everyone - always). You'll have to compile your own base ROM to use for such port ROMs (I am not a fan of).
Android-Andi said:
Sorry, I won't give permissions after different people used my ROMs as base in the past without permissions. Hope there is a learning affect....
Since i love OpenSource: Sources are available on every official GitHub (slim, Omni, Lineage, UA) and up to date (note: I wouldn't have to do this, I could keep all device trees private but I am updating them for everyone - always). You'll have to compile your own base ROM to use for such port ROMs (I am not a fan of).
Click to expand...
Click to collapse
Thank you. For at least replying. You works will always be appreciated. Now, I am gonna close this thread. Thanks again!
New build up at sx.ix5.org, use version 2018-10-30.
Changelog here: https://sx.ix5.org/changelog.html
Install guide: Flashing AOSP on Xperia XZ
XDA:DevDB Information
AOSP Pie based on Sony Open Devices Project, ROM for the Sony Xperia XZ
Contributors
local__hero, fastbooking, oshmoun
Source Code: https://git.ix5.org/felix/local-manifests-ix5/src/branch/ix5-customizations
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: .184 / .192
Based On: AOSP
Version Information
Status: Nightly
Created 2018-11-09
Last Updated 2019-05-17
Reporting bugs
Important: Read the bug list before posting. Anyone can add bugs to the list, just follow the rules.
If you have questions, ask them in this thread: Xperia XZ Pie ROMs Questions and Answers Thread
Don't make me ask you for logs every time!
I will repeat the rules again here:
Rules:
New bugs must include version where error popped up and which oem version you are using
Only reproducible errors
Should include adb logcat (linked in a pastebin service like https://del.dog)
Must include clear description what is wrong
If it is a visual/SystemUI bug, only report it here
If it is an internal bug(e.g. fingerprint crashes device), report it to the Sony bugtracker as well!
Always try to fix the bug yourself first! Then submit a pull request to Sony
Must search if error has already been reported (bug tracker, this document, dev buglist)
If you've reported the issue somewhere else already and just want to track it here as well, add a link
Before reporting a bug, always make sure to isolate it. That means, wipe everything, install only the ROM without GApps and Magisk and see if the problem still exists. Only then report the bug!
---
If you have questions, ask them in this thread: Xperia XZ Pie ROMs Questions and Answers Thread
---
In 9.11
1. Everything still works
2. Charging with plugged at screen off works
3. On gcam portrait mode and night photo gives purple glitched image
And phone seems to be faster.
Bug: 9.11 with oem v2- Clean install
- Hotspot not working
- Phone call issue - Mic and speaker not working, cannot hear anything or say anything << Listed in the bug
- Top speaker not working
Still testing.
An update
Yes, we know calling is kinda broken right now on both oem versions. Yes, we know you have problems with dualsim devices because you didn't flash the dualsim patcher. Yes, battery life isn't very good because we are testing out some increased CPU frequencies so video doesn't stutter. (you can go back to the 11-05 build which has the old CPU freqs and compare).
We're aware of a lot of these issues, and they are all tracked in the current buglist (see post #2).
Development happens mostly in the Sony open devices program, with a few heroic volunteers contributing. Right now, a lot of work is being done to get the current flagships(think XZ2, XZ3) to a semi-stable state, but work for our device is done as well.
You can check progress in the sonyxperiadev repos. E.g. recently, some changes to the telephony HAL integration have been made, see the common device repo.
Why is it taking so long to fix all this?
Sony buys many of their processors from Qualcomm. Lots of stuff in phones is proprietary and covered in patents, and you can only get the source code if you sign an NDA. So even if Sony wanted to, they could not release the source for a lot of things.
See all the files with the name "qti" in them? That's Qualcomm Technologies, Inc. See all the repos named something like "qcom-something-something"? That's Qualcomm.
When there's a problem, we have to report it to Sony, who report it to Qualcomm. This takes time already. And don't forget Qualcomm has suppliers as well, and so on and so on. The same is true for other parts, e.g. the Wi-Fi chips are from Broadcom.
Then, support for hardware stuff is on many levels. A lot of low-level drivers that are driving the hardware are on the /odm partition(the one that the oemv1/v2 blobs get flashed to). Then there is work to be done tweaking the actual hardware abstraction layer(HAL) interfaces that work with these driver blobs. Then there are kernel drivers that can go wrong and mess up. Then it can be a problem somewhere higher up in the Android frameworks. Lots of detective work.
If new blobs from Qualcomm come out, Sony itself needs to do some testing, and then releases a new oem version. It won't just magically work, we need to tweak the SODP vendor side as well. It could be as easy as changing a version to a newer one, but it could also be a lot harder. The sonyxperiadev crew knows what's needed to integrate these new blobs, but it still takes time and testing.
Qualcomm provide the a lot of the source code to work with their hardware and blobs from the higher-level Android side in their CodeAurora forum (CAF) repositories. The relevant changes then get merged into the sonyxperiadev repos and we can test if it works(or if something new is broken...).
For more info, read the Android documentation on hardware etc.
The chip in our phone, the MSM8996, is quite old already(even the SDM845 in the XZ2/3 is already quite old in processor standards). We can be luck that Qualcomm still provides support. But it's not a priority to them, they want to sell new
ones of course. That is also a reason updates can take longer.
Regarding full forced-reboot crashes:
Sadly, as of now, for some people the "/sys/fs/pstore" folder does not get populated after a crash. This is important to diagnose what happened.
You can apply this patch to force a kernel panic on every reboot, but I would recommend that you do
so only if you know what you are doing.
Regarding battery life:
Please install BetterBatteryStats
and find out what is draining the battery.
This could really help us out! But first, make sure you are not running any GApps, because the Google Mobile Services are a massive pile of battery drain.
If you absolutely have to use GApps, please run only the "pico" GApps version!
---
About the posts here:
Like 90% of posts here and in the old thread are full of people who just plain refuse to read, asking how to install or demanding someone help them out with something that has already been answered time and time again. This makes it extremely annoying for the us who have to scroll through pages of useless stuff to find the genuine bug reports. You do realize this site is literally named "xda-developers", right? If you're unclear on the concept, please read this: https://forum.xda-developers.com/showpost.php?p=16682226&postcount=2441
"This doesn't work!" - "This thing crashes!" - That gives us almost no clue what is happening. We need logs, or we can't do anything about it. I have only one phone, and I only use the stock ROM. There are a lot of nice testers who send others and me helpful bug reports, with detailed explanations in what circumstances it occured, with proper logs.
With that info, the Sony open devices team and us can actually look into issues.
So please, if something doesn't work AND we are not aware of it yet, post it to the bug list (not here!) and attach a link to a log that you uploaded, e.g. to a service like hastebin.com.
nhicko95 said:
how is battery life?
Click to expand...
Click to collapse
Test it out, please. And don't forget to report the diagnosed battery stats.
DarkPrinciple said:
I should be able to get to 12 lunch with my battery being more than 50%
Click to expand...
Click to collapse
I've tweaked for more performance right now, but you can use 11-05 to get old CPU freqs. Also, please help hunt down what is draining the battery, it's most likely too many held wakelocks, but it could be any number of things.
bihslk said:
So what is the latest and best working version of this rom?
Click to expand...
Click to collapse
It's literally in the first post.
bihslk said:
Rom is pretty OK but really annoying top speaker bug. Only lower one works.
Click to expand...
Click to collapse
That is already in the bug list. Please read the bug list before posting.
Update 2018-11-16
Some new developments are happening.
Oem binaries version 3 are out. This should give improved power management. The SODP team has also worked on getting audio handling during calls to work. A big thanks to oshmoun for his work on the audio manager. This change was introduced on the 11-15 build. The issue of no call audio when a bluetooth headset is connected is still present as of now.
Changed IRQ handling (PR by Angelo/"kholk"). This should give better battery life and maybe faster wakeup from deep sleep. But could also lead to instabilities and crashes. Send logs & pstore, see post #2. This change was introduced on the 11-15 build.
Testing kernel 4.9.137 i in progress (we are currently on .103). This means stability and security enhancements from upstream linux. Thanks to Nathan Chance who opened this pull request..
But some of those upstream changes might be incompatible with our Sony kernel, so we have to test that. Send logs & pstore, see post #2. This change was introduced in the 11-16 build. If the 11-15 and 11-16 builds are unstable, revert to an older one. But please be brave and run them for at least a day to get us logs of potential crashes.
---
optixperiaa said:
I am always confused about "flash latest stock ftf" part about roms as a newbie.. if we flash sony's ftf how can we flash rom ? isnt it overwrite ?
Click to expand...
Click to collapse
Your phone software is made up of many layers. The ROMs like omni or this AOSP-based one only modify your /system and /boot partitions.
But when you update your stock firmware via flashtool, you also update your phone modem firmware, your qnovo charging controller firmware, your lower-level bootloaders etc. That is why we instruct you to update to the latest stock firmware. You could theoretically skip flashing /system in flashtool(because it will get overwritten anyway, as you've already discovered) and directly flash a custom ROM afterwards.
When you're coming from omni, there is no need to flash stock firmware again in between, because your other partitions stay the same. Just a new /oem is needed.
viori said:
flash omni_kagura-2018-11-20_UNOFFICIAL_TESTBUILD-2
Click to expand...
Click to collapse
Again, please keep this thread about development for AOSP. The omni builds are not meant for you.
If you have trouble installing then simply don't use it.
DO NOT POST HERE FOR HELP OR YOU WILL BE REPORTED. Read everything before posting.
If you have questions, ask them in this thread: AOSP 9.0 Pie builds for F8331/F8332
The OP has requested that you do not post questions in this thread, please use the thread he states in the OP to do that.
If you have questions, ask them in this thread: AOSP 9.0 Pie builds for F8331/F8332
Click to expand...
Click to collapse
Thanks
Thread cleaned
General update
Newer builds will have selinux set to "enforcing". Most denials should have been fixed or are irrelevant. If you encounter any problems, selinux-related or anything else, please report them to the Sony bugtracker or - even better - submit a pull request to the selinux-policy repo.
Update 1: vendor blobs aren't binderized correctly atm, so no network. You can set selinux back to permissive to fix most issues atm.
The Wi-Fi hotspot has been fixed thanks to oshmoun. In newer builds, it should be using less battery.
Next thing we're going to tackle is deep sleep and battery drain. Big pain point and one of the last blockers, apart from the camera and bluetooth in-call audio.
You might have noticed that the omnirom device trees have been updated to 9.0. Nightly testing builds work fine, but they have the same issues as the AOSP-based ones.
Work is also under way to get a Pie-based TWRP recovery stable, with support for FDE encryption(this means that you will be able to back up your encrypted installations). Mounting /userdata works, but the builds are not ready for public release yet.
Update
New build up (2018-12-08)
Camera key works
Update to December security patch(12-05, r21)
Fingerprint should not crash device on enrollment any more
Allow setting lower minimum brightness
Double-tap-to-wake off by default(but can be enabled)
Plugging in charger with screen off should be fixed
Once again, I invite anyone who would like to help out or just learn a bit about building and tweaking to take a look at the sources posted here.
There will be a guide on how to build only the kernel and experiment with a custom boot.img shortly.
The build guide on sx.ix5.org for reproducing these AOSP builds should bring you up to speed, and if you need help building or just want to chat, the telegram group in post #1 is open to you.
local__hero said:
New build up (2018-12-08)
Camera key works
Update to December security patch(12-05, r21)
Fingerprint should not crash device on enrollment any more
Allow setting lower minimum brightness
Double-tap-to-wake off by default(but can be enabled)
Plugging in charger with screen off should be fixed
Once again, I invite anyone who would like to help out or just learn a bit about building and tweaking to take a look at the sources posted here.
There will be a guide on how to build only the kernel and experiment with a custom boot.img shortly.
The build guide on sx.ix5.org for reproducing these AOSP builds should bring you up to speed, and if you need help building or just want to chat, the telegram group in post #1 is open to you.
Click to expand...
Click to collapse
Great job.
I already built a custom Pie kernel about a week ago to gain better performance but the charging bug was driving me insane :crying:
I guess now's the time to go back to the mighty Pie and try building a nice and hopefully stable Marrow Kernel.
Cheers
Finally a new build is out!
I can't pass safety net on latest build.
Any ideas what should I use ?
Since modules for spoofing fingerprint simply don't work.
I tried universal safety net fix but with no avail.
V 12.15
Charging working fine. But i have problem with camera, photos are very dark.
Sometimes touch screen not working and i need to switch the screen and on again.
ov2rey said:
Sometimes touch screen not working and i need to switch the screen and on again.
Click to expand...
Click to collapse
Disable Dt2w
oem v4 is out
DahakePL said:
Disable Dt2w
Click to expand...
Click to collapse
Thank you It's work!
Layns said:
oem v4 is out
Click to expand...
Click to collapse
i am testing v4 on latest build aosp_f8331_2018-12-21-NIGHTLY-permissive.
Screen unable to display after update to oem v4
https://developer.sony.com/file/download/software-binaries-for-aosp-pie-android-9-0-kernel-4-9-tone/
ov2rey said:
Thank you It's work!
i am testing v4 on latest build aosp_f8331_2018-12-21-NIGHTLY-permissive.
Screen unable to display after update to oem v4
https://developer.sony.com/file/download/software-binaries-for-aosp-pie-android-9-0-kernel-4-9-tone/
Click to expand...
Click to collapse
I tried it works fine but the camera sucks and the sound is bad, the screen opening with double tap is running slow, the charge is a little quick