{
"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)
Related
Discontinuation Notice + Source Opened!
This project is now discontinued, as I have moved on to Android 4.X (ICS) which has perfect built-in RTL support.
I will still provide basic support as much as I can, but if your device has it, I recommend you move on to ICS as well.
If you wish to continue working on this project and improving, you have my blessing (as long as you credit me, of course).
Source code is available here, but be-ware: it's an undocumented, unorganized mess.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Android RTL Auto-Patcher
Version 1.5
The Problem
It's a well known fact that while Android has Hebrew and Arabic fonts, it has a problem with Right-To-Left alignment. The problem: It doesn't exist.
Sure, MOST programs display text correctly, but mix text and numbers in the same line and you'll get reverse numbers (123 appears as 321), and in SOME Google apps (like Gmail and Maps) the words themselves are reverse (so 'apple' appears as 'elppa').
The Old Solution
There is a solution for this, however you have to create a separate patch for every build, because the patch changes files in the build's framework. It's a relatively easy process, but for people who change builds constantly, it can get tiresome.
This Program
This program detects if a build is compatible with the patch, and if so - creates it almost automatically and install it back to the phone. A process that took about 10 minutes to complete before and required some knowhow, now takes only seconds and requires almost no prior experience!
{
"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"
}
ProTools
The ProTools are a collection of tools that will allow you to patch ROMs manually either directly to ZIP files, to the phone, or to framework files. It will also allow you to push, pull, extract and manipulate files to and from ROMs of all kinds, with great flexibility and ease!
Compatibility
This program is intended for use with custom DEODEXED roms of Android versions 2.1 and above. The program will inform you if your build is not deodexed.
The program will allow you to either push the fix directly to the device or flash via recovery.
WARNING: Some 'squashedFS' builds have been reported not to be compatible, and the program can not - at the moment - detect those!
Warnings
This program is in Beta stage!
Many features have not been thoroughly tested and error handling is far from perfect.
It may give some errors, crash or stall - at which point I ask that you please send me your log.txt (to find it, click 'About' and then 'Locate Log') or as an upload in this thread.
I do request - however - that you try to be as specific as possible regarding your build, your computer, and what caused the problem.
Also, if you include the log here, please enclose it in 'code' tags.
Requirements
You MUST have Microsoft .Net Framework 4 installed for this to work.
You will also need the latest Java Runtime Environment
You must also have the ADB drivers already installed:
In Windows Vista/7, just connect the phone and let Windows Update do it's thing.
In Windows XP, you need to manually install the drivers available here.
ADB itself comes with the program, so you don't need that.
How to use
If available, boot into recovery (recommended for non-rooted devices!)
Connect your phone to USB and make sure the computer recognizes it
Run the program, and select 'Test Connection'
After connection has been made, if the build is compatible - select the correct Sense version. The program WILL attempt to auto-detect, but it's not 100% reliable, so please confirm that the program detected correctly
Select distribution method:
Push to Device (Recommended) - does simply that, the program will attempt to automatically patch the phone for you.
Create ZIP - creates a ZIP file that's flashable through Recovery (Clockwork Recovery Mod). Will also offer you to save the ZIP on the SD card (doesn't even require mounting USB).
Show File - will just show you the patched 'framework.jar' so you can do whatever you want with it.
Select any additional options you might be interested in (Gingerbread keyboard, for example - is a fixed Gingerbread keyboard with fixed Hebrew RTL that is compatible with the patch the program installs. It should work on 2.2 devices as well, and replaces the stock Android keyboard).
GO GO GO!
Reporting bugs
Please be sure to provide the name and type of your build when giving feedback or reporting bugs. For better bug-squashing, please also provide your log.txt file, which you will find in the application's directory.
Also, even if you experienced no bugs, your logs will be appreciated.
Finally, if you put the the log content in your post, PLEASE encode it with 'code' tags.
If you have any additional non-bug-related questions, feel free to ask them in this thread. I will do my best to improve this program as time goes by.
Thank you, and good luck!
Download
Always available here:
Changelog, Known Issues and Planned Features
Changelog
1.5 - 14/08/2011
Advanced build numbers to 1.5 due to massive advances in the program.
Added global error handling - might not solve ALL problems, but will hopefully help avoid unlogged crashes.
When "Install Gingerbread Keyboard" and "Create Zip" are both selected, it will now also install the keyboard on the Zip.
The program will now also try to mount sd-ext in addition to system before patching (as will the flashable Zip).
When patching fails, the program will offer you to save the patched file to your computer for use with ProTools.
In the 'About' window, added the option to find the log file on your computer (for easier error reports).
Other minor undocumented improvements.
Completely overhauled the ProTools:
Offline Patching: Allows patching ROM Zips or 'framework.jar' files directly.
Manual Operations: Pretty much what ProTools was before, except with an easier straight-forward interface and with the option to operate on a ROM Zip file, from your phone, or directly from a 'framework.jar' file.
Added the option to manually push or pull anything to or from anywhere (with specific buttons for 'framework.jar', 'framework-res.apk' (for theming) and 'build.prop'.
Added the option to manually patch the Keyboard to the phone or the a ROM Zip.
1.1.2 - 20/07/2011 - minor update
Improved Sense 3.0 Detection
Updated build detection strings
1.1.0 - 14/06/2011
Fixed critical interface bug that caused the operation compelte / restart prompt not to appear if 'Push' was selected.
1.1.0 - 14/06/2011
Removed support for SD/SDRAM based builds
Instead, created three distribution methods: Push file, Create flashable zip or just Display file
Flashable zip will be flashable via recovery, and will attempt to push itself to the device's SD card.
Version 1.0.0 Beta
Build Detection:
Improved build properties detection
Vastly improved Sense detection mechanism
Sense versions now distinct by Sense version
Added Sense 2.1 (Gingerbread) support
'Pro Tools' (Beta) - Every single function of the patcher can now be called on seperately and manually.
Changed versioning scheme. Version 1.0.0 to be assigned.
Updated core framework files (fixed a lot of stability issues in Sense2.0 builds)
Planned Features
I plan to seriously improve the RTL fix itself in the near future, but since I lack the knowledge to do so myself, I'm waiting for some new methods currently under development by the excellent devs at iAndroid.co.il to be released.
I do plan to release to program's source code eventually, it's just such a mess at this point that I'm more ashamed of it than anything else.
I also plan to include a logcat monitor. Because the patch causes the phone to rebuild dalvik cache, first boot after patching often takes a VERY LONG time, and some users wrongfully assume their phone is frozen. I plan to include a logcat monitor that will hopefully know to differentiate between bootloops, errors, and dalvik rebuilding, so users can tell if their phone is actually frozen or just working. If this works, I might release this as an actual separate program.
Known Issues
Build 1.1.0 - If 'Push' is selected, when patching process finishes, no message is displayed and the program doesn't prompt to restart. - fixed in 1.1.1
There is hardly any error handling in the ProTools section. If they are called with no device available, it MAY freeze/crash the program. Will be fixed in upcoming release.
Fixes for Squashed filesystem roms do not work! Mostly.
Error handling is STILL utter ****e, may give unexpected errors (or not at all and just fail altogether).
If HTC Sync is installed and active, stuff may go nuts all around (as of 0.0.5 this is detected by the program and warns user).
Credits
Program and Graphics created by Elad Avron using Visual Studio 2010 Express.
ZIP Functions created by Elad Avron using free libraries from the IC#Code group, available at http://www.icsharpcode.net/opensource/sharpziplib/
Special thanks:
From HTCAddicts.com: Ronenpg, Ohect.
From XDA-Developers.com: TheAgent1982, silverbluem, mdeejay and the entire HD2 dev crew
From iAndroid.co.il: Classicaldude (Original fix, the hero of RTL!), Dudyk (Original fix), rasmux (Modified fix), Liavk1 (partial SenseHD fix), Avicohh (Gingerbread Keyboard), N1Man (RTL fix for Gingerbread Keyboard).
Keyboard fix by Avicohh and N1Man (from iAndoird.co.il)
If it will work man i'll give you a real big THANKS!
Just tried it V 001 , successfully connected + fetched framework+modified then pushed classes back....
log attached
PC - Win7 + net 4
LeoAndroid - Desire Z ....
Device restarted, passed the first splash (hTC) screen, took very long on the animation one, then started !
Changes :
1-No right side line alignement..
2-Numbers are still wrongly placed..
Tested and it workes!
Got an error in middle of the prosses but in the end it did what it was supposed to do.
Sent from my HTC HD2 using XDA App
congratulation
Congratz of your new Project!
I will give it a shot as soon as i can
my teset here ..
this is my test in the log file attached
thx
I appreciate your efforts
reverse numbers problem still exits
big thanks
Voffchik said:
Tested and it workes!
Got an error in middle of the prosses but in the end it did what it was supposed to do.
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
Thanks
Can you send me your log.txt?
I'd like to see what the error was.
Sup3r said:
I appreciate your efforts
reverse numbers problem still exits
big thanks
Click to expand...
Click to collapse
Can I get build type and log file please?
Thank you
jaguaralani said:
Just tried it V 001 , successfully connected + fetched framework+modified then pushed classes back....
log attached
PC - Win7 + net 4
LeoAndroid - Desire Z ....
Device restarted, passed the first splash (hTC) screen, took very long on the animation one, then started !
Changes :
1-No right side line alignement..
2-Numbers are still wrongly placed..
Click to expand...
Click to collapse
The log indicates that you did everything right and experienced no errors, so there are two things I'd like you to try:
In the 'Toolbox' dir in the app dir, the leftover files from the creation process are left. Try pushing framework.jar manually to the device.
If that doesn't work, try putting 'classes_new.dex' in 'framework.jar', renaming it to 'classes.dex' (thus replacing the old one), and repeat step 1.
If that doesn't work something went wrong in the patching process itself, i.e. my source files aren't good for your build (they should be), the compression failed, or any step in between. Let me know if the leftover framework.jar and classes_new.dex solve the problem, and we'll try to isolate the problem from there.
Thank you all for helping
Thank you
Thank you very much for your great work.
The alignment works great for Arabic, but the thing with Arabic is that letters need to be connected with each other when they are in one word. From what I gather, this means needing to change stuff in libskia.so and libwebcore.so (both in /system/lib/).
For more info, you can check out the efforts to add Arabic support for many Android devices at http://ardoid.com/
NSider said:
The alignment works great for Arabic, but the thing with Arabic is that letters need to be connected with each other when they are in one word. From what I gather, this means needing to change stuff in libskia.so and libwebcore.so (both in /system/lib/).
For more info, you can check out the efforts to add Arabic support for many Android devices at http://ardoid.com/
Click to expand...
Click to collapse
Yes, I understand it's a problem with a lot of software, not only Android.
I will try to implement patching of Arabic characters in the future, once the program has a more solid base.
this is my log
my build is : MDJ's gingerbread CyanogenMod 7 v. 2.1 [A2SD+][GRH78][RMNET][Kernel: MDJ S10.2 OC
wating the Arabic characters fix
thanks :0
Ambious said:
Thanks
Can you send me your log.txt?
I'd like to see what the error was.
Click to expand...
Click to collapse
I sent it yesterday via PM
I sent the log file + screenshot
U said u'll look in to it
Sent from my HTC HD2 using XDA App
Voffchik said:
I sent it yesterday via PM
I sent the log file + screenshot
U said u'll look in to it
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
Right, sorry, my bad
I worked around your reported error in v.0.0.2, it was a little oversight I had in interface design.
Thank you for the report
Sent from my Android HTC HD2 using XDA App
Sup3r said:
my build is : MDJ's gingerbread CyanogenMod 7 v. 2.1 [A2SD+][GRH78][RMNET][Kernel: MDJ S10.2 OC
wating the Arabic characters fix
thanks :0
Click to expand...
Click to collapse
Thank you for the log.
From the log it seems like there were no errors and that everything went as planned. I'm using the same build as you, so I know it's compatible.
What I'd like you to try, if it's not too much hassle, is this:
In the 'toolbox' dir in the app dir, there are leftover files from the process. Push 'frameowkr.jar' to your device's "/system/framework/" using:
Code:
adb push framework.jar /system/framework/
and reboot.
If that solves it, the issue was with the push command (I currently have no method to actually detect if it was successful or not, I hope to fix that in future version).
If even that doesn't solve it, open 'framework.jar' using any zip/rar program, delete 'classes.dex' from it, insert 'classes_new.dex' (from the toolbox dir) into the 'framework.jar' file, and rename to 'classes.dex'. Push to the device, restart, and try again.
If you don't mind doing those things, it would help me greatly to detect where the patching process failed.
Thank you so much, and I promise to include Arabic fix as soon as the program structure is solid enough!
Tried V 002
PC - Win7 + net 4
LeoAndroid - Desire Z ....
Log attached
changes
Nothing
jaguaralani said:
Tried V 002
PC - Win7 + net 4
LeoAndroid - Desire Z ....
Log attached
changes
Nothing
Click to expand...
Click to collapse
Yeah, well, v002 changes nothing in the process, only the interface.
I'd like you to try, if not too much hassle - to push the framework file manually and reboot.
If that doesn't work, try to put 'classes_new.dex' into 'framework.jar' and rename it to 'classes.dex' and push framework.jar again.
If any of that works then I can narrow down the issue.
On another note, I got reports from other people using DesireZ that the process worked for them, so I know it's compatible, it's just a localized issue.
This doesn't specifically belong to NAND development.
Moved.
(Regardless of that, it's a wonderful project).
This thread is outdate.New thread is here: http://forum.xda-developers.com/showthread.php?t=1239778
======================================================================================================
[Real DEV][ROM][Port][Updated: 19-Aug-2011]GB MIUI for Milestone2 All-in-one update.zip Thanks to r2beta0 !
Now dangpzanco has set up a project base on MIUI/CM7 on github, anyone who interst in it can contact with him or come here !.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------
If you have any problem in using CM7/MIUI, before question, you may take a look at this thread.
Im not a DEV, so any tutorial and help is very welcomed. If someone can develop for it, that would be very thankful !
Any defy CM7 based/cooked/moded ROM include MIUI can use this method to boot.
Thanks to dangpzanco and r2beta0 for their great effort. And walter79 for the great idea.
Known compatible kernels：
It seems only 2.6.32.9-********[email protected]**lnxdroid**#* series kernels are supported.
2.2.2-CH include 2.10.0 / 2.6.0 / 2.5.0
2.2.1-CH 1.10.0 / 0.24.0
Known incompatible kernels：
2.3.4-CH leak
2.2.2-UK/DE,AT,CH/Argentina/HongKong/Italy
2.2.1-Mexico
2.2-Brazil/France/UK/Australia
Unknown kernels:
2.2.2-France
2.2.1-Argentina
2.2-Argentina/DE, AT, CH
This is my nandroid backup with some fix but not all, you could choose one or not.
[Recommend!]1. Based on MIUI 1.8.12 moded by Wajk, download: http://www.megaupload.com/?d=1RF2A3JC
2. Based on a cooked CM7 ROM(thanks to VIPFXY): http://www.megaupload.com/?d=NOWVXJAK
3. Based on cm7-110813-2132-NIGHTLY-Jordan.zip http://www.megaupload.com/?d=17RERZSM
Patch for CM7/MIUI ( It should work on all defy CM7/MIUI based/cooked/moded ROM ):
This patch fix the following：
1.GSM problem, you may still need to use baseband switcher to change your baseband (If you still have no signal, take a look at this,theoretically it 100% works! http://forum.xda-developers.com/showthread.php?t=1182050 )
Thanks to i7ovehope and dangpzanco
2.Keyboard mapping issue ( except ALT-LOCK, however you can double press ALT instead ) Thanks to 19900828xy
3.fix CWM issues related to /data Thanks to r2beta0
4.When you are charing, you will have your LED turn yellow to tell you, instead of nothing (Charger light still not work)
5. Gravity-sensor/light-sensor are working again Thanks to walter79 and dangpzanco
6. GPS should works
7. compass should works
And the patch does NOT include the following fix, you will need to do it yourself：
[Both CM7 and MIUI]0. Keyboard backlight fix ( Thanks to r2beta0 for fixing. Thanks to nanox_06 from grupoandroid.com. Thanks to layoroa and Motodoido and julianlatasa for telling me ):
Make sure you have apply fix_for_cm7_miui.zip from my attachment ! AND, if you have tried the earlier method （replacing framework-res.apk ), you SHOULD restore the original apk before trying this method !
[CM7]open setting>CM setting>Displayer Setting>(on)Automatic brightness>Advance mode>(on) custom>Edit other levels...
[MIUI]open setting>Displayer Setting>(on)Automatic brightness>Advance mode>(on) custom>Edit other levels...
[Wajk/r2beta0`s MIUI]r2beta0 has uploaded a moded framework-res.apk in #203, you can download it from there and replace the one under /system/framework/ . Don`t forget to set the permission to rw-r--r--. Reboot and Done !
then you will see a mass of squares. Find keyboard row and change the first 2 value from 0 to 255. Save setting. OK, done! Pull out your keyboard and you will find backlight work again.(Be sure you are in dark environment)
Tips: After turning off automatic brightness, your backlight will still work.
{
"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"
}
1. camera upside down ( Thanks to walter79 )
comment the line:
ro.media.capture.flip=horizontalandvertical
in /system/build.prop, make sure it is
#ro.media.capture.flip=horizontalandvertical
2. The camera noise after system booting, which exist in MIUI moded by Wajk
freeze talk.apk under /system/app
if you still need to use gtalk, try to install it from apk (not test if this will bring back the noise )
3. Stock soft-keyboard too small
Use 3rd-party keyboard app to replace it
4. Phone version shows MB525
Edit the line:
ro.product.model=MB525
in /system/build.prop to
ro.product.model=A953 //or anything you want
5. The default baseband of my nandroid backup is CH2.6.0/2.5.0
If you have no signal, please use baseband switcher to change to a suitable one or take a look at this (theoretically 100% works ) http://forum.xda-developers.com/showthread.php?t=1182050
6. If you think your flash light is a little dim compared to before. (Thanks to walter79 and below is what he said )
Be careful with that. Chinese pepole killed it with fixed-sbf for Europe Defy and in past europe people killed led with china fixed-sbf. It is related to devtree. But if your flashlight works more than 2x then you can edit your build.prop and del this:
- ro.media.capture.flashIntensity=41
- ro.media.capture.torchIntensity=25
7. SD card can NOT be mounted in recovery
In recovery, open advance, select start adbd and then kill adbd. Go back to try, and you should find your sd card has been mounted correctly. Next time if the issue appears again, just re-do it again.
8. If you have USB connection problem. Thanks to r2beta0
[MIUI] Please go to #211 for framework-res.apk. Replace the one under /system/framework/ with it.
[CM7] This is the manual solution r2beta0 post in #213
You must download apk_manager and use it to decompile framework-res.apk. Then you edit bools.xml that is inside res/values folder. The variable you must change is called config_enableUsbModeSelection, it is a user friendly name. Change from false to true. Then you use apk_manager to recompile it but don't sign. Set compression to zero.
The known issues which can NOT be solved till now:
1.Video hardware decoding is dead mostly, only .mp4 survival (need someone to fix that soon!)
[DEV] I upload these 2 patch which is used to port rmvb/mkv HW Decoding to froyo. It should help with porting HW to CM7/MIUI.
[MultiUpload] http://www.multiupload.com/JYNSW5VILR
[MegaUpload] http://www.megaupload.com/?d=A9OC25CT
[WithProxy][MegaUpload] http://174.140.154.13/?d=A9OC25CT
[Hotfile] http://hotfile.com/dl/127190044/59fde10/milestone2_RmvbMKV.7z.html
2.ALT-LOCK not working ( double press ALT instead )
3.USB mass storage mode issue ( except MIUI moded by Wajk )
You will find that you can NOT mount your SD card to PC.
Softwate Solution[Recommend]: Install Protocol-X Dual Mount SD Widget, you can download it from Android Market.
Manual Solution: Every time you connect to PC. Make sure connection manager appears in your notification bar, if not, enable/disable USB debug. Once it shows, first choose NONE, and then choose USB mass storage. By all this, you will see your SD card mounted in PC.
4. Charger light still not work
Seems lights.jordan.so under /system/lib/hw is related to it in some way. I replace it with the one from new leaked GB, then the LED became the charger light
Tutorial:
1. reboot to CWM and then restore nandroid backup (if you want to flash defy_cm7/miui.zip, make sure your CWM is 3.0+)
2. enable bootloader mode, flash fixed sbf via RSD ( fixed sbf is in firmware.7z )
3. Its recommend to make double wipes in stock recovery
4. reboot
5. CM7/Miui running.
[DEV]CH 2.2.2 (2.10.0) Download (The one who has downloaded it earlier should redownload it again for the correct SBF )
If anyone need to download any other CH ROMs but cannt find them, you can send me a PM
http://u.115.com/file/clsmsk69 PASSWORD: bbs.dkdiy.net
Defy CM7 Download http://defycm7.tanguy.tk/ //RC1 and nightly build are all OK
[Defy][DEV][ROM] CyanogenMod 7 (Android 2.3.4) By Quarx
[Fixed]CWM3.0 Download http://forum.xda-developers.com/showthread.php?t=1196590
Fixed sbf of CH 2.2.2(2.10.0) please download it from attachment below:
Great!
Everything is working?
Sent from my Milestone 2 with GingerBread
Oh that sound great.
My phone is bootlooping right now I could test anything before flashing a working ROM
Gsm radio not working is expected, need custom fixes for cm7.
Just try to fix the led/lights
Good lord, this week is beeing the best for the milestone 2 community! Thanks for your efforts guys!
If rom is booting, we can easily get logcats to fix all the problems
inheme said:
Good lord, this week is beeing the best for the milestone 2 community! Thanks for your efforts guys!
Click to expand...
Click to collapse
I concur. Thanks guys for all your efforts!
Sent from Motorola Milestone 2
will5 said:
If rom in booting, we can easily get logcats to fix all the problems
Click to expand...
Click to collapse
It did boot! Now I am runing CM7.
inheme said:
Good lord, this week is beeing the best for the milestone 2 community! Thanks for your efforts guys!
Click to expand...
Click to collapse
+1 / Like
Sent from Motorola Milestone 2 @ GB
Exciting! Cant wait for a decent workable version.
Endless7 said:
It did boot! Now I am runing CM7.
Click to expand...
Click to collapse
Have you tried all the baseband fixes we have? chinese fix, defy baseband changer, milestone 2 baseband app...
Anyway, if none of them work, maybe baseband needs to be adapted to cm7.
yea like this one http://forum.xda-developers.com/showthread.php?t=1182050
will5 said:
Have you tried all the baseband fixes we have? chinese fix, defy baseband changer, milestone 2 baseband app...
Anyway, if none of them work, maybe baseband needs to be adapted to cm7.
Click to expand...
Click to collapse
The biggest porblem: I cannot connect my SD card to PC !
Maybe you can push the files via ADB to your SDCard/Internal memory?
U should get a microSD usb reader. I have one, maybe I could test stuff out for u.
Or you can use a sd card reader
Lets wait for experienced people, I think sd is not working just because it behaves differently than defy storage, it wont be hard to fix it.
I have no minisdcard reader and now time here is 0:30 am, so it`s impossible to buy one.
jambo89liam said:
U should get a microSD usb reader. I have one, maybe I could test stuff out for u.
Click to expand...
Click to collapse
USB debug is now dead
I have upload the files needed. You all could have a try !
You can try USB storage from CWM.
will5 said:
You can try USB storage from CWM.
Click to expand...
Click to collapse
OK , will have a try
Which cm did u download, ive downloaded the latest nightly build. "cm7-110518-0722-NIGHTLY-Jordan"
Im on Gingerbread at the moment, do i need to go back to froyo before flashing?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is an experimental build of the open ROM Omni5.1 for our Samsung GalaxyTab Plus.
Get the media patch for the 20150819 build in the 7.7 thread.
Detail can be found in 7.7 thread
Before you post, read the 7.7 thread first!
*** Post with no detail will be ignored ***
Know issues:
Now is in an early stage. Read carefully before flashing.
1. Wifi direct not fully working
2. May be more....
Downloads: :highfive:
AFH: https://www.androidfilehost.com/user/?w=settings-dev-files&flid=28293
d-h.st: http://d-h.st/users/danielhk/?fld_id=44273#files
mirror: 百度网盘
Use the latest Delta gapps: http://forum.xda-developers.com/showthread.php?t=2997368
** Latest TWRP (2.8.6.x or above) is required.
Omni is not rooted. To root, flash the latest SuperSU-24x.zip in recovery.
Credits: :good:
** The OmniROM team who have such a good idea and their hardworks
** All those who donate to me. Giving me the resources to upgrade my PC and accessories!
** All those who help our cool tab's developments!
Donations:
OMG.i'm such an idiot.roll out and i saw the twpr 2.8.6.0.I wasn' t see that before.flashing succes.Every thing work smoth and fast.
Main problem until now:
1.Brightness slide broke->soluion is download this app and disable "Automatic Brightness" https://play.google.com/store/apps/details?id=net.ailuro.android.settings.screen.brightness
2.Wifi passw clear LOL ~
3.Setting interface xxx
4.Unable to use Simcard
5.HW video notwork.BUT- you can try UC Browser for online video(Fb,youtube,...) like an option https://play.google.com/store/apps/details?id=com.UCMobile.intl .Not done yet,you need to restore the flash cache from 4.4 in titanium backup from the link below,other wise ,it don't work.
6.Can't upload file!
7.I don't see any problem left with reboot.app and system.I'm a BIG dump dump when forget to check update twpr ...what a shame (='.'=)
*.Root: http://download.chainfire.eu/supersu
Trung Gs said:
In TWPR ,after wipe,Omni(27mar2015) p6200 build and gapps5.1 is flashing succes.But,when i reboot system,the screen is black and my tab can't boot into homescreen.I try again with only rom,it still the same problem.It 's hard to say when i have try every way i know. what a shame ≧﹏≦. I hope u can't find out what problem with this build from other people too or the error come from my mistake.
Click to expand...
Click to collapse
Guess might be your tab............works for me. just perform a wipe, reboot the back into recovery and wipe once more.
Install rom, wipe and install rom again.
Reboot and see if it works for you. (can flash gapps later and super su if u need)
Can't access download link
Its weird! AFH says I dont have access to file, Dev-Host just direct me to their homepage, and mirror link is in chinese so I dont have any idea what buttons to hit. Is it just me? Anyone here who can guide me how to download the file?
omike123 said:
Its weird! AFH says I dont have access to file, Dev-Host just direct me to their homepage, and mirror link is in chinese so I dont have any idea what buttons to hit. Is it just me? Anyone here who can guide me how to download the file?
Click to expand...
Click to collapse
Edit 1:
Downloading now! Using google chrome I was able to translate mirror link page to English.
Edit 2:
Successfully flash the Rom via TWRP 2.8.6.0
As mentioned in the OP
- quicksettings pulldown can only be pulled once.
- adjusting brightness slider do nothing
- torch is working
- system apps seems to load faster than cm12.
One thing that caught up my attention is that simcard is not recognized. Have to goto settings/about tablet and found out that baseband version is unknown. Shame cause I really think this rom is more fluid compare to cm12.
I was unable to test user's app due to simcard unavailability, hence 3G as well, as I heavily dependent on it.
Also noticed that 1st & 2nd boot is ok but on 3rd boot is only showing blank screen ( omni bootlogo not showing ) have to longpress power button a couple of times until omni bootscreen appears.. P6200 user here.
Thanks again to this ROM, pretty much stable , no soft reboots. Battery is good, Minor issues i could see.
Video playback is still an issue i believe, even in YouTube.
Thanks again
If this rom could see the daylight I will really love it. It's much better than cm12 . Aside the baseband issue in p6200 really would have preferred this .
Sent from my GT-P6200 using xda Forums PRO
Have just installed latest version 20150518. Installation process without any problem. System is running stable.:good:
But SIM-card is not found. Tried several times.
It's no problem with CM12.1 rom. So I'm back to CM12.1.
uli-hh said:
Have just installed latest version 20150518. Installation process without any problem. System is running stable.:good:
But SIM-card is not found. Tried several times.
It's no problem with CM12.1 rom. So I'm back to CM12.1.
Click to expand...
Click to collapse
So unknown baseband issue has'nt been fix yet?
omike123 said:
So unknown baseband issue has'nt been fix yet?
Click to expand...
Click to collapse
That's what it shows in settings/about phone
uli-hh said:
That's what it shows in settings/about phone
Click to expand...
Click to collapse
Well I guess I'll just have to wait for the next release. I'm sure @daniel_hk would fix this in future updates.
omike123 said:
Well I guess I'll just have to wait for the next release. I'm sure @daniel_hk would fix this in future updates.
Click to expand...
Click to collapse
I don't have problem showing the baseband with or without a sim card. Don't know why some p6200 can't. It's the same modem chip and I'm using the same lib for both too.
Clean flash, Wait for a few minutes, etc.
Can anyone confirm that?
If really can't, in a terminal emulator type:
su (already rooted of course)
rild
see if any error message
here is the result:
WARNING: linker: libsec-ril.so has text relocations. This is wasting memory and prevents security hardening. Please fix.
rm: /data/misc/radio/dlink: permission denied
it is also showing invalid IMEI and unknown baseband version.
PugeAko said:
here is the result:
WARNING: linker: libsec-ril.so has text relocations. This is wasting memory and prevents security hardening. Please fix.
rm: /data/misc/radio/dlink: permission denied
it is also showing invalid IMEI and unknown baseband version.
Click to expand...
Click to collapse
The first one is just a warning because of the only old blob we have.
The second line means the daemon is not start. I'll look into it but I need someone with a p6200 to test for me.
daniel_hk said:
The first one is just a warning because of the only old blob we have.
The second line means the daemon is not start. I'll look into it but I need someone with a p6200 to test for me.
Click to expand...
Click to collapse
Willing to do that.
edwin270 said:
Willing to do that.
Click to expand...
Click to collapse
I think I found the reason. There is a file missing. View attachment libsecril-client.zip
unzip the above zip will get the file libsecril-client.so. Copy the file to /system/lib with a root browser (eg. ES FileExplorer) will do.
Hoping it work for t869 too. t869 owners are welcome to test too.
Good luck!
PS. Will include it in the next build
daniel_hk said:
I think I found the reason. There is a file missing. View attachment 3324813
unzip the above zip will get the file libsecril-client.so. Copy the file to /system/lib with a root browser (eg. ES FileExplorer) will do.
Hoping it work for t869 too. t869 owners are welcome to test too.
Good luck!
Click to expand...
Click to collapse
Was about to try that and alert you. Compared the lib folder for cm12.1 to that of omni and Realized the same missing libsecril-client.so and a couple of others. Looks like you got to it first. Anyway thinking of creating a flashable package for it. [emoji4] [emoji4] [emoji4]
OTG -Wifi???
@daniel_hk This may be stupid but i have to ask u.Does this kernel support USB Wifi with OTG?
Tried the lib files provided and a couple of others from cm12.1...................same old. Installed CM12.1 again and tried the rild check and got the same error as mentioned by PugeAko , though baseband is working with that rom.
Will be pulling the lib from stock MF1 rom for our dear p6200 soon, to see what comes of it.
Will post my findings soon.
Edit:
Checked radio directory in cm12.1 vrs OMni and some files are missing in Omni. Pulled that from cm12.1 but this constant black screen booting of Omni is making me frustrated at the moment. Too much black screen. Trying to see if I can get a boot.
Edit2:
Giving up. Don't know what it is but cannot endure this constant black screen any longer and time is not a luxury that I can afford now, its preventing me from helping figure out how to fix this baseband issue. Going back to the buggy cm12.1 rom. This rom is promising though.
Trung Gs said:
@daniel_hk This may be stupid but i have to ask u.Does this kernel support USB Wifi with OTG?
Click to expand...
Click to collapse
Each USB Wifi probably have different chips which requires drives supplied by the manufacture. For it to work, it requires HAL drivers/firmwares too. Normally there is a CD or place to download. Window might have some driver for a few chips. Linux (Android) would be another story.
Normally, a kernel would only have the drivers for the on board chips.
edwin270 said:
Tried the lib files provided and a couple of others from cm12.1...................same old. Installed CM12.1 again and tried the rild check and got the same error as mentioned by PugeAko , though baseband is working with that rom.
Will be pulling the lib from stock MF1 rom for our dear p6200 soon, to see what comes of it.
Will post my findings soon.
Edit:
Checked radio directory in cm12.1 vrs OMni and some files are missing in Omni. Pulled that from cm12.1 but this constant black screen booting of Omni is making me frustrated at the moment. Too much black screen. Trying to see if I can get a boot.
Edit2:
Giving up. Don't know what it is but cannot endure this constant black screen any longer and time is not a luxury that I can afford now, its preventing me from helping figure out how to fix this baseband issue. Going back to the buggy cm12.1 rom. This rom is promising though.
Click to expand...
Click to collapse
cm12.1 is probably the wrong place to try. Omin for p6800 would be the wiser choice.
Anyway, I will try to get it work on the next build.
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
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.