Related
Hey Guys,
So I finally decided to learn what all this compiling and building from source is about.. So far I really learned to appreciate the developers on this site.. I started out trying to build AOSP and cherry pick commits, but after the build kept failing now my goal is just straight up AOSP for now..
I followed all different guides to get to the point of building it - it boots up without issue however I have no cell signal - baseband version is unknown.
I am at a lose to what to do. I do have the Google Nexus Binaries, and in the device/lge/mako/full_mako.mk I changed PRODUCT_RESTRICT_VENDOR_FILES := true to false.
I did make clobber to clean out any failed build, and rebuilt. I also can't get a kernel to build but thats a different beast so for now I am just using the stock boot.img.
Any help would be greatly appreciated..
**Edit** Only thing that may be an issue I think I used the preview binaries for nexus 4 - which I guess might be for Android L? Going to try to download the ones for 4.4 and see if that changes anything.
**Edit 2** After changing from the preview binaries to the regular 4.4.4 ones from google, I did make clobber and rebuilt android.. And I have full cell signal
hi guys, I see there are still no threads for FirefoxOS that has been just released by FXP for our device too (z3c) so I'm creating one
this thread just to discuss about it!
INFO: http://fxpblog.co/2015/09/26/firefox-os-releases-by-fxp.html
DOWNLOADS: http://fxpblog.co/firefox/nightly/
INSTALLATION:
- You must have a UNLOCKED BL
- Extract all system images from the ARIES zip you downloaded
- Connect phone to PC in fastboot mode and then:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot reboot
downloading the zip for aries right now! will see how it goes
in the meantime, I have already some questions I would like to reply myself after testing the new OS or if somebody already knows the answers, please let me know!
1. rootable? DON'T THINK SO
2. recovery can be installed or to go back to stock will have to flash FTF via flashtool? SEEMS NO RECOVERY AT ALL?!
3. camera present/working? if so, without fish eye bug? CAMERA NOT WORKING AT ALL
4. gapps are needed? in firefox OS there is no Play Store right? NO GAPS, THERE IS MOZILLA MARKETPLACE WITH FEW STUFF STILL OF COURSE
Please contribute guys in answering all the above questions!
THANKS
All credits to Mozilla and FXP ( @freexperia ) teams of course!
few screenshots:
https://www.dropbox.com/s/2ut81qaqjgu3fqo/2015-10-01-11-14-23.png?dl=0
https://www.dropbox.com/s/vvrx7153ql6xjzf/2015-10-01-11-14-33.png?dl=0
few impressions so far:
the bad:
- no camera
- no dt2w
- no extsd support (where I have all my stuff!)
the good:
- seems very nice and promising
- app ops
- nice animations
will keep updating!
Really interested to try this once it's fully functional. Thanks for the heads up!
moly82 said:
- I'm pretty sure you must have a UNLOCKED BL
Click to expand...
Click to collapse
Unlocked bootloader for sure, since you must flash boot.img
Our device is ARIES, if someone doesn't know yet
Testing today...
me too just unlocked the BL!
EDIT: just booted inside FirefoxOS for my first time
things I noticed so far:
see OP
First impressions:
-only English language.. mmmhhh.. and the keyboard is only in english
-you can import your contacts also from gmail... ok.. that's good
-there's a tutorial at the beginning that explains how it works :victory:
-camera just doesn't work (the camera is in use by another app) !!??!!
-some popular apps ready to install... ok, fine!
-to take screenshots you have to press home+power... but I can't get it :crying:
-settings menu is like a hybrid between android and ios
-all the gestures work properly and are different from android, but they're friendly :good:
-the phone is getting very hot now
-arrrgghhh.... force close... the phone rebooted automatically :crying:
yes for sure not ready for daily driver, but seems very nice
for screenshots I just used android normal gesture (power + vol down)
no recovery right? will have to flash FTF to go back to stock?
phone is not hot at all here so far
Problem with camera is in HAL. Logcat... logcat.
In AOSP builds there is no camera, this is the cause.
Seems problem has been solved. Waiting for new build from fxp team then
https://t.co/XGZ6c75N0X
it seems very very basic and not ready for daily use but well better than nothing..! let's see
xperia z3c fxos
right now the bug for the camera on the lollipop build is being worked on, as far as i can find in our bug reports the kk build camera should be working or it would be under QA-blocker. Also for some of the problems you are having such as only english when building make sure to put PRODUCTION=1 it will make it so it flashes all of the languages, that just has to do with not setting the right build variables.
Fxos-QA contributor rep
Sorry i would give you links but i am a new user on this site so i cant...
jamie_fxos said:
right now the bug for the camera on the lollipop build is being worked on, as far as i can find in our bug reports the kk build camera should be working or it would be under QA-blocker. Also for some of the problems you are having such as only english when building make sure to put PRODUCTION=1 it will make it so it flashes all of the languages, that just has to do with not setting the right build variables.
Fxos-QA contributor rep
Sorry i would give you links but i am a new user on this site so i cant...
Click to expand...
Click to collapse
not sure to understand correctly, you mean there is a firefoxos version based on kk for z3c with working camera? where?
because it seems I can find only the lp build in fxp site... thanks! :silly:
moly82 said:
not sure to understand correctly, you mean there is a firefoxos version based on kk for z3c with working camera? where?
because it seems I can find only the lp build in fxp site... thanks! :silly:
Click to expand...
Click to collapse
i just double checked with of the devs, The aires device, you can build the kk version which does have a working camera, you just have to compile it yourself. The lp build currently available on task cluster does not have the working camera, in all honesty the lp kernal version is not fully complete yet, right now the camera is one of those parts that are not fully complete. if you want to take a look the bug number is 1163557 you have to go to bugzilla.mozilla.org it might help explain the situation. right now lp is experimental.
firefox os QA
mozilla rep
Jamie Charlton
thanks mate, will do! and thanks also for the info, it is nice someone from firefoxos project directly is looking around here and share info with us!
unfortunately i'm not skilled enough for building myself, so can just wait for fxp team to build them for us.
afaik devs are working on updated/fixed camera blobs for lp as we speak, so we could have a decent camera available for aosp soon, in that case hope it will land in firefox os too
really looking forward for a usable build of firefoxos for our device, it seems a very nice project... i like firefox, i like opensource, i don't like google at all recently... so hope to find in fxos soon a great alternative! :good: :fingers-crossed:
moly82 said:
thanks mate, will do! and thanks also for the info, it is nice someone from firefoxos project directly is looking around here and share info with us!
unfortunately i'm not skilled enough for building myself, so can just wait for fxp team to build them for us.
afaik devs are working on updated/fixed camera blobs for lp as we speak, so we could have a decent camera available for aosp soon, in that case hope it will land in firefox os too
ht
really looking forward for a usable build of firefoxos for our device, it seems a very nice project... i like firefox, i like opensource, i don't like google at all recently... so hope to find in fxos soon a great alternative! :good: :fingers-crossed:
Click to expand...
Click to collapse
come end of next week i might be able to get you a kk build, i cant say for 100% due to moz is giving me mine next week. If it comes with a KK kernal on it i can see if I can make you one, i dont think it is under nda for the blobs for kk, im not sure 100% though. i just know for the flame device im not allowed to give out builds that have not gone through approval from t2mobile as distributable.
moly82 said:
1. rootable? DON'T THINK SO
Click to expand...
Click to collapse
Yes. rootable.
jamie_fxos said:
come end of next week i might be able to get you a kk build, i cant say for 100% due to moz is giving me mine next week. If it comes with a KK kernal on it i can see if I can make you one, i dont think it is under nda for the blobs for kk, im not sure 100% though. i just know for the flame device im not allowed to give out builds that have not gone through approval from t2mobile as distributable.
Click to expand...
Click to collapse
thanks mate you rock!
will see so, btw no need to hurry for me, as I am taking my z3c to assitance today or tomorrow (broken magnetic port :crying: ) and dunno when I'll see it again... :silly:
moly82 said:
thanks mate you rock!
will see so, btw no need to hurry for me, as I am taking my z3c to assitance today or tomorrow (broken magnetic port :crying: ) and dunno when I'll see it again... :silly:
Click to expand...
Click to collapse
By the time you get it back i hope that i will already have a working build for you.
Also people, if the base image you are using is gotten from mozilla its a 99% chance its rooted, they are left unlocked for testing and development reasons, the only time they are locked usually is when you are getting them from the phone manufacturer also know as a production build, which we do not make.
Mozilla rep
Firefox OS QA
Jamie Charlton
Okay i have looked into it, the only way i can make you a base image is if it is blib free so you would have to get the blobs from Sony. The blobs are currently under nda so there is no way i can share them without getting in trouble. The only way it seems you could get the kk build with a working camera is if you flash back to android and then get the blobs from the device and then from there you would have to add them to the blob free base image.
The project got already discontinued by Mozilla because the not given chance to get close to Android, iOS or WIP
Maybe with a hardboot kernel it could be saved as a stable, second OS with Multirom...
When Moto X Play is getting official CyanogenMod 13? Any updates?
Nitish247 said:
When Moto X Play is getting official CyanogenMod 13? Any updates?
Click to expand...
Click to collapse
Probably never. Does it matter? No, not at all. What is better about an official version compared to the unofficial? Nothing at all.
But why? Any specific reason? All Moto phones till date have official CM.
It's my understanding cm13 will turn official some day.
Nitish247 said:
But why? Any specific reason? All Moto phones till date have official CM.
Click to expand...
Click to collapse
If you are following the cm13 thread then you would know that squid has told that he would push for the cm13 build to become official but there is no estimated time.
Sent from my XT1562 using Tapatalk
It's a matter of fixing bugs. My intention has always been to make CM13 official once it is ready. There are three bugs blocking this:
Use of WiFi assisted location causes soft reboots if you don't add additional bounds checking. I am not sure if this bounds checking should really be there or if it is a symptom of some other problem.
A mysterious issue with the new camera drivers is causing memory corruption in the audio HAL. I'm not sure of the cause (other than the crash only happening when liboemcamera is updated to the Marshmallow version). I have a crude hack to work around this, but it is not suitable for merging into official CM. This will be tricky to debug and fix properly.
The RIL needs fixing on XT1562. I don't have an XT1562, so that makes it more difficult for me to troubleshoot, but @scritch007 will be looking into this in the coming days.
squid2 said:
It's a matter of fixing bugs. My intention has always been to make CM13 official once it is ready. There are three bugs blocking this:
Use of WiFi assisted location causes soft reboots if you don't add additional bounds checking. I am not sure if this bounds checking should really be there or if it is a symptom of some other problem.
A mysterious issue with the new camera drivers is causing memory corruption in the audio HAL. I'm not sure of the cause (other than the crash only happening when liboemcamera is updated to the Marshmallow version). I have a crude hack to work around this, but it is not suitable for merging into official CM. This will be tricky to debug and fix properly.
The RIL needs fixing on XT1562. I don't have an XT1562, so that makes it more difficult for me to troubleshoot, but @scritch007 will be looking into this in the coming days.
Click to expand...
Click to collapse
Great news. Laud your hard work have a great year ahead squid2
Sent from my XT1563 using Tapatalk
squid2 said:
It's a matter of fixing bugs. My intention has always been to make CM13 official once it is ready. There are three bugs blocking this:
Use of WiFi assisted location causes soft reboots if you don't add additional bounds checking. I am not sure if this bounds checking should really be there or if it is a symptom of some other problem.
A mysterious issue with the new camera drivers is causing memory corruption in the audio HAL. I'm not sure of the cause (other than the crash only happening when liboemcamera is updated to the Marshmallow version). I have a crude hack to work around this, but it is not suitable for merging into official CM. This will be tricky to debug and fix properly.
The RIL needs fixing on XT1562. I don't have an XT1562, so that makes it more difficult for me to troubleshoot, but @scritch007 will be looking into this in the coming days.
Click to expand...
Click to collapse
Thanks! Thats' awesome! :good:
We expect lux on official CyanogenMod list soon
squid2 said:
It's a matter of fixing bugs. My intention has always been to make CM13 official once it is ready. There are three bugs blocking this:
Use of WiFi assisted location causes soft reboots if you don't add additional bounds checking. I am not sure if this bounds checking should really be there or if it is a symptom of some other problem.
A mysterious issue with the new camera drivers is causing memory corruption in the audio HAL. I'm not sure of the cause (other than the crash only happening when liboemcamera is updated to the Marshmallow version). I have a crude hack to work around this, but it is not suitable for merging into official CM. This will be tricky to debug and fix properly.
The RIL needs fixing on XT1562. I don't have an XT1562, so that makes it more difficult for me to troubleshoot, but @scritch007 will be looking into this in the coming days.
Click to expand...
Click to collapse
I tried the version from the 25th of December, and I don't have any issue with it (I own a dual sim xt1562) and only have one sim inserted, but just after the boot I was prompted for the pin code. So I won't be of any help...
I'm running the 24.11.18.lux_retasia_ds.retasiaall.en.03 retfr version as my main version, so all my partitions were updated to 6.0
MOD EDIT by @gregbradley. I did not see the need for the expletive in the title, so i took it out for you.
So here's a little rant.
Read it if you'd like to, don't read if you don't like to.
Let's start with a little introduction. I've bought my Z3 about a year ago. I wanted to go with the z3+, but the Snapdragon 810 seemed to cause some issues. I still wanted the Sony batterylife after coming from a Galaxy S4 (which doesn't have the best battery life). I found online that Sony shares AOSP source code, so building a custom rom shouldn't be too hard.
Recently I have thought about unlocking my bootloader, but reading further into it, I found there to be NO upsides to unlocking your bootloader.
- There's a possibility of losing your DRM Keys when unlocking bootloader.
- You can not lock your bootloader again, so you're forever excluded from any OTA's.. Sony supports AOSP source code, you know.. to be developer friendly. But locking your bootloader again is not possible. This makes unlocking it very unappealing.. and very developer unfriendly.
- You cannot flash a recovery through fastboot, because Sony doesn't use conventional recoveries. Very developer friendly!
- Fine, Sony decides to release Android MM concept. Great, I was excited for this! But, the actual MM final firmware is nothing like the concept firmware and still a lot like the actual Sony themed firmware. (In my opinion this is disappointing, but that might be just me). When asked about why there are differences between the concept and the final firmware, the concept team replies that it has nothing to do with the final firmware. Then what's the point of a concept firmware??
Maybe I'm just nitpicking, but this seems very hypocritical from Sony..
C'mon Sony, your mobile department isn't doing too well, and this sure as hell doesn't make it better.
Now I know there are maybe only several thousand people actually wanting to run AOSP on their Sony, but I sure as hell am not buying another Sony phone until this policy changes.
Thanks.
Joost
Im still trying to figure out which part you unhappy about lol ?????
I have the Z3 rooted with Android 6.0.1 Slim1.6 Rom LB
And its the best ever with longest battery life ive experienced no issues fast and smooth
I dont want any other phone right now what more could you want?
MasterCMTS said:
Im still trying to figure out which part you unhappy about lol ?????
I have the Z3 rooted with Android 6.0.1 Slim1.6 Rom LB
And its the best ever with longest battery life ive experienced no issues fast and smooth
I dont want any other phone right now what more could you want?
Click to expand...
Click to collapse
My issue?
On one hand Sony releases AOSP code, while on the other hand they make it a real damn pain in the ass to even run an AOSP rom. There have been several developers out there to try and build an AOSP rom. None of them managed to make a fully working one, because Sony made it so damn hard. I find this hypocritical and unjust.
What I want is for Sony to make it actually possible to run an AOSP rom, and stop pretenting like it's possible.
Me Gusta said:
So here's a little rant.
Read it if you'd like to, don't read if you don't like to.
Let's start with a little introduction. I've bought my Z3 about a year ago. I wanted to go with the z3+, but the Snapdragon 810 seemed to cause some issues. I still wanted the Sony batterylife after coming from a Galaxy S4 (which doesn't have the best battery life). I found online that Sony shares AOSP source code, so building a custom rom shouldn't be too hard.
Recently I have thought about unlocking my bootloader, but reading further into it, I found there to be NO upsides to unlocking your bootloader.
- There's a possibility of losing your DRM Keys when unlocking bootloader.
- You can not lock your bootloader again, so you're forever excluded from any OTA's.. Sony supports AOSP source code, you know.. to be developer friendly. But locking your bootloader again is not possible. This makes unlocking it very unappealing.. and very developer unfriendly.
- You cannot flash a recovery through fastboot, because Sony doesn't use conventional recoveries. Very developer friendly!
- Fine, Sony decides to release Android MM concept. Great, I was excited for this! But, the actual MM final firmware is nothing like the concept firmware and still a lot like the actual Sony themed firmware. (In my opinion this is disappointing, but that might be just me). When asked about why there are differences between the concept and the final firmware, the concept team replies that it has nothing to do with the final firmware. Then what's the point of a concept firmware??
Maybe I'm just nitpicking, but this seems very hypocritical from Sony..
C'mon Sony, your mobile department isn't doing too well, and this sure as hell doesn't make it better.
Now I know there are maybe only several thousand people actually wanting to run AOSP on their Sony, but I sure as hell am not buying another Sony phone until this policy changes.
Thanks.
Joost
Click to expand...
Click to collapse
You can use TA Backup to restore your DRM keys as long as you back them up before unlocking the bootloader ('m just about to do it)
You can install a custom recovery via fastboot (I used TWRP to replace cyanogen recovery).
Not really sure your points to be honest.
savo83 said:
You can use TA Backup to restore your DRM keys as long as you back them up before unlocking the bootloader ('m just about to do it)
You can install a custom recovery via fastboot (I used TWRP to replace cyanogen recovery).
Not really sure your points to be honest.
Click to expand...
Click to collapse
Sure, you can restore DRM.. but is it really convenient? My point is that Sony basically promotes AOSP roms by releasing source code, but on the other hand they make it impossible to enjoy a fully working AOSP rom because of DRM, camera's never working, etc..
Oh, and if you could explain to me how you flashed TWRP, and which file exactly, that'd be great . I've literally already spent 6 hours today trying to figure **** out after unlocking my bootloader..
Thanks in advance!
I totally agree with you. Building an AOSP ROM for Z3 seems to be difficult (Tried cm too but extracting proprietary blobs did not work). The way how recovery works here is pretty stupid, seeing that we dont have a recovery on N for example, so I need to be on it without root (i dont blame developers here, but again, Sony's implementation). Also I haven't been able to work around the radio or camera thing in AOSP, even though I have only been able to build the ROM like once some weeks ago
---------- Post added at 06:00 AM ---------- Previous post was at 05:55 AM ----------
Me Gusta said:
Sure, you can restore DRM.. but is it really convenient? My point is that Sony basically promotes AOSP roms by releasing source code, but on the other hand they make it impossible to enjoy a fully working AOSP rom because of DRM, camera's never working, etc..
Oh, and if you could explain to me how you flashed TWRP, and which file exactly, that'd be great . I've literally already spent 6 hours today trying to figure **** out after unlocking my bootloader..
Thanks in advance!
Click to expand...
Click to collapse
Also the recovery thing. Just download the .img from Nailyk's thread and put it in ADB folder. Then go to fastboot and type fastboot flash FOTAKernel . Then boot to recovery by pressing power and volume down button, releasing power when phone vibrates and volume when sony logo appears.
Me Gusta said:
- There's a possibility of losing your DRM Keys when unlocking bootloader.
Click to expand...
Click to collapse
That is true and disappointing. However, there is a way to backup the keys and restore whenever the need arises.
Me Gusta said:
- You can not lock your bootloader again, so you're forever excluded from any OTA's.. Sony supports AOSP source code, you know.. to be developer friendly. But locking your bootloader again is not possible. This makes unlocking it very unappealing.. and very developer unfriendly.
Click to expand...
Click to collapse
fastboot oem lock or restoring the DRM keys should relock the bootloader.
Me Gusta said:
- You cannot flash a recovery through fastboot, because Sony doesn't use conventional recoveries. Very developer friendly!
Click to expand...
Click to collapse
Sure it works, you just need to run 23.4.A.1.264 firmware or newer. I use fastboot flash recovery something.img all the time.
Me Gusta said:
- Fine, Sony decides to release Android MM concept. Great, I was excited for this! But, the actual MM final firmware is nothing like the concept firmware and still a lot like the actual Sony themed firmware. (In my opinion this is disappointing, but that might be just me). When asked about why there are differences between the concept and the final firmware, the concept team replies that it has nothing to do with the final firmware. Then what's the point of a concept firmware??
Click to expand...
Click to collapse
I think the Concept software is for those who don't need Sony enhancements (X-Reality, ClearAudio+, etc.) and want something that is close to stock.
So:
-You can backup and restore DRM functions even with an unlocked BL.
-You can relock BL again (haven't tried it myself but I think it's possible, if you check out DRM restoration guides I think they also show how to relock the BL)
-The new Sony BL allows fastbooting recoveries, the older ones support FOTA recoveries (I've used both with no problems)
-The MM concept project is still live, you can install it and continue using it, it gets updated regularly and is very close to AOSP.
-True Sony is kind of shady with their sources but you can build AOSP, there are AOSP builds for the Z3 here: http://fxpblog.co/ they get released whenever Sony releases new sources but you can also make builds yourself. The only true issue with sources comes out on certain AOSP functions and that we don't have (yet) fully working CM13 builds. As for the concept firmware it's exactly what you said, Sony is giving it out to people who are interested in having a close AOSP experience with support from the vendor while giving feedback to further improve it. Sony is making moves and is becoming more developer friendly by the month, other than new and constantly updated sources, proof of this is the Xperia Z3 is the only non-Nexus device that gets to run the Android N preview officially given from the vendor.
The Z3 is a great device, I personally haven't regreted the purchase, the only thing that bugs me is that neither I nor anyone else has managed to build a fully functional CM13 build (kudos to infected btw).
---------- Post added at 09:02 AM ---------- Previous post was at 08:58 AM ----------
Evokkimus said:
I totally agree with you. Building an AOSP ROM for Z3 seems to be difficult (Tried cm too but extracting proprietary blobs did not work). The way how recovery works here is pretty stupid, seeing that we dont have a recovery on N for example, so I need to be on it without root (i dont blame developers here, but again, Sony's implementation). Also I haven't been able to work around the radio or camera thing in AOSP, even though I have only been able to build the ROM like once some weeks ago
---------- Post added at 06:00 AM ---------- Previous post was at 05:55 AM ----------
Also the recovery thing. Just download the .img from Nailyk's thread and put it in ADB folder. Then go to fastboot and type fastboot flash FOTAKernel . Then boot to recovery by pressing power and volume down button, releasing power when phone vibrates and volume when sony logo appears.
Click to expand...
Click to collapse
As I said fxp has some builds, I haven't tested them but I think they work (http://fxpblog.co/)
I was eager to try out FXP's aosp ROM, due to 3.10 kernel and such, but I got an error about updater-script in META-INF, didn't read further. I have my suspicions that it was a bad download, but their current site is so slow to download from (about 2 hours to download, and only a +20kb/s faster if you register), and i'm not going to pay for that site. If it helps any, i just wiped data, system and caches and tried flashing the ROM.
---------- Post added at 12:14 PM ---------- Previous post was at 11:56 AM ----------
CedArctic said:
So:
-You can backup and restore DRM functions even with an unlocked BL.
-You can relock BL again (haven't tried it myself but I think it's possible, if you check out DRM restoration guides I think they also show how to relock the BL)
-The new Sony BL allows fastbooting recoveries, the older ones support FOTA recoveries (I've used both with no problems)
-The MM concept project is still live, you can install it and continue using it, it gets updated regularly and is very close to AOSP.
-True Sony is kind of shady with their sources but you can build AOSP, there are AOSP builds for the Z3 here: http://fxpblog.co/ they get released whenever Sony releases new sources but you can also make builds yourself. The only true issue with sources comes out on certain AOSP functions and that we don't have (yet) fully working CM13 builds. As for the concept firmware it's exactly what you said, Sony is giving it out to people who are interested in having a close AOSP experience with support from the vendor while giving feedback to further improve it. Sony is making moves and is becoming more developer friendly by the month, other than new and constantly updated sources, proof of this is the Xperia Z3 is the only non-Nexus device that gets to run the Android N preview officially given from the vendor.
The Z3 is a great device, I personally haven't regreted the purchase, the only thing that bugs me is that neither I nor anyone else has managed to build a fully functional CM13 build (kudos to infected btw).
---------- Post added at 09:02 AM ---------- Previous post was at 08:58 AM ----------
As I said fxp has some builds, I haven't tested them but I think they work (http://fxpblog.co/)
Click to expand...
Click to collapse
I also tried building CM but stuck on proprietary blobs part. Couldn't pull them from the device for some reason, even though i was on CM rom at the time. (I did it because breakfast ended up in some vendor errors and Z3 didnt show up on the list either)
Evokkimus said:
I also tried building CM but stuck on proprietary blobs part. Couldn't pull them from the device for some reason, even though i was on CM rom at the time. (I did it because breakfast ended up in some vendor errors and Z3 didnt show up on the list either)
Click to expand...
Click to collapse
Weird, I build CM12.1/CM13.0/twrp 3 with theMuppet repo without a glitch. Can you paste your compilation error in a pastebin or something like this? Maybe I can help you a little (I'm a compilation newbie)
nailyk said:
Weird, I build CM12.1/CM13.0/twrp 3 with theMuppet repo without a glitch. Can you paste your compilation error in a pastebin or something like this? Maybe I can help you a little (I'm a compilation newbie)
Click to expand...
Click to collapse
Basically the error I get is with extract-files.sh. When I run "./extract-files.sh" while phone is plugged in, I get permission denied. The other option for me is to run it with sudo, but then I get "line XX adb: command not found" (many lines of this error). Someone suggested chmod or opening a terminal window inside the folder where extract-files.sh is located. There shouldn't be any errors with my AndroidSDK path, even though some suggest the error is with this.
Also the reason I'm trying to pull these blobs, is because the CM tutorial told me so
{
"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"
}
https://wiki.cyanogenmod.org/w/Build_for_z3
------------------------------------------------------------
Also the reason I'm building CM is because I still don't know how to get radio working, even though a person has told how to get it working, I don't know how to exactly do it. But firstly I would like this CM thing to work. Thanks for your help.
Evokkimus said:
Also the reason I'm building CM is because I still don't know how to get radio working, even though a person has told how to get it working, I don't know how to exactly do it. But firstly I would like this CM thing to work. Thanks for your help.
Click to expand...
Click to collapse
No worries.
So it may be a little more complicated.... If you just need a functional self build CM, try to include themuppet repo. If your device variant is not currently officially supported it can be more complicated.
I suggest you to open (or find) a dedicated thread and quote me, or join #[email protected]
Otherwise I'm following this thread because I found some point really interesting. I'm currently in trouble with Sony, that's why I subscribe.
Sorry for off-topic answers.
sorry did not see the date
arminbih said:
sorry did not see the date
Click to expand...
Click to collapse
Customer service troubles. They didn't respect law about unlocked bootloader into my country and refused to fix my device.
I know this thread is basically dead but I figured I'd poke it with a stick a few times and give my two cents.
First of all, the reason I chose Sony. I peviously owned Galaxy S4 and at some point (Android 4.2.2?) they implemented a security software called KNOX. It lets you create encrypted partitions for business stuff. Soon after, users started reporting that any unofficial changes result in a "0x01" flag showing in the download mode. Turns out, the device has a physical e-fuse which is burned and can not be reverted (except with a motherboard change). It was mainly for the customer services to be able to tell if the phone had been tampered with. But here's the catch - it was also triggered when installing official Samsung firmware using ODIN (basically FlashTool or Emma for Samsung). And downgrading firmware to pre-KNOX resulted in a special lock - the inability to upgrade again.
XDA members, such as Chainfire and others, have not managed to crack the software after several years, despite the bounty of thousands of dollars. I didn't think much of it, and rooted. Months after that my phone stopped recognizing the SIM card. And since I had "0x01" I had no warranty. So it went to customer service many times, I paid for the SIM reader change, and still nothing. Even custom ROMs didn't help.
So, I had a phone with no SIM support, and no faith in Samsung. I found out that Sony "encourages Android development" - bootloader unlocking and so on. Soon after I bought a Z3, and being a power user, I wanted to root. And then I found out about the DRM. The more I researched, the more livid I got. Finally I managed to dig up a method of rooting without bootloader unlock. After every small update Sony issued, I had to go through hours of researching and developing a new cusom update for my device. After some time I just decided to go with a (back then unreliable) DRM function restoring flashable zip.When I heard there will be no Nougat for Z3, I was quite mad. I looked into some AOSP's. NONE of them were working correctly. So I settled with a Z3 on unlocked BL with some DRMs working. The device has hiccups but is usable. I am disappointed in Sony and I am disappointed in Samsung. Never buying their phones again.
But now that @nailyk is developing LineageOS for Shinano devices, we have new hope! :victory:
The Android Robot said:
I know this thread is basically dead but I figured I'd poke it with a stick a few times and give my two cents.
First of all, the reason I chose Sony. I peviously owned Galaxy S4 and at some point (Android 4.2.2?) they implemented a security software called KNOX. It lets you create encrypted partitions for business stuff. Soon after, users started reporting that any unofficial changes result in a "0x01" flag showing in the download mode. Turns out, the device has a physical e-fuse which is burned and can not be reverted (except with a motherboard change). It was mainly for the customer services to be able to tell if the phone had been tampered with. But here's the catch - it was also triggered when installing official Samsung firmware using ODIN (basically FlashTool or Emma for Samsung). And downgrading firmware to pre-KNOX resulted in a special lock - the inability to upgrade again.
XDA members, such as Chainfire and others, have not managed to crack the software after several years, despite the bounty of thousands of dollars. I didn't think much of it, and rooted. Months after that my phone stopped recognizing the SIM card. And since I had "0x01" I had no warranty. So it went to customer service many times, I paid for the SIM reader change, and still nothing. Even custom ROMs didn't help.
So, I had a phone with no SIM support, and no faith in Samsung. I found out that Sony "encourages Android development" - bootloader unlocking and so on. Soon after I bought a Z3, and being a power user, I wanted to root. And then I found out about the DRM. The more I researched, the more livid I got. Finally I managed to dig up a method of rooting without bootloader unlock. After every small update Sony issued, I had to go through hours of researching and developing a new cusom update for my device. After some time I just decided to go with a (back then unreliable) DRM function restoring flashable zip.When I heard there will be no Nougat for Z3, I was quite mad. I looked into some AOSP's. NONE of them were working correctly. So I settled with a Z3 on unlocked BL with some DRMs working. The device has hiccups but is usable. I am disappointed in Sony and I am disappointed in Samsung. Never buying their phones again.
But now that @nailyk is developing LineageOS for Shinano devices, we have new hope! :victory:
Click to expand...
Click to collapse
Lots of OEM are doing this stuffs to protect their intellectuals rights with DRMs. AFAIK oneplus allow bootloaders unlock.
Just for fun, the TA partition of sony contain so much things... It is crazy! BTW I think we have fuse too
idk where you live but in Europe there is a law which basically said: hardware and software are separated and OEM need to fix hardware, except if they can prove this is user fault.
1999/44/CE in date of 1999-05-31.
Hi,
My M30s started randomly restarting after a software update. I could not find solutions here when I searched but it appears a lot of people on the internet having been facing similar issues for quite a few months now. The Samsung community forums are full of multiple messages and Samsung is pushing people to get to their phones to the service centers and are getting the motherboards replaced for free if the warranty is valid (or at a cost of INR 9,000 otherwise).
In any case, I found another poster on the Samsung forums who seems much more tech savvy than I am. And he seems to have solved the problem on his phone by changing 2 lines of code in the Linux kernel wand rebuilding the OS afterward.
Like I said, I am not tech savvy enough for this, but I thought I would post the link here because I could not find this particular fix here.
Re: READ THIS IF YOUR SAMSUNG GALAXY M30S KEEPS RANDOMLY FREEZING AND RESTARTING AUTOMATICALLY
To add a bit of my research into this problem: My phone (SM-M307FN) is rebooting many times every single day due to a Linux kernel issue which has been already fixed a long time ago in the mainline version. I am still running Android 10, because that's the latest version (M307FNXXU2BTC6) of the...
r2.community.samsung.com
(Here is the text from the post in case you are not able to open it)
-----------------------------------------------------------------------
To add a bit of my research into this problem:
My phone (SM-M307FN) is rebooting many times every single day due to a Linux kernel issue which has been already fixed a long time ago in the mainline version. I am still running Android 10, because that's the latest version (M307FNXXU2BTC6) of the OS Samsung has released on their open-source portal. I can use this source code to fix and rebuild the OS to prevent the issue from happening.
The issue and the fix is well known among the Samsung M30s community. It's two lines of code that need to be changed to prevent at least one of the common reasons for frequent reboots.
It takes a lot of work for a private user to fix those two lines of code, because Samsung releases source code that's non-trivial to compile and actually run on your device afterwards.
Samsung's Android 11 still ships with the same old kernel version (4.14.62) as their Android 9 (4.14.62), released back in 2018. There might have been some fixes between 4.14.62-19694174 and 4.14.62-20748039 introduced by Samsung in the meantime.
Regardless, this fix is not part of the source code for M307FNXXU2BTC6 (linked above) that's been released by Samsung in June 2020. Therefore, it doesn't seem like Samsung is actually applying all fixes to their kernels.
The kernel itself should have been upgraded to a higher version - at least to 4.19 - to fix bugs that's been plaguing users of Exynos 9611 chips running on Linux v4.14 for a long time.
Samsung: Please apply this fix to your Android kernels and push the update to your customers. Thank you!
References about the "fix NULL pointer deref in smaps_pte_range()":
Mainline Linux kernel fix:
[4.19,248/361] mm: /proc/pid/smaps_rollup: fix NULL pointer deref in smaps_pte_range()
https://lore.kernel.org/patchwork/patch/1010971/
Google Android Linux kernel backported this change in 2019 :
https://android.googlesource.com/kernel/common/+/043c92bd0517e0018cb6307390eb9c36b864fb9f
--------------------------------------------------------------------------------------
EDIT: After more hours of experimenting I have managed to compile a kernel with the patch mentioned in this post. I can confirm that I faced no reboots since I flashed my phone with this new kernel. Hence, I can confirm this fix really prevents frequent reboots.
superstarksa said:
Hi,
My M30s started randomly restarting after a software update. I could not find solutions here when I searched but it appears a lot of people on the internet having been facing similar issues for quite a few months now. The Samsung community forums are full of multiple messages and Samsung is pushing people to get to their phones to the service centers and are getting the motherboards replaced for free if the warranty is valid (or at a cost of INR 9,000 otherwise).
In any case, I found another poster on the Samsung forums who seems much more tech savvy than I am. And he seems to have solved the problem on his phone by changing 2 lines of code in the Linux kernel wand rebuilding the OS afterward.
Like I said, I am not tech savvy enough for this, but I thought I would post the link here because I could not find this particular fix here.
Re: READ THIS IF YOUR SAMSUNG GALAXY M30S KEEPS RANDOMLY FREEZING AND RESTARTING AUTOMATICALLY
To add a bit of my research into this problem: My phone (SM-M307FN) is rebooting many times every single day due to a Linux kernel issue which has been already fixed a long time ago in the mainline version. I am still running Android 10, because that's the latest version (M307FNXXU2BTC6) of the...
r2.community.samsung.com
(Here is the text from the post in case you are not able to open it)
-----------------------------------------------------------------------
To add a bit of my research into this problem:
My phone (SM-M307FN) is rebooting many times every single day due to a Linux kernel issue which has been already fixed a long time ago in the mainline version. I am still running Android 10, because that's the latest version (M307FNXXU2BTC6) of the OS Samsung has released on their open-source portal. I can use this source code to fix and rebuild the OS to prevent the issue from happening.
The issue and the fix is well known among the Samsung M30s community. It's two lines of code that need to be changed to prevent at least one of the common reasons for frequent reboots.
It takes a lot of work for a private user to fix those two lines of code, because Samsung releases source code that's non-trivial to compile and actually run on your device afterwards.
Samsung's Android 11 still ships with the same old kernel version (4.14.62) as their Android 9 (4.14.62), released back in 2018. There might have been some fixes between 4.14.62-19694174 and 4.14.62-20748039 introduced by Samsung in the meantime.
Regardless, this fix is not part of the source code for M307FNXXU2BTC6 (linked above) that's been released by Samsung in June 2020. Therefore, it doesn't seem like Samsung is actually applying all fixes to their kernels.
The kernel itself should have been upgraded to a higher version - at least to 4.19 - to fix bugs that's been plaguing users of Exynos 9611 chips running on Linux v4.14 for a long time.
Samsung: Please apply this fix to your Android kernels and push the update to your customers. Thank you!
References about the "fix NULL pointer deref in smaps_pte_range()":
Mainline Linux kernel fix:
[4.19,248/361] mm: /proc/pid/smaps_rollup: fix NULL pointer deref in smaps_pte_range()
https://lore.kernel.org/patchwork/patch/1010971/
Google Android Linux kernel backported this change in 2019 :
https://android.googlesource.com/kernel/common/+/043c92bd0517e0018cb6307390eb9c36b864fb9f
--------------------------------------------------------------------------------------
EDIT: After more hours of experimenting I have managed to compile a kernel with the patch mentioned in this post. I can confirm that I faced no reboots since I flashed my phone with this new kernel. Hence, I can confirm this fix really prevents frequent reboots.
Click to expand...
Click to collapse
Amazing work brother, everyone is facing this restart problem but you can help
Can you compile the latest kernal(4.14.113) and share it with our M30s community.
razs.originals said:
Amazing work brother, everyone is facing this restart problem but you can help
Can you compile the latest kernal(4.14.113) and share it with our M30s community.
Click to expand...
Click to collapse
Like I said in my post, I am not tech savvy enough to do this. And I am wondering if this problem has been widely reported even. This is the place I expected to find lot of buzz but i dont see any
Everyone is upset with this Samsung's reboot problem. Anyways we users will find a solution.
I am a M30s owner. I have done this on my phone and it's a temporary fix. Atleast try this and wait for the official fix. It's better to have something than nothing.
How To Fix Restart Issue On Galaxy M30s, M31, M31s, A50, A50s? (Updated) - SamsungSFour.Com
How To Fix Restart Issue On Galaxy M30s, M31, M31s, A50, A50s? (Latest Method)
www.samsungsfour.com