Database Info

[DISCONTINUED][ROM][08 FEB 13][JB4.2.1] JellyTime CM10.1 R6.1 - SAGA

{
"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"
}
JellyTime CM10.1 is an unofficial CyanogenMod 10.1 ROM, made by randomblame for DHD. This is a minimalistic port to Desire S (SAGA) with changing 5-7 Proprietary Files.
Packed with Andromadus Kernel 3, This has very few bugs and can be used as daily driver.
If you come across any bugs , make sure you attach a logcat (Below is a guide on how to take logcat).
INSTRUCTIONS TO FLASH
Code:
- Make Sure You're On The Latest 4EXT Recovery
- Make A Backup
- Wipe Data/Factory Reset In Recovery
- Flash ROM And Follow Aroma Instructions
- Reboot
BUGS
Code:
- Pic taken by camera has green line. Can be fixed by changing pic to 3MP
THIS IS HOW YOU TAKE LOGCAT AND REPORT BUGS
Source : Here
Code:
[B]How To File a Bug Report with Logcat:[/B]
Install android sdk
Install drivers for adb on PC
Connect phone to PC
Open cmd.exe or terminal
Type 'adb logcat' without the quotes
Start the app that causes the issues
Wait for the app to close or get to the error
Copy logcat contents and put in pastebin
Copy pastebin links here
[B]How To Find Wakelocks:[/B]
Install android sdk
Install drivers for adb on PC
Connect phone to PC
Open cmd.exe or terminal
Type 'adb shell cat /proc/wakelocks > wakelocks.txt' without the quotes
Copy contents and put in pastebin
Copy pastebin links on your post
[B]How To Get dmesg logs:[/B]
Install android sdk
Install drivers for adb on PC
Connect phone to PC
Open cmd.exe or terminal
Type 'adb shell dmesg > dmesg.txt' without the quotes
Copy contents and put in pastebin
Copy pastebin links on your post
[B]Before filing a bug report, please consider the answer to these:[/B]
Is the bug reproducible?
How do you reproduce it?
What is the expected behavior?
What actually happens?
Are you on the default Kernel?
Did you restore data of System Apps using Titanium Backup?
CREDITS
Code:
[B]Randomblame [/B]- For Making This Beautiful ROM
[B]Superkid and Andromadus [/B]- For CM10 Kernel
DONATE
Code:
Please Consider Donating
- [B]To Me :[/B] [URL="http://forum.xda-developers.com/donatetome.php?u=4244152"]Donate[/URL]
DONATORS
Code:
- [URL="A-Guest-On-XDA"]Mario Baumann[/URL]
- [URL="http://forum.xda-developers.com/member.php?u=4871428"]TnIan[/URL]
- [URL="http://forum.xda-developers.com/member.php?u=4846465"]AJIEKCander[/URL]
- [URL="A-Guest-On-XDA"]CL[/URL]
- [URL="http://forum.xda-developers.com/member.php?u=3018727"]polda78[/URL]
- [URL="http://forum.xda-developers.com/member.php?u=982728"]OnDemand[/URL]
CLICK ME FOR DOWNLOADS​

CHANGELOG
Code:
[B]JellyTime CM10.1 - R 6.1[/B]
Camera was inverted in R6 this fixes it.
Fixed Bluetooth
[B]JellyTime CM10.1 - R 6.0[/B]
Update kernel
Fixed EGL Fence issue
Fixed Camera
Pulled in a few new commits
[B]JellyTime CM10.1 - R 5.0[/B]
synced with cm
new features all over the place
stability improvements
[B]JellyTime CM10.1 - R 4.0[/B]
Fixed FFC (Front Facing Camera)
Added custom background on lockscreen feature
updated frameworks av quite a bit
synced with cyanogenmod
camera updated
should fix issue some had playing certain file types like mp3s
added SuperSU
[B]JellyTime CM10.1 - R 3.0[/B]
Updated Kernel to 3.0.58
synced with cyanogenmod
changed default io scheduler to sio
changed default cpu governor to interactive
Fixes issue with center clock and am/pm enabled
Fixes google voice search/tts
added call statistics to contacts
[B]JellyTime CM10.1 - R 2.0[/B]
Added Center Clock Option
Changed default wallpaper to match bootanimation and graphic art
Updated prebuilt apks
bootanimation tweaked
[B]JellyTime CM10.1 - R 1.0[/B]
Kernel 3.0.59
based on cm10.1 modified & compiled from source
cid mostly removed
jellytime branding added
jellytime bootanimation added
removed cm updater and cm statistics as usual
added nexus 4 wallpapers
added microbes live wallpaper
added nova launcher
added esfile
lots more
FAQ's - Frequently Asked Questions
Code:
[B]Where can I download this awesome ROM?[/B]
From www.blindndumb.com
[B]What's so awesome about this ROM?[/B]
See Changelog or Refer [URL="http://forum.xda-developers.com/showthread.php?t=1778202"]Here[/URL]
[B]Is a full wipe needed?[/B]
YES , If its first time you are flashing the ROM
NO, it is not required, but it is strongly recommended. If you choose to do a "dirty" flash, please do NOT post bug reports or issues you are having, as something from an earlier release might be causing the issue.
[B]I flashed this awesome ROM but I don't have (insert Google app here) why?[/B]
Gapps were removed from the ROM back on Alpha 7. You simply have to download the gapps from download page and flash via recovery.
[B]Is Project Butter working on this ROM?[/B]
vsync was implemented in Beta 9 and triple buffering in Beta 10. So, yes, Project Butter in included.
[B]I'm having an issue and want to report it but I don't know how.[/B]
First, check the Issue Tracker to see if someone else has reported the same issue. If no one has reported the issue then start a new issue and follow the provided template to describe your issue. Don't forget to attach your logcat.
[B]I keep reading about this "logcat" what is it and how do I make on?[/B]
"The Android logging system provides a mechanism for collecting and viewing system debug output. Logs from various applications and portions of the system are collected in a series of circular buffers, which then can be viewed and filtered."1 To learn more about logcats and how to create them please refer first post
[B]Is Jellytime better/faster then (insert your favorite ROM here)?[/B]
Its all a matter of opinion. You'll get 10 different answers from 10 different people. The reason for this is different people use their phones for different things, so what may be an awesome experience for one might be terrible and full of bugs for another. The best way to choose is to just flash Jellytime and find out for yourself.
[B]How's battery life?[/B]
This is also a matter of opinion. Like the previous question you'll get 10 different answers from 10 different users. People use their phones for different things. The only true answer is to find out for yourself. If you are having battery issues however, there are a few things you can do. First, find out which apps are causing the most drain. Kill them and see if that helps. Second you can re-calibrate your battery.
SIGNATURE
By nissanskylinebam
​

blindndumb said:
Reserved For Me
Below is yours
Click to expand...
Click to collapse
AWESOME,,,,, will try this

Seems good, will try
Sorry for my bad English

ROM is online
Make sure you do a full wipe ..
If you have problem downloading, PM Me
Cheers

reserved........

UUhhh yehaa my first rom on my new desire s and it works wuhhuu
old desire s has fried eMMC :silly:

I don't want to offend you and I appreciate your work. But why you have so many JB Roms? Instead of join all of your efforts and work in only one rom?
Sorry for this question, I'm only trying to understand it.
One more time, thanks for your work.
Sent from my HTC Desire S using xda app-developers app

where can i find the download of this radio RADIO-3831.17.00.16_M? i can't find it and the link here http://forum.xda-developers.com/showthread.php?t=1146601 is dead! thx

sweet, gotta try this soon.
looks like you've got the sound issue resolved, is it possible to base paranoid on this rom?
where can i find the download of this radio RADIO-3831.17.00.16_M?
Click to expand...
Click to collapse
WRONG LINK, SORRY LINK HERE:http://forum.xda-developers.com/showpost.php?p=31990339&postcount=16
blindndumb, you could link to this radio on first post
Fredericosilva said:
I don't want to offend you and I appreciate your work. But why you have so many JB Roms? Instead of join all of your efforts and work in only one rom?
Sorry for this question, I'm only trying to understand it.
Click to expand...
Click to collapse
Everyone have different tastes and like to do things a bit different. Some like cm, some aokp, some love miui, each of them have a different feel, but none of them is fully complete at this stage as there are some issues that are not simple to resolve, so often it's a tradeoff - either more features or less bugs or another bugs
Plus lots of roms here are ports from other devices, just made to work on desire S, and give us a bigger choice.
Also, contrary to what you are saying, developers here exchange info and help each other, so it's not like every dev is just making his rom and not telling everyone. Just look at thanks list rom makers are posting, one maker is often thanked by another etc.
Remember, the whole rom business is not as easy as you may think. Some issues are complex and are caused by sometimes strange things that take time to track down.

thepgo said:
http://hotfile.com/dl/127550064/97802b9/PG88IMG-NEW-RADIO-20.4130.0818U_3817.07.00.19.zip.html
blindndumb, you could link to this radio on first post
Click to expand...
Click to collapse
thanks! i'll install it! :good:

before downloading,,,,,, i must ask,, rear camera preview is working? 720p recording??

when calling,nobody can hear me.
use your radio.ths

thepgo said:
Also, contrary to what you are saying, developers here exchange info and help each other, so it's not like every dev is just making his rom and not telling everyone. Just look at thanks list rom makers are posting, one maker is often thanked by another etc.
Click to expand...
Click to collapse
I think he's trying to say, why doesn't BlindnDumb just make 1/2 ROMs. I kinda get where he's coming from, BlindnDumb has (had) the following ROMs:
BlindBEAN
Codename Android
ParanoidDroid
AOKP Jelly Bean
JellyTime CM10
And in the thread of AOKP Jelly Bean there is also another JellyTime! I can see what this can become confusing.
On the other hand, I have no experience at all in Android Rom coding, what I think he's doing is that he's trying to find the best ROM on any device and then he ports it to Desire S. I'm very grateful for his effortts and I'm sure that he knows what he's doing, so I will not complain about his approach.
That being said, I'm downloading the ROMright now, can't wait to try it out!
EDIT: Camera works without a green or purple line at the side, 720p seems to work, but directly after shooting a short video, my home screen wallpaper gets all messed up. It doesn't seem very smooth at the moment, when opening the app drawer the first few times it opens at about 4 frames per second -.- Rebooting now to see if it helps.
EDIT 2: After a reboot, 720p video was all messed up, changing it back and forth to 480p fixed it.I sadly have to go now,when I'm backi'll make somelogcats.
Adb doesn't work, though.

I am sorry to interrupt but I am just wondering why it is so hard to solve the front camera problem. Haven't we got the HTC kernel source? What else do we need?

In previous post, I posted wrong link to the radio, sorry about that. Here's the 3831.17.00.16_M radio:
http://mirror1.virtuousrom.com/saga/firmware/PG88IMG.zip
FLASH THIS RADIO BEFORE FLASHING ANY ROM. FLASHING IT AFTER CAN MESS THINGS UP ON YOUR ROM, POSSIBLY WIPE YOUR DATA. BACKUP FIRST.

thepgo said:
In previous post, I posted wrong link to the radio, sorry about that. Here's the 3831.17.00.16_M radio:
http://mirror1.virtuousrom.com/saga/firmware/PG88IMG.zip
FLASH THIS RADIO BEFORE FLASHING ANY ROM. FLASHING IT AFTER CAN MESS THINGS UP ON YOUR ROM, POSSIBLY WIPE YOUR DATA. BACKUP FIRST.
Click to expand...
Click to collapse
What does thisbradio change
Sent from my Desire S using xda app-developers app

Installed this ROM but it seems that phone doesn't work, the other person doesn't hear me. Only echoes back his input. Using radio: 20.76.30.0835U_3831.19.00.110
Too bad cause the speed seemed fantastic
LE: noticed the Radio mention in the initial post, sorry but I'm not interested in downgrading radio

ste_vlad said:
Too bad cause the speed seemed fantastic
Click to expand...
Click to collapse
Really? For me it's the slowest ROM I've ever had unfortunately. I'll try to reinstall it.
Anyway here is a pastebin for the "no voice issue"
http://pastebin.com/uFNTSxqC
Some errors from the logcat:
E/AudioHardwareMSM7X30( 4624): updateDeviceInfo: E rx_device 6 and tx_device 11
E/AudioHardwareMSM7X30( 4624): updateDeviceInfo: X cur_rx 6 cur_tx 11
E/Trace ( 5802): error opening trace file: No such file or directory (2)
E/msm7x30 PowerHAL( 4741): Error opening /sys/devices/system/cpu/cpufreq/ondemand/sampling_rate: No such file or directory
E/MM_OSAL ( 4624): FileSourceHelper::ValidateAACFile failed
Some other errors while just going into system menus and/or connecting to USB:
E/WifiStateMachine( 4741): Failed to set country code nl
E/VoldConnector( 4741): NDC Command {32 volume unmount /storage/sdcard0 force} took too long (1269ms)
E/VoldConnector( 4741): NDC Command {36 volume mount /storage/sdcard0} took too long (7714ms)
E/VoldConnector( 4741): NDC Command {37 volume shared /storage/sdcard0 ums} took too long (7657ms)
Next problem, glitchy camera footage:
http://pastebin.com/bNYdBRXe
What I did: I press Home,open app drawer, open camera,take a picture, switch to video mode,make a 720p video
The picture came out OK, the video was glitchy, see http://youtu.be/mVQNc47tCpo
Some errors from the logcat:
E/videocamera( 2472): Color effect value =none
E/mm-camera( 1431): [Flash Calibration] read from file OK: /sys/android_camera_awb_cal/awb_cal (3624) (32)
E/mm-camera( 1431): HTC_AWB_Calibration_Reference_Points_Correction, [Flash Calibration] Not load Flashlight-Calibraton data
E/QualcommCameraHardware( 1431): found match returning 0
E/QualcommCameraHardware( 1431): found match returning 1 etc..
All with default kernel
No Titanium Backup

Fredericosilva said:
I don't want to offend you and I appreciate your work. But why you have so many JB Roms? Instead of join all of your efforts and work in only one rom?
Sorry for this question, I'm only trying to understand it.
One more time, thanks for your work.
Sent from my HTC Desire S using xda app-developers app
Click to expand...
Click to collapse
Thats possible only from source, merging all features in one.. I do have some plans
Haomuch said:
I am sorry to interrupt but I am just wondering why it is so hard to solve the front camera problem. Haven't we got the HTC kernel source? What else do we need?
Click to expand...
Click to collapse
Because the andromadus kernel is made from One V sources which doesnt have FFC
Yes, Sources have been released for our device but Someone needs to work on that to work with aosp..
zxzyzd said:
Really? For me it's the slowest ROM I've ever had unfortunately. I'll try to reinstall it.
Anyway here is a pastebin for the "no voice issue"
http://pastebin.com/uFNTSxqC
Some errors from the logcat:
E/AudioHardwareMSM7X30( 4624): updateDeviceInfo: E rx_device 6 and tx_device 11
E/AudioHardwareMSM7X30( 4624): updateDeviceInfo: X cur_rx 6 cur_tx 11
E/Trace ( 5802): error opening trace file: No such file or directory (2)
E/msm7x30 PowerHAL( 4741): Error opening /sys/devices/system/cpu/cpufreq/ondemand/sampling_rate: No such file or directory
E/MM_OSAL ( 4624): FileSourceHelper::ValidateAACFile failed
Some other errors while just going into system menus and/or connecting to USB:
E/WifiStateMachine( 4741): Failed to set country code nl
E/VoldConnector( 4741): NDC Command {32 volume unmount /storage/sdcard0 force} took too long (1269ms)
E/VoldConnector( 4741): NDC Command {36 volume mount /storage/sdcard0} took too long (7714ms)
E/VoldConnector( 4741): NDC Command {37 volume shared /storage/sdcard0 ums} took too long (7657ms)
Next problem, glitchy camera footage:
http://pastebin.com/bNYdBRXe
What I did: I press Home,open app drawer, open camera,take a picture, switch to video mode,make a 720p video
The picture came out OK, the video was glitchy, see http://youtu.be/mVQNc47tCpo
Some errors from the logcat:
E/videocamera( 2472): Color effect value =none
E/mm-camera( 1431): [Flash Calibration] read from file OK: /sys/android_camera_awb_cal/awb_cal (3624) (32)
E/mm-camera( 1431): HTC_AWB_Calibration_Reference_Points_Correction, [Flash Calibration] Not load Flashlight-Calibraton data
E/QualcommCameraHardware( 1431): found match returning 0
E/QualcommCameraHardware( 1431): found match returning 1 etc..
All with default kernel
No Titanium Backup
Click to expand...
Click to collapse
So you copied all the E/
Will look at that..
And guys I am not telling anyone to upgrade / downgrade radio. I have just put my device info in case anyone needs.
- I havent faced any sound issues during call.
- Confirmed Video Issues with 720p Recording
- About smoothness, I am using as daily for last two days, no such prob
For battery drain issues, flash 77n Kernel
While booting for the first time . Dont start messing with your phone, Let the startup processes end ! (Keep calm for atleast a minute)

Breaking: Android 4.3 For Google Nexus 4 Leaks (JWR66N) - Here's The System Dump

Breaking: Android 4.3 For Google Nexus 4 Leaks (JWR66N) - Here's The System Dump​
For the past few hours, I've been observing a curious case of Jeff Williams on Google+. Jeff posted a screenshot of what he claimed was a Nexus 4 he bought from a Googler... with a build of Android 4.3 on it. The same build, JWR66N, that we saw leaked earlier on a Galaxy S4 GPE by SamMobile.
{
"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"
}
In disbelief, some have called him a hoaxer, but a number of resourceful folks decided to get Jeff on IRC (channel #Android43 on freenode) and worked with him for hours, trying over and over to get the magical system dump that would prove Jeff's story to be real.
The system dump, which we have since confirmed as legitimate and along with dozens of other IRC members mirrored to multiple destinations, indeed belongs to a Nexus 4 (mako), and the build number is indeed JWR66N. The radio and bootloader are missing right now - Jeff promised them tomorrow - so I have my doubts about a working port to other Nexus 4s for the time being.
In the meantime, the system dump itself is ready to go, and Ron and I are ripping through it as we speak. We'll have a teardown ready for you soon if we do dig something up, and by the looks of things, there's enough for a post.
I'd like to thank Jeff for his persistence as well as IRC users efrant, gravufo, Jason__, vividboarder, Introspection, and everyone else who drove this one to the finish line.
Update: There's chatter on IRC that restoring the backup via TWRP recovery seems to work. We haven't tested this, so if you do decide to proceed, do so with caution and after making a full backup of your entire system.
AP mirror #1
AP mirror #2
AP mirror #3
AP multi-mirror
Even more mirrors (by hackthevoid)
Breaking: Android 4.2.2 (Build JDQ39) Update Rolling Out To GSM Galaxy Nexus, Nexus 7, Nexus 10​
exus owners may have a reason to stay up tonight, as a couple of Reddit users report that Android 4.2.2 has begun rolling out to the GSM Galaxy Nexus and the Nexus 7.
There's not much word regarding what the update (which carries build JDQ39) includes just yet, but readers may remember that Google promised a Bluetooth A2DP audio streaming fix in the "next release" of 4.2 after 4.2.1.
At the moment it would seem that Reddit users in the thread linked below are the only ones reporting success at grabbing the update, so it's hard to judge the thread's veracity. If 4.2.2 has hit your device, though, let us know in the comments below.
Update: It looks like the update is rolling out after all. We've received confirmation from a number of users on Google+, including Marco Duran, who kindly provided some shots of the 47.6MB download from the Nexus 10.
Source: Android Police

4.2.2 nexus 7
NEED OTA LINK FOR NEXUS 7:laugh::laugh:

Here's The Android 4.2.2 JDQ39 Update For The GSM Galaxy Nexus
Here's The Android 4.2.2 JDQ39 Update For The GSM Galaxy Nexus [Manual Installation Instructions]​
A couple of hours ago, Google started rolling out the Android 4.2.2 update to a very limited subset of Nexus devices (build JDQ39). At this point, almost nobody can get the OTA pulled by going through the Settings screen, but don't worry - one of our loyal readers extracted the OTA url for the Galaxy Nexus and sent it over to us (great work, Daniel Koch!).
For now, we only have the link for the takju Galaxy Nexus variant, i.e. GNex handsets bought from the Play Store. Once we get the yakju build, we'll update this post.
Note: Every Custom ROM flashing May have risk. So, please do it at your own Wish.
If you're not sure whether you have a takju or yakju variant, download Nexus Update Checker from the Play Store and see what it says.
Click to expand...
Click to collapse
What's New?
We don't have any reliable information at this point because Google hasn't pushed the 4.2.2 files to AOSP yet or published any changelogs. We suspect the Bluetooth bug has been fixed, but are unclear what else has changed right now.
There is a new radio in this OTA.
Prerequisites
Your device should be running build JOP40D before trying to install the update manually. If you for some reason don't have JOP40D, Google has it available in factory image form here.
For those ready to download and install manually, the process is easy. If you
have a custom recovery, just download the zip (linked below), move it to your device, and flash as usual
have the stock recovery, keep the zip file on your computer and follow a few easy instructions below
Manual Instructions
Step 1.
Reboot your Galaxy Nexus, holding the Volume Up and Volume Down buttons while it boots up. Once you see the fastboot menu and "Start," press Volume Up to navigate to "Recovery" and press the power button. Once you see an Android with a red exclamation point icon, press Volume Up and the Power button together, which will bring you to a new menu. Navigate to "apply update from adb."
Step 2.
Connect your Galaxy Nexus to your computer with a USB cable.
Make sure you have a recent version of adb that supports the sideload command (if you don't, download the latest Android SDK to ensure your adb is up-to-date).
Open up a command prompt (cmd in Windows, regular shell in Linux and Mac) in the same directory as the zip file you've downloaded.
Type in the following:
adb sideload 472aafeb9fe3.signed-takju-JDQ39-from-JOP40D.472aafeb.zip
Click to expand...
Click to collapse
You should see a progress bar, which will eventually hit 100%. At this point, your device is installing the update.
Step 3.
Reboot and enjoy! You are now running Android 4.2.2 on your Galaxy Nexus.
Download
Here's the OTA, hosted on Google's servers: takju build JDQ39.
AP mirror just in case it goes down: AndroidFileHost.
MD5: d37cd3aeeacc0d25a523acbebb5557f4
File size: 46.4 MB (48,672,997 bytes)
Source: Android Police

Shouldn't this file word being updated from recovery the normal way to?
I'm on Galaxy Nexus takju with TWRP recovery, and my updated failed..
EDIT: I get this error. assert failed: apply_patch _check ("system/lib/li
E: Error in /sdcard/filename.zip
(status7)
Error flashing zip
Updating partition details
/Söder

Re: Breaking: Android 4.2.2 (Build JDQ39) Update Rolling Out To GSM Galaxy Nexus, Nex
Good update
Sent from my GT-I8150 using xda app-developers app

soder said:
Shouldn't this file word being updated from recovery the normal way to?
I'm on Galaxy Nexus takju with TWRP recovery, and my updated failed..
EDIT: I get this error. assert failed: apply_patch _check ("system/lib/li
E: Error in /sdcard/filename.zip
(status7)
Error flashing zip
Updating partition details
/Söder
Click to expand...
Click to collapse
Try to flash using CWM buddy. Also are you applying the commands..??

soder said:
Shouldn't this file word being updated from recovery the normal way to?
I'm on Galaxy Nexus takju with TWRP recovery, and my updated failed..
EDIT: I get this error. assert failed: apply_patch _check ("system/lib/li
E: Error in /sdcard/filename.zip
(status7)
Error flashing zip
Updating partition details
/Söder
Click to expand...
Click to collapse
Dude it's not a regular flashable zip. You need a takju stock recovery.

m.kochan10 said:
Dude it's not a regular flashable zip. You need a takju stock recovery.
Click to expand...
Click to collapse
But, as I remember it, the 4.2.1 update was that kind of that kind of zip to?
And I was told I could flash it in a custom recovery? Or do I remember it wrong?
EDIT: This is where I got that info I think
http://forum.xda-developers.com/showthread.php?p=34706283#post34706283
and also from here
http://forum.xda-developers.com/showthread.php?t=1592689&page=84
Also:
"For those ready to download and install manually, the process is easy. If you
have a custom recovery, just download the zip (linked below), move it to your device, and flash as usual"
EDIT2: I now remember that I might have edited my gps.conf, and created a new file. That might have anything to do with it? How do I get back an "untouched" version? I go have a backup of the stock rom, but how do I get the file back untouched?
/Söder

Re: Breaking: Android 4.2.2 (Build JDQ39) Update Rolling Out To GSM Galaxy Nexus, Nex
Now the source needs to be updated so I can get it on my Samsung galaxy s1
Sent from my SCH-I500 using Tapatalk 2

Android 4.2.2 (JDQ39) Source Has Started Pushing To AOSP
Android 4.2.2 (JDQ39) Source Has Started Pushing To AOSP [Updated]​
It's begun - the newest version of Android, 4.2.2, is being pushed to AOSP right now. We saw the accompanying Nexus OTA rollout start last night, with update files slowly springing up thereafter. Right now, 4.2.2 builds can be downloaded for the Takju Galaxy Nexus, Nexus 7 (Wi-Fi), and Nexus 10.
The build number is JDQ39 and the tag in AOSP is android-4.2.2_r1. Here are a few of the many directories that have been updated:
/device/common/+/android-4.2.2_r1
/platform/dalvik/+/android-4.2.2_r1
/platform/build/+/android-4.2.2_r1
While the push has just started this morning, source will likely continue to show up throughout the day, and we'll update this page as that happens. The Android Building Google Group should have a post by JBQ when the push is complete.
Update: It appears the push has finished, all Android 4.2.2 code should be in AOSP now.
They're working on compiling a full developer changelog right now, and once we've done that, we'll try to come up with a more human-readable one.
[Developer Changelog] Here's What's New In Android 4.2.2 (JDQ39)​
Following yesterday's Android 4.2.2 OTAs to various Nexus devices, Google today followed up with the push of all 4.2.2 open source code changes to AOSP. There is a lot here to parse through this time around compared to the minor 4.2.1_r1.2 commit from 10 days ago.
We've already identified some obvious user-facing changes, which we'll post about separately soon to keep it clean and organized. The purpose of this post is, as before, to find the low-level changes that may not be obvious. So move the beard out of the way and dig in.
Update: Ron detailed some new things here: New Android 4.2.2 Features: Toggle From Quick Settings, Better App Download Notifications, and Some New Sounds!
What's New?
Things we've discovered so far, in brief:
Play Store downloads now show time left to download.
Long-pressing Wi-Fi and BT now toggles them in the notification Quick Settings.
More secure ADB thanks to the new whitelist.
BT bug fixes? I've seen conflicting reports whether this is fixed - citation needed if anything's been done to it. Can you spot the right commits?
Update #1: Play a tone when wireless charging begins (if below 95% battery). Use new low battery and wireless charging sounds on Mako. Here are the new sounds: WirelessChargingStarted.ogg and LowBattery.ogg.
Here is the list of developer commits in 4.2.2 (AOSP tag android-4.2.2_r1, JDQ39) compared to 4.2.1's latest revision (AOSP tag android-4.2.1_r1.2, JOP40G).
Note: For whatever reason, some of these we may have seen before - perhaps someone who understands the intricacies of AOSP's git structure can explain why they're getting included in the diff, but for the most part, this is all new stuff.
Code:
Project name: /platform/development
•Chris Banes - Update bitmapfun sample to call recycle()
•Dirk Dougherty - Add redirect for removed file.
•Dirk Dougherty - Minor updates to keep androiddevdocs redirect in sync with devsite version (in frameworks/base)
•Adam Koch - Bitmapfun Sample: Fix bug where background image loading could hang
•Chet Haase - Cherrypick from Change-Id: I4ae984cf776604cede32b98db6b1eb3cb6c59c7e
•Adam Koch - Bitmapfun Sample: Change cache memory calculation to use maxMemory()
•Adam Koch - Bitmapfun Sample: Fix inSampleSize selection and update dependencies
•Katie McCormick - Network sample: fix typo in manifest
•Xavier Ducrohet - Update platform tools rev to 16.0.2
•Dirk Dougherty - Add ko and ru to validLangs.
•Joe Malin - Android Training: Threads sample app
•Dirk Dougherty - Add redirect for IAB v3 restructure.
•Dianne Hackborn - SDK Only: Fix search interaction with various samples.
•Dirk Dougherty - Redirects /guide/google to /google/.
•Xavier Ducrohet - Move plat-tools SDK component rev to 16.0.1
•&& repo sync -j8 - Doc change: sample app for Notifications class
•Scott Main - docs: update redirects for articles
•Scott Main - docs: add redirects for best practices pages that moved to training
•Scott Main - docs: a few bonus redirects for dac
•Andy Stadler - Cleanup eclipse .classpath for Gallery2
•Scott Main - docs: redirect next steps to building first app class
Project name: /platform/cts
•Leo Liao - DO NOT MERGE Add missing features of JB and JB MR1
•Leo Liao - Add missing features of JELLY_BEAN to feature list
•Brian Muramatsu - Updated Holo test assets for JB MR1
•Nick Kralevich - FileSystemPermissionTest: add directories
•Brian Muramatsu - DO NOT MERGE Update CTS Verifier to R4
•Brian Muramatsu - DO NOT MERGE Update CTS Verifier to R5
•Laurent Tu - Restore CtsVerifier rate for passive updates
•Brian Muramatsu - Some Holo Test Improvements
•Nick Kralevich - Try reading every file on /sys
•Brian Muramatsu - DO NOT MERGE Update CTS Verifier version again
•Marco Nelissen - Improve testSetNextMediaPlayer test
•Brian Muramatsu - DO NOT MERGE Update CTS Verifier version to 4.2 R3
•Brian Muramatsu - DO NOT MERGE Update CTS Verifier version to 4.1_R4
•Laurent Tu - Assert mean and stdev of update deltas
•Nick Kralevich - Add CVE to Exynos vulnerability test.
•Brian Muramatsu - DO NOT MERGE Update CTS Verifier Version to 4.1_R3
•Laurent Tu - DO NOT MERGE Relax LocationVerifier assertions.
•steven_huang - DO NOT MERGE Filter out the overdue location cases in GPS test
•Brian Muramatsu - DO NOT MERGE Update CTS Verifier Version to 4.2_r2
•Laurent Tu - DO NOT MERGE Relax LocationVerifier assertions.
•Brian Muramatsu - DO NOT MERGE Update CTS Verifier Version to 4.2_r2
•Laurent Tu - DO NOT MERGE Relax LocationVerifier assertions.
•Brian Muramatsu - DO NOT MERGE Update CTS Verifier Version to 4.1_R3
•Laurent Tu - DO NOT MERGE Relax LocationVerifier assertions.
•steven_huang - DO NOT MERGE Filter out the overdue location cases in GPS test
•Nick Kralevich - Add Exynos vulnerability tests.
•Adam Momtaz - CTS tests for UiAutomator at API 17
•Marco Nelissen - Add test for MediaScanner misbehavior
•Andreas Huber - Add a CTS test that iterates through all codecs using MediaCodecList and
•Andreas Huber - Adds a CTS test verifying audio encoder functionality. (AAC, AMR-NB, AMR-WB)
•Adam Momtaz - Fixed a mistakenly deleted line from the last submit
•Marco Nelissen - Fix ringtone test
•Brian Muramatsu - Update BuildVersionTest to support 4.2.2
•Fabrice Di Meglio - Fix bug #7664208 android.widget.cts.TextViewTest#testResetTextAlignment failures on JD
•Eino-Ville Talvala - CTS Verifier: Fix Camera Formats preview orientation.
•Fabrice Di Meglio - Fix bug #7664305 android.widget.cts.TextViewTest#testResetTextDirection failures on JD
•Adam Momtaz - UiAutomator test APK and Tests for CTS
•Fabrice Di Meglio - Add more CTS tests for the reset of RTL properties
•Keun young Park - DO NOR MERGE make reboot default in CTS (merge from mr1)
•Keun young Park - add log to print time-out when time-out happens
•Nick Kralevich - Add more tests for restricted broadcasts.
•Keun young Park - add 4.2.1 to version list
•Svetoslav Ganov - Cannot move edit text cursor to first position using character granularity.
•Keun young Park - change all file writes to random access with O_SYNC
•Brett Chabot - Add UiAutomator test skeleton to CTS.
•Svetoslav Ganov - Fix the shell commands used to clean up after the accessibility tests.
•Svetoslav Ganov - Add NumberPicker CTS tests.
•Nick Kralevich - FileSystemPermissionTest: Expand block device tests.
•Keun young Park - force reboot after accessibility test
•Guru Nagarajan - Version number for CTS 4.2 modified: tools/tradefed-host/src/com/android/cts/tradefed/build/CtsBuildProvider.java
•Brian Muramatsu - Report suite name to result server
•Igor Murashkin - Camera: New test to check app firing intent after capturing picture/video
Project name: /platform/prebuilts/sdk
•Ying Wang - Drop official SDK 17
Project name: /platform/prebuilts/misc
•Brett Chabot - Manually update tradefed prebuilt from jb.
•Xavier Ducrohet - Update Layoutlib_api to API 9. do not merge.
Project name: /platform/hardware/libhardware
•Mathias Agopian - Fix HWC documentation.
Project name: /platform/hardware/libhardware_legacy
•Eric Laurent - audio policy: notification delay - DO NOT MERGE
•Eric Laurent - audio policy: fix volume problem - DO NOT MERGE
•John Grossman - audio policy: fix dynamic parameter - DO NOT MERGE
•Jason Simmons - audio policy: direct output fix - DO NOT MERGE
•Irfan Sheriff - Fix stop supplicant api
Project name: /platform/hardware/ril
•Wink Saville - Update documenation for DATA_REGISTRATION_STATE
remaining Can be view here -> [URL="https://gist.github.com/archon810/4772945#file-changelog_android-4-2-1_r1-2_android-4-2-2_r1-txt"]ile-changelog_android-4-2-1_r1-2_android-4-2-2_r1-txt[/URL]
Detailed Changelog
Full_changelog_android-4.2.1_r1.2_android-4.2.2_r1.txt
Source: Android Police

Thanks for change log, I have not yet received the update but know that flashing will be good to get a fresh start.

nexus4?

Android 4.2.2 adds new sounds and notification toggles
Android 4.2.2 adds new sounds and notification toggles​
Why just the other day, we told you that Android 4.2.2 was being sent out to the Google Nexus 10, Google Nexus 7 and the Samsung GALAXY Nexus. While there has not yet been any changelist, we do have some information from those who have installed it on their tablet or phone. First of all, there is a new notification bar that shows you the time remaining and the percentage left of an in-progress app download. A change to Quick Settings lets you long press on the Bluetooth or Wi-Fi square to turn them into toggle switches. Now here is where it gets confusing. The Airplane Mode box is a single press toggle while some boxes do not change any settings.
Calculate speed of in-progress downloads and estimate time remaining until completion. Uses a moving average that is weighted 1:1 with the most recent 500ms sample. Funnels timing data to notifications through DownloadHandler."-How Google calculates the time remaining of an app download
Click to expand...
Click to collapse
Android 4.2.2 also brings a couple of new sounds, The two short bursts that tell you that your battery is low has been replaced while there is now a sound for wireless charging. Previously, the latter had no sound at all.
It should be interesting to see how the Android 4.2.2 update affects the next distribution data from Google. Also, we could see Android 4.0 drop more as some devices get updated to Android 4.1. The large chunk of Android users sporting a device powered by Gingerbread is only going to dissipate slowly as those owners start to upgrade once their 2-year contract expires. Those Android 2.3 phones will be replaced by Android 4.1 by the time the updates are in full swing, providing another reason to expect Ice Cream Sandwich to continue to melt.
If you have installed the Android 4.2.2 update on any of your devices, drop us a comment with some of the other changes that you might have noticed.
Source: PhoneArena

The Nexus 4 Finally Gets Android 4.2.2 (JDQ39) As Well - Here Are Instructions For In
ctakah27 said:
nexus4?
Click to expand...
Click to collapse
The Nexus 4 Finally Gets Android 4.2.2 (JDQ39) As Well - Here Are Instructions For Installing It Manually​
Good news, everyone! The Nexus 4 Android 4.2.2 OTA (JDQ39) is finally here, surprisingly late in the update cycle, following the Nexus 10 and older Nexus devices, such as both variants of the Nexus 7 and both variants of the Galaxy Nexus. Chances are you probably don't have the coveted update notification just yet, but who wants to wait if you can sideload it manually? Rooted, unrooted, stock or custom recovery - it matters not.
What's New?
To see what's new in Android 4.2.2, see New Android 4.2.2 Features: Toggle From Quick Settings, Better App Download Notifications, and Some New Sounds!
Code:
[B]Heads up:[/B] There is also a new radio in this update.
Prerequisites
Your device should be running build JOP40D before trying to install the update manually. If you for some reason don't have JOP40D, Google has it available in factory image form here.
For those ready to download and install manually, the process is easy. If you
have a custom recovery, just download the zip (linked below), move it to your device, and flash as usual
have the stock recovery or a custom recovery that supports sideloading, keep the zip file on your computer and follow a few easy instructions below
Manual Instructions
Step 1.
Reboot your Nexus 4, holding the Volume Down button while it boots up. Once you see the fastboot menu and "Start," press Volume Up to navigate to "Recovery" and press the power button. Once you see an Android with a red exclamation point icon, hold Power and press Volume Up a few times, which will bring you to a new menu. Navigate to "apply update from adb."
Step 2.
Connect your Nexus 4 to your computer with a USB cable.
Make sure you have a recent version of adb that supports the sideload command (if you don't, download the latest Android SDK to ensure your adb is up-to-date).
Open up a command prompt (cmd in Windows, regular shell in Linux and Mac) in the same directory as the zip file you've downloaded.
Type in the following:
Code:
adb sideload de8b8d101614.signed-occam-JDQ39-from-JOP40D.de8b8d10.zip
You should see a progress bar, which will eventually hit 100%. At this point, your device is installing the update.
Step 3.
Reboot and enjoy! You are now running Android 4.2.2 on your Nexus 4.
Download
Here's the OTA, hosted on Google's servers: build JDQ39.
MD5: 1c752738f65acfd48f2d3b6e6e11a654
File size: 51.0 MB (53,529,568 bytes)
Source: AndroidPolice

Thank You
Thanks for change log!

rishabhgangwar said:
Thanks for change log!
Click to expand...
Click to collapse
Pressing thanks button can speak louder then words in Xda buddy..

question
do we need to wipe data to complete this action? is there any problem could face SDCARD folder?

New 4.3 Update found Check the OP.:good:
Breaking: Android 4.3 For Google Nexus 4 Leaks (JWR66N) - Here's The System Dump

Disturbed™ said:
New 4.3 Update found Check the OP.:good:
Breaking: Android 4.3 For Google Nexus 4 Leaks (JWR66N) - Here's The System Dump
Click to expand...
Click to collapse
thanks for the convincing statements :good:

[5.0.x] [SM-T325] CyanogenMod 12.0 UNOFFICIAL Nightlies for the Tab Pro 8.4 LTE

CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.0.x (Lollipop), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Instructions
First time flashing CyanogenMod 12.0 on your device, or coming from another ROM?
Download the zip(s).
Install a compatible Recovery
Perform a NANDroid backup of your current ROM (Optional)
Wipe data & cache partitions of your device (required when coming from stock!).
Flash CyanogenMod.
Optional: Install the Google Apps addon package.
Known Issues
* None
Other Issues?
Before posting on this thread, make sure of a few things:
You've utilized the search function of the forums. Nothing irritates me more than lazy people who do not search for an answer before asking.
If you are the only one having a problem. Boot into recovery, wipe data/factory reset, reflash the rom/gapps and nothing else. Boot up and see if the problem persists.
Make sure your post is relevant to this thread. "I'm having problems rooting/unlocking" is NOT relevant here.
LOGS LOGS LOGS!!!! Use this: SysLog by Tortel
Download Links
CyanogenMod: download.crpalmer.org
Google apps addon:
Download: http://d-h.st/users/dhacker29/?fld_id=27426 (use latest lp gapps)
XDA:DevDB Information
CyanogenMod 12.0 for MondrianLTE (Unofficial), ROM for the Samsung Galaxy Tab Pro 12.2, 10.1, 8.4
Contributors
crpalmer
ROM OS Version: 5.0.x Lollipop
Version Information
Status: Testing
Created 2015-03-02
Last Updated 2015-03-02

Reserved

error installing
cwm error log
Code:
-- Installing: /storage/sdcard1/cm-12-20150302-UNOFFICIAL-mondrianlte.zip
Finding update package...
I:Update location: /storage/sdcard1/cm-12-20150302-UNOFFICIAL-mondrianlte.zip
Opening update package...
Installing update...
minzip: Extracted 3 file(s)
detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/systemabout to run program [/tmp/install/bin/backuptool.sh] with 2 args
Not backing up files from incompatible version: 12
run_program: child exited with status 127
about to run program [/tmp/install/bin/otasigcheck.sh] with 1 args
erasing 627200 blocks
blkdiscard failed: Invalid argument
writing 118679 blocks of new data
lseek64 failed: Invalid argument
E:Error in /storage/sdcard1/cm-12-20150302-UNOFFICIAL-mondrianlte.zip
(Status 1)
Installation aborted.
I:using /data/media for /sdcard/0/clockworkmod/.last_install_path.
I:Cannot load volume /misc.
I:Can't partition non mmcblk device: /devices/msm_sdcc.2/mmc_host/mmc1

runoverheads said:
cwm error log
Code:
-- Installing: /storage/sdcard1/cm-12-20150302-UNOFFICIAL-mondrianlte.zip
Finding update package...
I:Update location: /storage/sdcard1/cm-12-20150302-UNOFFICIAL-mondrianlte.zip
Opening update package...
Installing update...
minzip: Extracted 3 file(s)
detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/systemabout to run program [/tmp/install/bin/backuptool.sh] with 2 args
Not backing up files from incompatible version: 12
run_program: child exited with status 127
about to run program [/tmp/install/bin/otasigcheck.sh] with 1 args
erasing 627200 blocks
blkdiscard failed: Invalid argument
writing 118679 blocks of new data
lseek64 failed: Invalid argument
E:Error in /storage/sdcard1/cm-12-20150302-UNOFFICIAL-mondrianlte.zip
(Status 1)
Installation aborted.
I:using /data/media for /sdcard/0/clockworkmod/.last_install_path.
I:Cannot load volume /misc.
I:Can't partition non mmcblk device: /devices/msm_sdcc.2/mmc_host/mmc1
Click to expand...
Click to collapse
Try again with tomorow's nightly build. I missed a commit to mondrianwifi which fixes the ability to flash the build on EUR devices which have a smaller /system/ partition. I just pushed that change and it will be picked up in tomorrow's build. If that doesn't fix it, let me know.

YESSSS!!!!! Very thanks, you are the number one
---------- Post added at 07:11 AM ---------- Previous post was at 06:18 AM ----------
"Error: unable mount /system" during the flash via TWRP

No SIM
the new build works but does not recognize the sim

adrenalynik said:
the new build works but does not recognize the sim
Click to expand...
Click to collapse
Try removing this line from /system/build.prop:
persist.radio.apm_sim_not_pwdn=1

crpalmer said:
Try removing this line from /system/build.prop:
persist.radio.apm_sim_not_pwdn=1
Click to expand...
Click to collapse
Great! Work very well, but the apn settings are missing. The " Cellular Network" in "Setting" is not visible.

adrenalynik said:
Great! Work very well, but the apn settings are missing. The " Cellular Network" in "Setting" is not visible.
Click to expand...
Click to collapse
I can't believe I never noticed that was missing... Doh!
You can either wait for tomorrow's build or add this:
Code:
<?xml version="1.0" encoding="utf-8"?>
<!-- Copyright (C) 2009 The Android Open Source Project
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
-->
<!-- This is the standard set of telephony features for a GSM phone. -->
<permissions>
<feature name="android.hardware.telephony" />
<feature name="android.hardware.telephony.gsm" />
</permissions>
in the file:
Code:
/system/etc/permissions/android.hardware.telephony.gsm.xml
.

the file does not exist, I have create it and the menu is appeared.
You are the best!

Dear crpalmer,
short report from germany:
Having a german SM-T325 with t-mobile sim, running your CM11
Backup of apps with titanium backup
Factory reset plus formatted /system with twrp 2.8.4.0
Installed image 20150303 plus pa-gapps plus SuperSU
Rebooted
Language selector did not detect the german sim
Initial setup without any topic
Restored apps with titanium
Applied the mods from post #7 and #9
Rebooted
Everything fine: Calling, texting and ussd codes are working.
"Mobile Networks" available under settings.
This looks very promising!
Thanks a lot!
Stefan

i purchased a couple of days ago a 2nd hand set, 2 days which were enough to get me pissed bout samsung os crap
So I installed this and I can finally breathe. I can't be very accurate but it seems to me that it depletes battery a bit too fast when "idling" so I just got wakelock detector installed and will monitor, meanwhile someone more familiar with the device than me can confirm this CM12 is indeed not a batteryguzzler and it's just mine the exception ?
PS: Thanks to crpalmer for the beautiful rom, i have yet to insert the sim so I wouldnt have noticed the error posted above. Works great here and supersmooth.

Thx @crpalmer - great job with this first CM12 port, so far all works without any hickups and the 2 little changes to enable APN worked flawlessly.
Thumbs up

The setting "Cellular network" continues to disappear and if I set the camera resolution to 6mpx, the image is distorted.

wonderful rom many thanks for the lollipop flavor update so far so good you rock!!

adrenalynik said:
The setting "Cellular network" continues to disappear and if I set the camera resolution to 6mpx, the image is distorted.
Click to expand...
Click to collapse
I had to give all wipes with the new nightly, i try a dirty update and network didnt work
now everything is perfect

Anyone having WiFi issues?
I can connect fine to my virgin router 5ghz but can't connect to any of my Cisco WAP devices on 5 or 2.4 GHz frequencies
Was a fresh wipe and install and have tried the 4 different versions posted

Everything works fine here! Thanks crpalmer for the great work!!
Two questions:
- anyone noticed some little lags browsing the launcher pages or opening apps?
- do you use any tweak to hide root in certain apps?
Sent from my SM-T325 using XDA Free mobile app

Thanks für that great ROM!!!! I sent you a donation via paypal.

I tried latest version aka cm120703 but there was 1 big problem. Cyanogenmod setting screen went fine to point where it asks for cm account. No matter if i skip it or sign in ...i'm directed to begining where to select language, set wlan and then again cm account... Here we go again to select language and so on. I tried reboot and other stuff but all i got was cycle as previously mentioned. I'll try 0603 version next.
Edit: 0603-version installed nicely. No problems.

[ROM & discussion][7.1.2_r11][Grouper|Tilapia][3May2017]AOSP - UNOFFICIAL

In Android ROMs' developments, I always start with AOSP. It is the root and if I want to do it right, I have to make it work for AOSP first. Putting the AOSP tests in my kernel thread is getting messy. As I would continue my work here for a while. Starting a thread for AOSP seems reasonable.
Here is for sharing of experiences and discussions.
There would be no nightly, weekly or monthy. I would follow the releases of AOSP and keep it as genuine as possible. If you are looking for a feature, there are many nice ROMs out there.
Known Issues:
　1. AOSP Camera App　The AOSP Camera2 app is not working with the Nexus 7 (2012) which is the only (I think) Nexus device with a Front Camera but not the Back Camera. The new Camera2 app set the back camera as default. I can make the preview shown by a simple overlay configs. But, make it really work would be quite a work. In the app market(s), there are many camera apps already taking care of that and would work flawlessly. I see no reason to waste time on that.​　2. "E:unknown command [log]"　If you got this message when flashing, don't panic. It's the new "block_image_update()" in recovery cause that. It would do no harm and it would be gone in the next TWRP.​　3 Please report.
Tips:
　1. DT2W　At deep sleep, the idled CPU takes time to resume. If the taps are too close, it might not be recognized. Delay the duration between taps would give you better results.​　2. Built-in File Explorer　There is an built-in file explorer in AOSP. We can explore the files as well as installing apks.
Its in: Settings > Storage > Explore (under the storage you want. In case of Nexus 7, only the internal and OTG exist.)​Change log:
Code:
[COLOR="Blue"]2017/5/3[/COLOR]
　- Android-7.1.2_r11 (NHG47L)
[COLOR="Blue"]2017/4/9[/COLOR]
　- Android-7.1.2_r5 (N2G47J)
　- PerformanceControl: boot up settings fixed
　- Fix Wifi hotspot
　- Performance patches
[COLOR="Blue"]2017/3/8[/COLOR]
　- Android-7.1.1_r28 (N6F26U)
[COLOR="Blue"]2017/2/8[/COLOR]
　- Android-7.1.1_r21 (NOF26W)
[COLOR="Blue"]2017/1/6[/COLOR]
　- Android-7.1.1_r13 (N6F26Q)
　- Camera: Fix video recording
[COLOR="Blue"]2016/12/16[/COLOR]
　- Android-7.1.1_r6 (NMF26Q)
　- SEPolicy update
[COLOR="Blue"]2016/12/7[/COLOR]
　- Android-7.1.1_r4 (NMF26O)
　- Fix the Camera
[COLOR="Blue"]2016/11/11[/COLOR]
　- Android-7.1.0_r7 (NDE63X)
[COLOR="Blue"]2016/10/24[/COLOR]
　- Android-7.1.0_r4 (NDE36P)
　- Remove every recovery related resources
[COLOR="Blue"]2016/10/14[/COLOR]
　- Android-7.0.0_r14 (NBD90Z)
　- Shield the occasional crash in MTP Document provider
　- USB and Bluetooth Tethering support enabled
[COLOR="Blue"]2016/9/23[/COLOR]
　- Android-7.0.0_r6 (NRD90U)
　- latest DC kernel (Android-7.0 branch)
　- PerformanceControl: version 2.1.6
　- Find a way to fix the hwcomposer for video/audio playback, need to review later
　- A few sepolicy patches for Gapps and Mediaserver
　- SELinux: Enforcing
Downloads: :highfive:
　Hosts: Android File Host　MEGA　mirror: 百度网盘
　Note: I only tested it in TWRP 3.0.2.
　 　 　PerformanceControl app requires ROOT access.
　 　 　Root access can be obtained by the systemless SuperSU from @Chainfire.
　Gapps: opengapps (pico) and BaNKs Gapps for 7.0 are tested
Sources:
　Sources in github
Credits: :good:
　** Definitely the AOSP
　** The AndroidFielHost provide a FREE host with no limits and expiration.
　** All the developers who help the Nexus 7 (2012) development
　** All those who donate and/or help the developers. Giving us the resources and reason to carry on.
Donations: :angel:
{
"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"
}

Discussions
Anyone has any idea are welcome to post here
DT2W
Sometimes it won't wakeup after a long DEEP_SLEEP
When volume buttons are also enabled for wakeup. It won't work too. Seems there are situations "soft pwr button press" won't work.
Fail after reboot
Code:
Supported API: 3
E: unknown fs_type "f2fs" for /cache
E: Can't mount /cache/recovery/last_locale
Some of you might encounter the above message after reboot. I never encountered before but there is definitely something wrong.
@millosr found that it was the recovery being replaced. I think that make sense and I want to study why.
I looked into the source. In the original AOSP, an OTA might come with a recovery patch. Stated in the build/core/Makefile "boot.img + recovery-from-boot.p + recovery-resource.dat = recovery.img"
It would generate the "recovery.img by the above formula itself. Custom ROMs usually won't carry a recovery and this part was usual ignored.
There is a warning in TWRP before reboot. Some of you might not read clearly and slide to continue immediately. In that case, the above mentioned recovery.img will be generated and flashed to the /recovery partition. Everything seems normal but after reboot.
When the script kick in, it would execute the "new" recovery. As a normal recovery, it would load the fstab and try to mount the partitions. The current fstab version is API 3. Almost all ROMs (no matter how close to AOSP) would have F2FS support. When we open a typical fstab:
Code:
/dev/block/platform/sdhci-tegra.3/by-name/APP /system ext4 ro wait
/dev/block/platform/sdhci-tegra.3/by-name/CAC /cache f2fs noatime,nosuid,nodev,nodiratime,discard,inline_xattr,inline_data,inline_dentry wait,check
/dev/block/platform/sdhci-tegra.3/by-name/CAC /cache ext4 noatime,nosuid,nodev,nomblk_io_submit,journal_async_commit,errors=panic wait,check
Note that the second line is the declaration for the /cache in f2fs. Stock AOSP recovery doesn't support f2fs. That's why the above error shown. Since it fail to mount /cache, the last_locale is not loaded and recovery would hang.
How to recover?
Naturally, you have to flash TWRP again.
First of all, you need to boot into bootloader (fastboot mode)
Some init.xxx.rc might start adbd earlier and in this case "adb reboot bootloader" would do the job.
If adbd was not started before the hang, the command won't work. In this case you can only use the pwr+vol. down combination.
If it is still hanging, the buttons might not work. Press the power button continuously might lead to repeatedly reboot. It is better to make sure the device is OFF first.
1. Connect to a charger.
2. Press the power button until you see the charging image
3. Release the power button immediately.
4. After that, press the volume down button first, and then the power button.
It would go to the bootloader.
Note: /system is not really formatted during flashing. To make sure no residue left in /system, it is better to wipe the /system before flashing.
For ROM builders, there is a flag BOARD_USES_FULL_RECOVERY_IMAGE. Set it to true will stop the generation of recovery-resource.dat (in /system/etc) and break the above formula.

Does D2TW require the digitizer to remain permanently on? Trying to guage the impact of such a feature before I turn it on.

Nintonito said:
Does D2TW require the digitizer to remain permanently on? Trying to guage the impact of such a feature before I turn it on.
Click to expand...
Click to collapse
obviously.
---------- Post added at 09:52 AM ---------- Previous post was at 09:46 AM ----------
@daniel_hk good to see a separate thread. Will test this build this weekend as i am already on grouper.

：手指划线：

Thanks for bringing nougat to our beloved Nexus 7!!!
I just flashed but no matter which gapps I use, I can't make playstore and google play services installed.
Any hints?
Thanks.

ho0o0o11111 said:
Thanks for bringing nougat to our beloved Nexus 7!!!
I just flashed but no matter which gapps I use, I can't make playstore and google play services installed.
Any hints?
Thanks.
Click to expand...
Click to collapse
If you want anyone to help, you have to provide details.
The tested Gapps' are listed in OP. "No matter which gapps" ?
Can you tell us which one and version you actually tried?
What's your flashing procedures? etc.

daniel_hk said:
If you want anyone to help, you have to provide details.
The tested Gapps' are listed in OP. "No matter which gapps" ?
Can you tell us which one and version you actually tried?
What's your flashing procedures? etc.
Click to expand...
Click to collapse
Procedures (clean flash)
- rom
- gapps
- supersu
- reboot
- no playstore/play services have been installed after reboot
I used explorer to check and found that those gapps are installed (e.g. Vending.apk) but their sizes are all in 0kb.
the gapps I used were opengapps PICO and Banks. (I tried both. All after clean flash)
Finally I got playstore installed as follows
- flash rom/gapps/supersu
- reboot
- uninstall some system apps I don't need
- flash gapps again
then the playstore appears in app drawer. (And it works)
However, I have another big problem after reboot.
My device is now stuck in bootloop after splashscreen.
It just shows message as follows and I can't enter recovery/bootloader.
Supported API: 3
E: unknown fs_type "f2fs" for /cache
E: Can't mount /cache/recovery/last_locale
In the following page I found a solution "adb reboot bootloader" but I can't even enter bootloader/fastboot mode.
http://forum.xda-developers.com/nex...ip-linux-tegra-nv-3-4-bringup-t3128195/page46
still trying...
Any helps would be appreciated.
Thanks.

ho0o0o11111 said:
Procedures (clean flash)
- rom
- gapps
- supersu
- reboot
- no playstore/play services have been installed after reboot
I used explorer to check and found that those gapps are installed (e.g. Vending.apk) but their sizes are all in 0kb.
the gapps I used were opengapps PICO and Banks. (I tried both. All after clean flash)
Finally I got playstore installed as follows
- flash rom/gapps/supersu
- reboot
- uninstall some system apps I don't need
- flash gapps again
then the playstore appears in app drawer. (And it works)
However, I have another big problem after reboot.
My device is now stuck in bootloop after splashscreen.
It just shows message as follows and I can't enter recovery/bootloader.
Supported API: 3
E: unknown fs_type "f2fs" for /cache
E: Can't mount /cache/recovery/last_locale
In the following page I found a solution "adb reboot bootloader" but I can't even enter bootloader/fastboot mode.
http://forum.xda-developers.com/nex...ip-linux-tegra-nv-3-4-bringup-t3128195/page46
still trying...
Any helps would be appreciated.
Thanks.
Click to expand...
Click to collapse
I think you are not using the Official TWRP. There are similar reports having the same problem for other MM ROMs too.
You may try the Official TWRP 3.0.2 here (follow the link if you have a Tilapia) and flash everything again.
You might have corrupted your /cache and /data. It is better format them (to ext4 or f2fs) in the Official TWRP again.
Good luck!

daniel_hk said:
I think you are not using the Official TWRP. There are similar reports having the same problem for other MM ROMs too.
You may try the Official TWRP 3.0.2 here (follow the link if you have a Tilapia) and flash everything again.
You might have corrupted your /cache and /data. It is better format them (to ext4 or f2fs) in the Official TWRP again.
Good luck!
Click to expand...
Click to collapse
Thanks for your suggestion but the TWRP I used were downloaded from TWRP's official website, so I supposed it is official version.
I can't flash TWRP again as I am still struggling to enter bootloader mode.

ho0o0o11111 said:
Thanks for your suggestion but the TWRP I used were downloaded from TWRP's official website, so I supposed it is official version.
I can't flash TWRP again as I am still struggling to enter bootloader mode.
Click to expand...
Click to collapse
Which version? eariler version might have a wrong fstab which have issue on f2fs.
Make sure you got the latest version 3.0.2
You can't go to boot loader?
That means you press pwr+vol down and it won't reboot to bootloader?
That's strange.
"adb reboot bootloader" only work if the adbd is up. That means you can use "adb devices" to check the existance of your device.
You may try this:
1. connect to the charger
2. pressing the pwr button for > 8 seconds.
See if the tablet reboot. If yes, it would boot into charging mode. Pwr+vol down again would work.
If it doesn't reboot after you pressed say 20 seconds, you need to remove the battery.
Good luck!

@daniel_hk
Thanks for the new AOSP build Daniel. Nice work fixing the hardware decoder, my Netflix is now working and I was able to play one of my MP4 movies with BS Player in HW mode. I've been changing back and forth between your first AOSP 7 build and your DU 7 build with dirty flashes. With this build I decided to clean flash and at first things were very sluggish but settled down after a reboot and probably after Google finished whatever it does in the background. LOL Aside from a few occasional random force closes, it's running pretty well.
A couple of observations:
As mentioned, I did a clean install with this build. I'm using official TWRP 3.02 and installed the rom and 7.0 Open Gapps nano 20160915 at the same time and when it booted up for the first time, there were no gapps installed. I powered down and then went back into TWRP and reflashed the gapps, this time they were there upon reboot. Surprisingly, I didn't have to set permissions for Google Play or Play Store, as they were already correctly set??? I did run into a snag when trying to download apps from PS, clearing the data for the download manager app solved that problem for me.
I installed a camera app (HD Camera) from Play Store and it works but when I use my phone's camera, it reminds me how crappy the N7 camera is. LOL
After setting things up, I wanted to try phhsuperuser (no Magisk) to root and it went fine. All of my apps that require root worked...except Titanium Backup. I tried uninstalling/reinstalling both phhsuperuser and Titanium but couldn't get it to work. I rely on Titanium quite a bit, so I flashed Supersu 2.78 and all's well.
Thanks again.
Mike T

Do games work on this rom?

Hi,
This is the best 7.0 ROM so far !!!
Smooth, video HW decoding is working, games work perfect.
As webdroidmt said I also had to reflash GAPPS to have GAPPS installed and i had to give proper permissions on Google Play service to stop seeing the "google play service stop" message.
All Apps/games that i installed are working properly.
Thanks Daniel_hk for your work

Many thanks Works like a charm !
Is SEpolicy restrictive in your build? (I cannot see it from Settings -> about tablet)
.
Can you post your manifest on Your Github for easier building ?

Hi, currently testing your ROM, looks awesome!
When Browsing the web with Chrome, loads and loads of SELinux denials, mostly when the page loads:
Code:
09-26 13:34:20.990 4424 4424 W Thread-4: type=1400 audit(0.0:174): avc: denied { ioctl } for path="socket:[45348]" dev="sockfs" ino=45348 ioctlcmd=8b1b scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:r:untrusted_app:s0:c512,c768 tclass=udp_socket permissive=0
This message times * 100 for every page load.

paasoares said:
Hi,
This is the best 7.0 ROM so far !!!
Smooth, video HW decoding is working, games work perfect.
As webdroidmt said I also had to reflash GAPPS to have GAPPS installed and i had to give proper permissions on Google Play service to stop seeing the "google play service stop" message.
All Apps/games that i installed are working properly.
Thanks Daniel_hk for your work
Click to expand...
Click to collapse
In any case, it's a good practice to read the console after flash anything. There might already be essential messages which not necessarily in red.
I also experience SuperSU need to flash again. I just found out something that might help. Seems SuperSU would use the cache to start a checking process in the next boot. I don't know if it would help gapps too.
1. Try factory reset before flashing.
2. Flash ROM+Gapps+SuperSU
3. After that don't do wipe cache/d-cahce again. (factory reset already include this action)
Good luck!
3yan said:
Many thanks Works like a charm !
Is SEpolicy restrictive in your build? (I cannot see it from Settings -> about tablet)
.
Can you post your manifest on Your Github for easier building ?
Click to expand...
Click to collapse
I think you meant "Enforcing". Yes, it is enforcing. Only some Custom ROM would show this in About but not AOSP.
There is a shell command "getenforce" which you can check the SEPolicy status.
If you read the OP, you would know its an AOSP without any mod/tweak, just porting. You can get the manifest and all the helps in https://source.android.com.
Good luck!
fat-lobyte said:
Hi, currently testing your ROM, looks awesome!
When Browsing the web with Chrome, loads and loads of SELinux denials, mostly when the page loads:
Code:
09-26 13:34:20.990 4424 4424 W Thread-4: type=1400 audit(0.0:174): avc: denied { ioctl } for path="socket:[45348]" dev="sockfs" ino=45348 ioctlcmd=8b1b scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:r:untrusted_app:s0:c512,c768 tclass=udp_socket permissive=0
This message times * 100 for every page load.
Click to expand...
Click to collapse
Chrome has many versions and it should not be an untrusted app. I'm testing the CarbonROM which has a bloated Chrome and being treated as isolated app. It might take time for those UID's being properly handled.
I already included some extra permissions which would be include in my later builds.
Anyway, we would encounter denials more often in apps. That's what newer Android intent to do.

Code:
09-26 19:14:02.119 189 344 D hwcomposer: hotplug_thread: processing control fd
09-26 19:14:02.119 189 344 I hwcomposer: hotplug: connected = 0
09-26 19:14:03.469 503 579 W AlarmManager: Unrecognized alarm listener [email protected]
09-26 19:14:03.469 503 579 E WifiScanner: listener cannot be found
09-26 19:14:03.478 677 677 E wpa_supplicant: wlan0: Failed to schedule PNO
09-26 19:14:03.481 503 581 E SupplicantWifiScannerImpl: PNO state change to true failed
09-26 19:14:03.481 503 581 E SupplicantWifiScannerImpl: Failed to start PNO scan
09-26 19:14:03.484 503 581 W SupplicantWifiScannerImpl: No PNO scan running
09-26 19:14:03.486 503 579 E WifiConnectivityManager: PnoScanListener onFailure: reason: -1 description: pno scan failed
This is repeated every 5 minutes during deep sleep. I'm not an expert, but this probably doesn't help with battery drain
I'm also having some touch sensitivity issues when coming out of deep sleep or off the charger. I have to do some more testing, then I will have more details.

I wanted to try this 'Sept 23' ROM as it should play video OK: in the end I got it to work, and I can now indeed play video in some video based apps that did not work before. I used the older DU ROM and also the nAOSP ROM of millosr. There video does not work yet.
But with this Sept23 ROM I had a fight with Gapps to get it to work... First the Gapps I normally use failed to install in TWRP. At least, that is what I think I saw: the progress bar suddenly jumps ahead as if the install process was broken off somehow. So I again clean wiped all and now used opengaps-pico. That installed fine, but on first boot, no gapps. So I again installed opengapps and now finally I had working playstore. Strange, I never ran into something like this before (I am mostly active on Xperia S with nAOSP).
But the story ends well, as my video now works: great job !

fat-lobyte said:
Code:
09-26 19:14:02.119 189 344 D hwcomposer: hotplug_thread: processing control fd
09-26 19:14:02.119 189 344 I hwcomposer: hotplug: connected = 0
09-26 19:14:03.469 503 579 W AlarmManager: Unrecognized alarm listener [email protected]
09-26 19:14:03.469 503 579 E WifiScanner: listener cannot be found
09-26 19:14:03.478 677 677 E wpa_supplicant: wlan0: Failed to schedule PNO
09-26 19:14:03.481 503 581 E SupplicantWifiScannerImpl: PNO state change to true failed
09-26 19:14:03.481 503 581 E SupplicantWifiScannerImpl: Failed to start PNO scan
09-26 19:14:03.484 503 581 W SupplicantWifiScannerImpl: No PNO scan running
09-26 19:14:03.486 503 579 E WifiConnectivityManager: PnoScanListener onFailure: reason: -1 description: pno scan failed
This is repeated every 5 minutes during deep sleep. I'm not an expert, but this probably doesn't help with battery drain
I'm also having some touch sensitivity issues when coming out of deep sleep or off the charger. I have to do some more testing, then I will have more details.
Click to expand...
Click to collapse
Did you set "keep wi-fi on during deep sleep" to NEVER?
My tablet drain 5% during this night (about 8 hours), so i guess this is normal/acceptable

SailfishOS 3 for Photon Q and siblings

Code:
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it!
SailfishOS 3 for Photon Q
Continuation from 2.0 thread to keep most important information in first post. Thanks to vevgeniev for initial port, without it I would never buy Photon Q.
Repo with my apps is added to image. Packages can by installed via terminal:
Code:
devel-su zypper in "package name"
Images
{
"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"
}
Click to expand...
Click to collapse
Installation
Download and flash cm-11-20150626-SNAPSHOT-XNG3CAO1L8-moto_msm8960_jbbl.zip via twrp-3.0.2-0-asanti_c.img according to ordinary cm instruction. Use ext4 filesystem for /data partition. Boot to android and make sure everything works.
Download SailfishOS 4 image (open browser in private mode if onedrive ask you to login) and flash it over cyanogenmod. It's compressed tarball so installation may take even 10 minutes.
OTA
Read about Stop Releases and make backup using TWRP
Code:
/usr/share/sfos-moto_msm8960_jbbl-adaptation/upgrade.sh
# after reboot execute pkcon refresh to update all repositories
For any issues with upgrade.sh script download more up-to-date version, add --verbose argument or execute commands from real-upgrade.sh manually: https://build.sailfishos.org/packag...bl:4.4.0.68/sfos-moto_msm8960_jbbl-adaptation
At first boot tracker might slow down phone and eat a lot of storage. If it's too resource hungry move your media files out of device or create .nomedia empty file to exclude particular directory from tracker. Then force reset it:
Code:
tracker reset --hard
Custom Bootlogo
vevgeniev created a custom bootlogo:
Instruction how to use it
Known issues
Half screen mirror glitch occurs sometimes. Blank/unblank display fixes it
Sometimes removing files does not have any effect, i.e. free space doesn't increase and sdcard can't be unmounted. Could be easily triggered by mtp or dd usage. For sdcard access use FileZilla (SFTP).
QProcess:startDetached can hang randomly. Workaround added to fingerterm. Looks like it's bug in Qt and it is not photon q specific: https://together.jolla.com/question/202337/bug-fingerterm-terminal-freezes-after-opening-new-window
There are no 2.XG, 3.XG network indicators.
glReadPixels() return empty content in some cases. This means no screen recording, screenshots and thumbnails in browser. Workaround for screenshots added to lipstick.
All bugs at first boot are features.
FAQ
Q: How to run apk?
A: It's not android, you can't
Q: Can I switch between hardware keyboard layouts?
A: Default xkb layout switch shortcut: "shift + sym". You need to also set second keyboard layout:
dconf write /desktop/lipstick-jolla-home/layout "'us,ru'"
Click to expand...
Click to collapse
In newer releases layouts can be enabled in settings and switched via "shift + space"
Tips
Fast way to restart lipstick:
shift + tab + k
Alt + Tab like switching (if you have sailfishos-alttab-patch installed):
OK + tab
To disable volume media keys:
dconf write /apps/photonq-helper/mediaKeysEnabled 0
batt_health can cause reported battery capacity decrease which I am not sure works correctly at least on my aging battery. It's disabled since 3.3.0 in 2 places in /init.target.rc. Therefore btry will not report Aged Capacity anymore.
To use h264 (hardware accelerated) decoder in youtube set in about:config media.mediasource.webm.enabled to false
user name is still 'nemo' instead 'defaultuser' even for latest releases
Changelog
4.4.0.68
* Partially usable browser. Javascript doesn't cause crash on almost all sites like in 4.0-4.3 sfos. Tabs in landscape mode are unusable.
* Using browser probably breaks video encoding/decoding ('vid_dec_open() max number of clientslimit reached' in dmesg). Killing minimediaservice/browser usually helps.
* Disabled sailjail, and enabled start up boosters back.
* Few general sfos bugs more (see patchmanager catalogue for my patches)
4.3.0.15 - No for daily use, just required Stop Release
4.2.0.21 - No for daily use, just required Stop Release
4.1.0.24 - No for daily use, just required Stop Release
4.0.1.48
Broken browser
3.4.0.24 - Latest usable version
Fix memory leak when taking screenshot
Add workaround for remembering wlan state after reboot in airplane mode
Media keys works only in locked screen
3.3.0.16
NFC pn544 plugin added
batt_health disabled in /init.target.rc
glibc 2.30, gcc 8.3
3.1.0.12
kernel: hold volume up/down to select next/previous song
droid-hal-init: disable mpdecision due to constant cpu usage
3.0.3.9
Patch glibc for 3.0 kernel
3.0.2.8
Handle system and data partition automatically
New methods to wake up sensors
3.0.1.11
kernel: Fix crashes caused by new firewall rules
kernel: Experimental multi LUNs support
droidmedia: Fix random audio/video fail in browser
usb-moded: Mass storage was dropped in upstream. Use patched one
Click to expand...
Click to collapse
XDA:DevDB Information
SailfishOS 3 for Photon Q, ROM for the Motorola Photon Q 4G LTE
Contributors
elros34, vevgeniev
Source Code: https://github.com/elros34?utf8=✓&tab=repositories&q=msm8960&type=&language=
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.0.x
Based On: CyanogenMod
Version Information
Status: Alpha
Created 2018-11-23
Last Updated 2019-08-20

Thanks for maintaining this for our devices @elros34
I have been meaning to try Sailfish for some time on my RAZR HD (xt926) and i finally got around to it the other day only to find that it wont boot up.
As per the 2.0 thread i can flash CM11 and that will boot and work fine but once i flash Sailfish over the top it wont boot past the bootloader unlocked logo. I have tried both the xt907 and photonq zips but neither will boot.
The xt907 zip did shown some signs of something happening since the led would light up either orange or white but after leaving it for 45 mins with no other signs of life i gave up on it.
Please find attached a list of my device drivers using the following command:
Code:
ls -alR /dev
Are there any chances of this running on my xt926 ?

Thanks, so it has xt907 like partition table, you can't use photon q image. LED glowing means system is booting.
Boot to TWRP then:
Code:
rm /data/.stowaways/sailfishos/init_disable_telnet
Now reboot, connect phone to usb and telnet to it:
Code:
telnet 192.168.2.15 2323
In windows you can use putty but it's hard to copy logs from it.
Then wait a while so logs are complete and run:
Code:
dmesg
journalctl --no-page
logcat
evdev_trace -I

elros34 said:
Thanks, so it has xt907 like partition table, you can't use photon q image. LED glowing means system is booting.
Boot to TWRP then:
Code:
rm /data/.stowaways/sailfishos/init_disable_telnet
Now reboot, connect phone to usb and telnet to it:
Code:
telnet 192.168.2.15 2323
In windows you can use putty but it's hard to copy logs from it.
Then wait a while so logs are complete and run:
Code:
dmesg
journalctl --no-page
logcat
evdev_trace -I
Click to expand...
Click to collapse
Thanks @elros34
Please find attached the various logs from my xt926.
Note i'm still running Sailfish 2.1.3.7, i figured it would be easier to start with that but if needed i can re-run these on 3.0.0.8
I have no idea what most of it means for the most part but a few errors did stand out to me in particular
Code:
Dec 12 20:20:16 Sailfish systemd[1407]: Failed to start The lipstick UI.
Could this possibly explain why its not booting any further?

Lipstick fails to start because xt926 use different touchscreen driver. Change "/dev/touchscreen" to "/dev/input/event1" in /var/lib/environment/compositor/droid-hal-device.conf
Also paste output of:
Code:
udevadm info -a /dev/input/event1

elros34 said:
Lipstick fails to start because xt926 use different touchscreen driver. Change "/dev/touchscreen" to "/dev/input/event1" in /var/lib/environment/compositor/droid-hal-device.conf
Also paste output of:
Code:
udevadm info -a /dev/input/event1
Click to expand...
Click to collapse
Thanks @elros34 its working now after changing the touchscreen driver boots up fine. I'm not seeing any immediate issues but will see how i get on with it. First impressions are very good, a really nice os i'm actually surprised at how fast and fluid it is.
Here is the output of
Code:
udevadm info -a /dev/input/event1
Code:
sh-3.2# udevadm info -a /dev/input/event1
Udevadm info starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.
looking at device '/devices/i2c-3/3-0048/input/input1/event1':
KERNEL=="event1"
SUBSYSTEM=="input"
DRIVER==""
looking at parent device '/devices/i2c-3/3-0048/input/input1':
KERNELS=="input1"
SUBSYSTEMS=="input"
DRIVERS==""
ATTRS{name}=="melfas-ts"
ATTRS{phys}=="3-0048/input0"
ATTRS{properties}=="2"
ATTRS{uniq}==""
looking at parent device '/devices/i2c-3/3-0048':
KERNELS=="3-0048"
SUBSYSTEMS=="i2c"
DRIVERS=="melfas-ts"
ATTRS{drv_debug}=="Debug Setting: 0"
ATTRS{drv_reset}=="Reset: HIGH"
ATTRS{hw_irqstat}=="Interrupt line is HIGH."
ATTRS{ic_reflash}=="No firmware loading in progress."
ATTRS{irq_enabled}=="Interrupt: 1"
ATTRS{latency_debug}=="Latency Debug Setting: 0"
ATTRS{latency_times}==""
ATTRS{latency_values}=="Touch Latency Time: Average 0uS, High 0uS,0 interrupts of 0 were slow"
ATTRS{name}=="melfas-ts"
looking at parent device '/devices/i2c-3':
KERNELS=="i2c-3"
SUBSYSTEMS=="i2c"
DRIVERS==""
ATTRS{name}=="QUP I2C adapter"
I'll also see if i can convert some of the other xt925 and xt926 users for testing.

Absolutely love this - haven't had a single problem yet. Thank you so much elros34.

Could somebody check what "getprop ro.product.device" returns for xt926 or xt907 with sailfish installed?

mounting /dev/mmcblk0p39 on /data failes
Hi,
at first i would like to thank you for building SFOS3 for the Photon Q series, i bought another XT907 to finally get SF running on this pretty nice and tiny handset.
As @drkdeath5000 i stuck at the bootloader unlocked screen but with another problem as the touchscreen driver for his XT926.
I think it's a problem with the partition table here the error from /init.log
mount: mounting /dev/mmcblk0p39 on /data failed: No such file or directory
I followed the installation instructions you provided and flashed cm11, which is booting without issues. I already tried it with and without wiping dalvik/cache, with and without booting to cm11 first. So i would really appreciate your help. If i can provide some more detail just tell me.
Best regards
André

rkdeath5000 get further because he used old xt907 image, you can't use photon q image in XT907.
I have tried to support all devices in one image. I even prepared untested script to update kernel but need a nice way to distingnues between devices. No feedback so far.
Few days ago I came up with different an idea how to auto detect correct partitions in all devices but so far I am struggling with some serious issue in 3.0.2 so I am not sure when I will release it.

elros34 said:
Could somebody check what "getprop ro.product.device" returns for xt926 or xt907 with sailfish installed?
Click to expand...
Click to collapse
On my XT907 it returns scorpion_mini

Thank you for your fast response,
as you recommended Version Alpha3 is running but of course i would like to run SFOS3 So i would like to help you in any way possible.
Best regards
André

If you could test whether this image works (boots without issue and touchscreen works) then it would be great. This is image I just built with new method to detect correct partitions but without all needed patches for middleware so other bugs are not important for now.

Thank you so much! I can hardly tell you how happy you made me I always wanted i tiny handset running on SFOS and finally after i already had given up on that your rom make it happen.
I just started some basic testing on it, as i want to wait for the screen protector before starting to really use it so i'll give you a feedback on the rom later.

3.0.2.8 Released as OTA and new image probably for all moto_msm8960_jbbl devices.
Also I created new patch for Alt+Tab (OK + Tab key) like switching between windows. It's added to my obs repo.

So far the new version alpha9 installs without issues on the XT907. Right now i have just one problem, as in version alpha8 I'm not able to send text messages (SMS). I tried different sim cards from two different networks, so i think it's a problem within the ROM. How could i help you on this? Maybe collecting some logs?

What about Alpha3 or android? To boot android you don't have to flash whole system, just boot cm11 kernel via fastboot. Have you tried to set "Prefer 3G" in cellular settings?
To get most basic logs, reboot phone and try to send sms, then:
Code:
dmesg
journalctl --no-page
logcat -b radio
If it's something more serious then you will need to follow:
https://jolla.zendesk.com/hc/en-us/articles/203761078-How-to-collect-SMS-logs-

Thanks so much for 3.0.2.8 - works great. Really hope you're able to give us a 3.0.3 with the updated browser.
Don't know if you have any interest/knowledge on Maemo Leste or PMOS, but since you're the most knowledgeable person on the Photon Q, just wondered if you could hazzard a guess as to how possible it might be to get them working on this device further down the line?
Thanks again.

Yes, updated browser is tempting so I will definitely bring 3.0.3 when it will be available for ported devices.
Unfortunately I have never ported Leste or Postmarketos so I have limited knowledge here.
With Photon there are several issue like: no sim without modification and no flex cable to buy. Also we are stuck with android drivers and ancient 3.0 kernel with no chance for upstream. It means to run anything (in usable form) other than android we need libhybris. I think there are better devices with more active developers for these systems: droid 4 - have ongoing upstream efforts, Fxtec pro1 for sure will have 4.x or even 5.x kernel. That's why you will not find photon in actively supported devices in postmarketos or leste site.
- Leste use hildon-desktop (x window manager) so it would be probably not trivial to get libhybris based ui acceleration if it's possible at all. Is that os even daily usable?
- After a quick read of Postmarketos wiki looks like it support wayland based compositor like weston so it is a good sign. I was able to run libhybris accelerated weston in ubuntu chroot in sailfish. It has some touch issues but it may be because I run it nested in lipstick. From what I understand if device doesn't have upstream kernel then postmarketos requires ported halium and lxc containers. That might be not possible because of 3.0 kernel but you will never know until you try.
Take everything I said with a grain of salt and start porting. For halium you will probably need newer base than cm11. There are few important commits which are needed otherwise kernel will not work.

SMS issue could be general ofono bug: https://together.jolla.com/question...installing-3028/?answer=205366#post-id-205366
Jolla is focused on android8 base so older bases are neglected. Upstream libhybris is also broken for hybris-11 base.