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
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
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)
THREAD
"Hi, I've no 10 msg on xda so i can't report bugs to the dev "
Report here your questions/bugs about the rom, don't spam the dev thread with your 11th post :highfive:
I've created this thread without ask permission to HardLight, your warranty is now void :victory:
First of all, a big thanks to HardLight, skinbark and bigsupersquid for the OS2SD mod
AndroidMeda, Conn O'Griofa and other members of androidarmv6 for bringing KitKat to P500
CyanogenMod for sources
Here is the ROM : Link
please, read the first post
and remember:
To wipe clean 100% and install a new rom, in CWM or TWRP
Select “wipe data/factory reset
Select “yes”
Go to “mounts and storage”
Select “format /boot”
Select “yes”
Select “format /system”
Select “yes”
Back out of that menu to the main one again and select “advanced”
Select “Wipe Dalvik Cache”
Select “yes”
Click to expand...
Click to collapse
PLEASE UPDATE THE ROM ONLY WITH OS2SD UPDATES FROM HARDLIGHT'S THREAD
FROM OCTOBER ONLY THE F2FS OS2SD VERSION WILL BE DEVELOPED (best performance)
IF YOU UPDATE IN OTHER WAYS YOUR PHONE WILL BOOTLOOP
Summary:impression
Bugs/strange things
How To (2nd post)
- Minitool tutorial
- Overclock & Performance settings
- Superuser update and titanium backup problem
- Navigation bar with soft key
- Mod power button<-> search button (if your power button is broken)
- Saving battery
- Dialer pad number problem with L theme
- Make any rom an OS2SD rom
Impression, what i've done:
1st time:
with my "old" 8gb class 10 sd, a transcend, i've followed the instructions, with partition TWRP and TB
the first boot it's ok (after 2 min on the CM logo :fingers-crossed
open the options menu, i see lag and slow speed menu,
tried install some apps with TB and some were installed in the sd when i have "1 Gb" free in the internal memory.
Ok there was something wrong, so ... i changed the sd
Click to expand...
Click to collapse
2nd time:
format/wipe with a sandisk 8gb class 10, i've followed the instructions, 6 gb fat32, 380mb ext4, 128 swap, 1,1gb ext4
now everything it's ok, a little lag to launch the dialer and apps, like with the CM 4.1.2,
TB restore all apps in the "internal" memory :victory:
Click to expand...
Click to collapse
Performance
performance settings: cpu 320-650, smartassv2, sio - kms page merging on,
dev options: set to 0,0 all animations,
without a sim or not in aereo mode the phone lag a bit, insert a sim or turn on Aereo
battery use as phone only, sms&call, 2g: yesterday 81% (14h), now 16% (2d 7h)
{
"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"
}
battery use as phone, data on 2g mode all the time and 1h gps:..
Click to expand...
Click to collapse
Bugs/strange things:
in call the proximity sensor don't turn off the screen it happens only if you have enabled the loudspeaker or use hearphones
for 3rd part apps use this to enable the airplane mode (with llama is not needed)
sound volume:in sound options play a little with the notify/ringtone level, check or uncheck the separate volume option and play again with notify& ringtone level, to me they change together also with the "separate" options solved in 18/08/14 rom
could i update to the latest normal or ota nightly? NO, you need an OS2SD rom, see the summary to make your os2sd rom
wifi battery drain
wifi hotspot,it need a reboot after use
fm not working
If you use Instagram, download the v.6.3.1: http://instagram.en.uptodown.com/android/download/72905
please refer to this post for instagram downloader and xposed module etc (thanks to xu3sno)
How To:
- Repartition SD card, the minitool partition tutorial:
Now in the first post of the HardLight's thread, under "Installation instructions" there are two beautifull "Partitioning guides", please follow one of them step by step
start minitool partition, chose minitool partition wizard,
select your usb disk (i.e. with my 8gb sd i've selected the disk "basic 7,47 GB" )
if you have also a sd with 2 or more partitions you have to delete all partitions -> select partition and click on "delete" button
when you have all the space in your sd "unallocated" (in gray) you can create the partitions needed
so select your unallocated volume and clic the "create" button
if minitool say "the new created partition cannot be used in win..." click yes
in partition label: leave blanc, don't give it a name (no /system, system or anything else)
in create as select "Primary"
in file system select "fat32"
in cluster size leave default
in size location unallocated space before 0.00 MB
partition size 5900 MB
click ok
do last steps for a second partition: primary, select the file system "ext4", partition space 450MB (You need 380+ mb for system on f2fs.)
the same for 3rd: primary, select the file sistem "linux swap, partition space 128MB"
the same for the 4th: primary; select the file system "ext4", partition space ~1.100 MB
in the end you have to CLICK THE APPLY BUTTON, else nothing happens
partition scheme for F2FS only:
1st: 5850 mb FAT32
2nd: 450 mb EXT4 (before flash the rom you have to change the file system to f2fs in TWRP-> select wipe->advanced wipe->SELECT Data -> click Repair or Change File System->Change File System>F2FS->swipe to change)
3rd: 128 mb linux swap
4th: ~1.100 mb EXT4 (change the file system to f2fs before install the rom)
- Overclock & Performance settings
To enable the performance menu you have to:
go to settings->about phone-> and tap tap tap tap tap tap ... tap on the "build number"
Now you've "dev options" & a "performance" menus at the end of the "settings" menu.
In dev options:
you can find 3 scale animation options, set them to 0,0x
In Performance:
set CPU min freq to 320, max to 729 (check "the set on boot" option) ... warning someone can keep 800+mhz but at long time this can BREAK (really) your phone & use a lot of battery
set Governor to smartassv2
set in I/O scheduler -> SIO or DEADLINE (check the "set on boot" option)
set in Memory -> check the Kernel page merging
uncheck "force high end graphic" (if you don't need a transparent notification bar)
make a reboot after these settings is highly recomended
in Testing PurePerformance mod
- Superuser update and titanium backup problem
if you have Superuser problem with titanium backup: i remember there was a fix to that, but the simple method is to install supersu (via TWRP) from the playstore
- Navigation bar with soft key
edit the build.prop and insert
Code:
qemu.hw.mainkeys=0
to show navigation bar with soft key
update, thanks to xu3sno
Well, for transparent/translucent status bar and softkeys, just edit build.prop, find ro.config.low_ram= true, change the value to false. It will enable translucent status bar.
Still in build.prop add line qemu.hw.mainkeys=0 in order to enable softkeys in navigation bar. Save > exit > reboot system.
Softkeys with L theme, install this module (you need Xposed of course). To enable L theme softkeys, go to Settings > Buttons > Buttons and layout > tap reset. However, once the screen lock and open, softkeys will back to the traditional one. Don't know, may be it's a bug.
Click to expand...
Click to collapse
- Mod power button<-> search button (if your power button is broken)
the search<->power button mod can be applied in the rom zip before to flash, with 7zip open the CM-11-XXXXXXX-NIGHTLY-OS2SD-p500.zip\system\usr\keylayout and you need only to sobstitute the 4 files manually inside the zip ( see in the mod thread -> manual version)
- Saving Battery
refer to this thread
and to this explanation
please don't use tweaks like the parsley
i'll test the wifi.supplicant_scan_interval=180 in the end this build.prop change don't saving power if wifi is connected but when not in range of a known network and you leave wifi on, you can set from 120 to ...3600 (i think is the time expressed in seconds to wake up the wifi and to check if there are known network).
2nd test: the bigsupersquid's patch need a new kernel, not applicable ATM
bigsupersquid patch and dovidhalevi iwconfig suggestion
on the second p500 (yes!, i use it only in aereo and wifi because i've no 2nd sim)
- Dialer pad number problem with L theme
If you see this in your dialer:
there is a problem in the L dark theme, until the theme dev will solve the problem you can click where you usually write phone numbers and swipe to the top.
or in the "speedcall""all contacts""favourite" tabs click on the search bar on top and write a number to call,now you can call the number directly from the search bar or then if you click the pad icon can see the full pad number
- Make any rom an OS2SD rom
Please read the HardLight Guide
try this if you want the latest nightly
Images:
with kitkat original theme and with L theme (Android L - CM 11 Theme, thanks to tung91 )
Thanks, good thread.
By the way you won't be able to flash new nighly, first I need to modify it for sd.
Sent from my LG-P500 using xda premium
HardLight said:
Thanks, good thread.
By the way you won't be able to flash new nighly, first I need to modify it for sd.
Sent from my LG-P500 using xda premium
Click to expand...
Click to collapse
thanks
i see in the updater-script that the mount point is set to this
mount("ext4", "EMMC", "/dev/block/mmcblk0p2", "/system")
a simple question, if i use this updater script mod with other rom (i.e. rhar****'s omega) and your TWRP could i make my "omega os2sd" or there is something else to change?
ah i pushed the thanks button, but however i want to say Thank you for your work
edit:
added at 1st post the link to the HardLight's os2sd guide
Anyone tried using this rom with a class 4 sd card? I think I'm about to try it, even though I'm pretty sure it'll be slow like hell
brgil96 said:
Anyone tried using this rom with a class 4 sd card? I think I'm about to try it, even though I'm pretty sure it'll be slow like hell
Click to expand...
Click to collapse
a little bit, maybe,however also the internal memory transfer rate is 5-10 mb/s (lower than an usb2 transfer rate), is not like the hdd internal transfer rate (hundreds mb/s) or an ssd (gb/s)
what i can see is that, few apps = the phone is quite fast
much apps need internet connection = the phone is unusable
i've a decent use with Whatsapp on, but is the only app with data necessity unfreezed
the amazon store,appfree, skype, teamviewer etc. are freezed, and i'll unfreeze when needed
wats ths
cm11 or bug fixs
xdema said:
a little bit, maybe,however also the internal memory transfer rate is 5-10 mb/s (lower than an usb2 transfer rate), is not like the hdd internal transfer rate (hundreds mb/s) or an ssd (gb/s)
what i can see is that, few apps = the phone is quite fast
much apps need internet connection = the phone is unusable
i've a decent use with Whatsapp on, but is the only app with data necessity unfreezed
the amazon store,appfree, skype, teamviewer etc. are freezed, and i'll unfreeze when needed
Click to expand...
Click to collapse
For some reason I never thought of freezing data apps, might give it a try.
So I took the bait and installed it. Apart from the obvious delay when opening most apps (which is perfectly bearable so far), the rom runs smooth as silk. However, I don't have any additional apps apart from google's yet, so I still have to try that out. Time will tell.
PS: battery usage seems to be way lower so far (except for the wifi drain) when compared to gingersnap (which I was using before), and that's a first to me. You can barely say this battery is 4 years old (it's actually quite obvious but whatever x) )
Bricked?
I've flashed this ROM with files for broken power button mod and gapps. After first boot everything seemed to be working but I was getting constant keyboard crashes so I've tried all that "reflash gapps, clear cache etc." As it didn't solve the problem I've downloaded a keyboard on PC but I couldn't connect the phone via USB (there was no notification about connection and nothing showing up on PC). Then I turned off the phone and I can't turn it back on and I can't enter recovery. It's completly dead. The only thing that is working is offline charging. However when screen turns off after a few seconds I can't wake it up with any button. What to do?
Przeszczep said:
I've flashed this ROM with files for broken power button mod and gapps. After first boot everything seemed to be working but I was getting constant keyboard crashes so I've tried all that "reflash gapps, clear cache etc." As it didn't solve the problem I've downloaded a keyboard on PC but I couldn't connect the phone via USB (there was no notification about connection and nothing showing up on PC). Then I turned off the phone and I can't turn it back on and I can't enter recovery. It's completly dead. The only thing that is working is offline charging. However when screen turns off after a few seconds I can't wake it up with any button. What to do?
Click to expand...
Click to collapse
Please at this moment don't use the f2fs version, it's only for the brave, in the OP there are 2 kind of rom: a f2fs version and another not-f2sf
keyboard app problem -> go to setting -> app -> select keyboard -> clear data, clear cache (into this menu, not in the recovery or something else)
else you can try with another keyboard, usually i set swiftkey as default.
See you the LG logo and after a black screen?
if you didn't use KDZ or LGMDP to flash roms, usually you can enter in recovery (if somethings go wrong with LGMDP or KDZ you make an hardbrick).
so don't use KDZ by now
how to enter the recovery: pull out the battery, wait 2 sec, reinsert, push power on button (you can see the LG logo) and after keep only vol down and home buttons.
if you can see the recovery then reflash the rom
sometimes after the LG logo you see a black screen, please check if the phone is off or the screen is on but black, if it's black it could be you didn't pressed the vol+home buttons in time
if you have problem contact shinobisoft or HardLight and search the howto unbrick/revive p500 guides in xda (i remember that there were 3 or 4)
brgil96 said:
So I took the bait and installed it. Apart from the obvious delay when opening most apps (which is perfectly bearable so far), the rom runs smooth as silk. However, I don't have any additional apps apart from google's yet, so I still have to try that out. Time will tell.
PS: battery usage seems to be way lower so far (except for the wifi drain) when compared to gingersnap (which I was using before), and that's a first to me. You can barely say this battery is 4 years old (it's actually quite obvious but whatever x) )
Click to expand...
Click to collapse
with latest file system mod (f2fs) it should a bit faster, tomorrow i'll test on my 2nd p500 (actually with omega rom), see the HardLight's thread
I've managed to somehow turn on the phone but i still have 2 problems:
Crashing keyboard app. It has no data and 24.00KB cache. However I don't know if I can clear it because when I tap on "Clear cache" nothing happens and it stays at 24KB.
I can't add Google account. In settings I tap on "Add account" and nothing happens.
Factory reset and reflashing gapps didn't resolve those issues.
Przeszczep said:
I've managed to somehow turn on the phone but i still have 2 problems:
Crashing keyboard app. It has no data and 24.00KB cache. However I don't know if I can clear it because when I tap on "Clear cache" nothing happens and it stays at 24KB.
I can't add Google account. In settings I tap on "Add account" and nothing happens.
Factory reset and reflashing gapps didn't resolve those issues.
Click to expand...
Click to collapse
fix for keyboard issue: the keyboard app is corrupted
fix: http://forum.xda-developers.com/showpost.php?p=55220723&postcount=99
G account: are you with the f2fs rom or not?
Keyboard working.
xdema said:
G account: are you with the f2fs rom or not?
Click to expand...
Click to collapse
Yes I'm using f2fs.
Przeszczep said:
Keyboard working.
Yes I'm using f2fs.
Click to expand...
Click to collapse
the 31/08 seem have some corrupted files, now i'm trying with the bigsupersquid 30/08 rom
Skype 5 is not working on my P500, the previous version 4 worked. Is anyone experiencing the same problem?
I have attached my logcat output below, however I cannot deduct any useful information from that. I am using hardlight's current CM version from 30th august.
Code:
I/Timeline( 686): Timeline: Activity_launch_request id:com.skype.raider time:65250488
I/ActivityManager( 426): START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.skype.raider/.Main bnds=[82,191][148,264]} from pid 686
V/Zygote (20585): Switching descriptor 31 to /dev/null
V/Zygote (20585): Switching descriptor 10 to /dev/null
I/ActivityManager( 426): Start proc com.skype.raider for activity com.skype.raider/.Main: pid=20585 uid=10118 gids={50118, 1006, 3003, 3002, 1028, 1015}
D/ActivityThread(20585): handleBindApplication:com.skype.raider
D/ActivityThread(20585): setTargetHeapUtilization:0.25
D/ActivityThread(20585): setTargetHeapMinFree:524288
V/ActivityThread(20585): com.skype.raider white listed for hwui
D/dalvikvm(20585): Trying to load lib /data/app-lib/com.skype.raider-1/libSkypeAndroid.so 0x419d0760
D/dalvikvm(20585): Added shared lib /data/app-lib/com.skype.raider-1/libSkypeAndroid.so 0x419d0760
D//Ln.java:218(20585): main Configuring Logging, minimum log level is INFO
D/dalvikvm(20585): Trying to load lib /data/app-lib/com.skype.raider-1/libSkyLib.so 0x419d0760
E/CrashAndAnrHandler(20585): Dumping stack for signal 7
E/CrashAndAnrHandler(20585): Dumping stack for signal 11
D/Zygote ( 134): Process 20585 terminated by signal (11)
I/ActivityManager( 426): Process com.skype.raider (pid 20585) has died.
V/Zygote (20600): Switching descriptor 31 to /dev/null
V/Zygote (20600): Switching descriptor 10 to /dev/null
I/ActivityManager( 426): Start proc com.skype.raider for activity com.skype.raider/.Main: pid=20600 uid=10118 gids={50118, 1006, 3003, 3002, 1028, 1015}
D/ActivityThread(20600): handleBindApplication:com.skype.raider
D/ActivityThread(20600): setTargetHeapUtilization:0.25
D/ActivityThread(20600): setTargetHeapMinFree:524288
V/ActivityThread(20600): com.skype.raider white listed for hwui
D/dalvikvm(20600): Trying to load lib /data/app-lib/com.skype.raider-1/libSkypeAndroid.so 0x419d1670
D/dalvikvm(20600): Added shared lib /data/app-lib/com.skype.raider-1/libSkypeAndroid.so 0x419d1670
W/ActivityManager( 426): Launch timeout has expired, giving up wake lock!
D//Ln.java:218(20600): main Configuring Logging, minimum log level is INFO
D/dalvikvm(20600): Trying to load lib /data/app-lib/com.skype.raider-1/libSkyLib.so 0x419d1670
E/CrashAndAnrHandler(20600): Dumping stack for signal 7
E/CrashAndAnrHandler(20600): Dumping stack for signal 11
D/Zygote ( 134): Process 20600 terminated by signal (11)
I/ActivityManager( 426): Process com.skype.raider (pid 20600) has died.
V/Zygote (20615): Switching descriptor 31 to /dev/null
V/Zygote (20615): Switching descriptor 10 to /dev/null
I/ActivityManager( 426): Start proc com.skype.raider for activity com.skype.raider/.Main: pid=20615 uid=10118 gids={50118, 1006, 3003, 3002, 1028, 1015}
D/ActivityThread(20615): handleBindApplication:com.skype.raider
D/ActivityThread(20615): setTargetHeapUtilization:0.25
D/ActivityThread(20615): setTargetHeapMinFree:524288
V/ActivityThread(20615): com.skype.raider white listed for hwui
D/dalvikvm(20615): Trying to load lib /data/app-lib/com.skype.raider-1/libSkypeAndroid.so 0x419d2590
D/dalvikvm(20615): Added shared lib /data/app-lib/com.skype.raider-1/libSkypeAndroid.so 0x419d2590
D//Ln.java:218(20615): main Configuring Logging, minimum log level is INFO
D/dalvikvm(20615): Trying to load lib /data/app-lib/com.skype.raider-1/libSkyLib.so 0x419d2590
E/CrashAndAnrHandler(20615): Dumping stack for signal 7
E/CrashAndAnrHandler(20615): Dumping stack for signal 11
I/ActivityManager( 426): Process com.skype.raider (pid 20615) has died.
W/ActivityManager( 426): Force removing ActivityRecord{423a5838 u0 com.skype.raider/.Main t41}: app died, no saved state
D/Zygote ( 134): Process 20615 terminated by signal (11)
W/InputMethodManagerService( 426): Window already focused, ignoring focus gain of: [email protected] attribute=null, token = [email protected]
I/Timeline( 686): Timeline: Activity_idle id: [email protected] time:65269779
xdema said:
the 31/08 seem have some corrupted files, now i'm trying with the bigsupersquid 30/08 rom
Click to expand...
Click to collapse
about this problem,
i have tried f2fs builds from 8/30, 9/5 and 9/8 ... and i cant get gapps to work in any of those ...
however gapps are working fine on ext4 version ... tried two latest from hardlights drive
is it possible that gapps are just not working on fresh install f2fs builds?
and upgrading from ext4 version to f2fs with converting data partition should work ?
/edit
well nevermind, hardlight uploaded new version of gapps and f2fs build works for me now
thank you hardlight & everyone affiliated
Flo.de said:
Skype 5 is not working on my P500, the previous version 4 worked. Is anyone experiencing the same problem?
I have attached my logcat output below, however I cannot deduct any useful information from that. I am using hardlight's current CM version from 30th august.
Code:
I/Timeline( 686): Timeline: Activity_launch_request id:com.skype.raider time:65250488
I/ActivityManager( 426): START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.skype.raider/.Main bnds=[82,191][148,264]} from pid 686
V/Zygote (20585): Switching descriptor 31 to /dev/null
V/Zygote (20585): Switching descriptor 10 to /dev/null
I/ActivityManager( 426): Start proc com.skype.raider for activity com.skype.raider/.Main: pid=20585 uid=10118 gids={50118, 1006, 3003, 3002, 1028, 1015}
D/ActivityThread(20585): handleBindApplication:com.skype.raider
D/ActivityThread(20585): setTargetHeapUtilization:0.25
D/ActivityThread(20585): setTargetHeapMinFree:524288
V/ActivityThread(20585): com.skype.raider white listed for hwui
D/dalvikvm(20585): Trying to load lib /data/app-lib/com.skype.raider-1/libSkypeAndroid.so 0x419d0760
D/dalvikvm(20585): Added shared lib /data/app-lib/com.skype.raider-1/libSkypeAndroid.so 0x419d0760
D//Ln.java:218(20585): main Configuring Logging, minimum log level is INFO
D/dalvikvm(20585): Trying to load lib /data/app-lib/com.skype.raider-1/libSkyLib.so 0x419d0760
E/CrashAndAnrHandler(20585): Dumping stack for signal 7
E/CrashAndAnrHandler(20585): Dumping stack for signal 11
D/Zygote ( 134): Process 20585 terminated by signal (11)
I/ActivityManager( 426): Process com.skype.raider (pid 20585) has died.
V/Zygote (20600): Switching descriptor 31 to /dev/null
V/Zygote (20600): Switching descriptor 10 to /dev/null
I/ActivityManager( 426): Start proc com.skype.raider for activity com.skype.raider/.Main: pid=20600 uid=10118 gids={50118, 1006, 3003, 3002, 1028, 1015}
D/ActivityThread(20600): handleBindApplication:com.skype.raider
D/ActivityThread(20600): setTargetHeapUtilization:0.25
D/ActivityThread(20600): setTargetHeapMinFree:524288
V/ActivityThread(20600): com.skype.raider white listed for hwui
D/dalvikvm(20600): Trying to load lib /data/app-lib/com.skype.raider-1/libSkypeAndroid.so 0x419d1670
D/dalvikvm(20600): Added shared lib /data/app-lib/com.skype.raider-1/libSkypeAndroid.so 0x419d1670
W/ActivityManager( 426): Launch timeout has expired, giving up wake lock!
D//Ln.java:218(20600): main Configuring Logging, minimum log level is INFO
D/dalvikvm(20600): Trying to load lib /data/app-lib/com.skype.raider-1/libSkyLib.so 0x419d1670
E/CrashAndAnrHandler(20600): Dumping stack for signal 7
E/CrashAndAnrHandler(20600): Dumping stack for signal 11
D/Zygote ( 134): Process 20600 terminated by signal (11)
I/ActivityManager( 426): Process com.skype.raider (pid 20600) has died.
V/Zygote (20615): Switching descriptor 31 to /dev/null
V/Zygote (20615): Switching descriptor 10 to /dev/null
I/ActivityManager( 426): Start proc com.skype.raider for activity com.skype.raider/.Main: pid=20615 uid=10118 gids={50118, 1006, 3003, 3002, 1028, 1015}
D/ActivityThread(20615): handleBindApplication:com.skype.raider
D/ActivityThread(20615): setTargetHeapUtilization:0.25
D/ActivityThread(20615): setTargetHeapMinFree:524288
V/ActivityThread(20615): com.skype.raider white listed for hwui
D/dalvikvm(20615): Trying to load lib /data/app-lib/com.skype.raider-1/libSkypeAndroid.so 0x419d2590
D/dalvikvm(20615): Added shared lib /data/app-lib/com.skype.raider-1/libSkypeAndroid.so 0x419d2590
D//Ln.java:218(20615): main Configuring Logging, minimum log level is INFO
D/dalvikvm(20615): Trying to load lib /data/app-lib/com.skype.raider-1/libSkyLib.so 0x419d2590
E/CrashAndAnrHandler(20615): Dumping stack for signal 7
E/CrashAndAnrHandler(20615): Dumping stack for signal 11
I/ActivityManager( 426): Process com.skype.raider (pid 20615) has died.
W/ActivityManager( 426): Force removing ActivityRecord{423a5838 u0 com.skype.raider/.Main t41}: app died, no saved state
D/Zygote ( 134): Process 20615 terminated by signal (11)
W/InputMethodManagerService( 426): Window already focused, ignoring focus gain of: [email protected] attribute=null, token = [email protected]
I/Timeline( 686): Timeline: Activity_idle id: [email protected] time:65269779
Click to expand...
Click to collapse
skype 5.0.0.49715 it was ok for me on os2sd (not the f2fs version) now i've installed latest version from playstore, click the icon did nothing, so back to v4 (last titanium backup)
microphone is really silent in the latest build ... at normal setting no one can hear me, when i put it on speaker i have to hold it right next to mount to get my voice barely hear-able......
nesty1990 said:
microphone is really silent in the latest build ... at normal setting no one can hear me, when i put it on speaker i have to hold it right next to mount to get my voice barely hear-able......
Click to expand...
Click to collapse
reported to HardLight's thread
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.
The intention behind this thread is to share some experience of a little project where I try to migrate the Sony Xperia Shinano devices (based on Qualcomm MSM8974 chipset with a Broadcom BCM4339 wifi/bluetooth chip) from the old bcmdhd wifi driver to a close-to-mainline brcmfmac driver. I want to share the progress and status here, and maybe get some hints. It is work in progress, and for sure it still contains some mistakes - I haven't done something like this before and am still learning.
Why?
The Shinano devices are still maintained by the LineageOS, and some devices are currently on the official LineageOS 17.1 stream.
The kernel however is terribly outdated, based on msm-3.4
There are some wifi issues with all LineageOS-based ROMs since years, like weak 5GHz connections and non-working wifi in some countries. There are some hacks around that, but they work (afaik) by practically disabling the kernel-level regulatory system by e.g. setting a static country code like "DE".
I am curious if we can improve that by updating the kernel drivers and network/wifi components, and maybe also the firmware (to the latest release available from Broadcom, 6.37.34.43 ?) . I got the ideas from Sonyxperiadev/Loire (+ related platform config), the Linux Backport Project and other MSM8974 based devices.
Working so far:
Did a few tests only so far, STA with WPA2 and p2p (hotspot) seem to work
Wifi connection is stable on 2,4GHz on 00 world regulatory domain (tested on a Z3 and a Z3c)
5GHz manually setting a country code (could only test DE)
Switching countries / setting new regulatory domains is now working, too
Download speed looks OK to me, in my case at least better than before Download >60MBit, Upload >30 Mbit on some initial tests.
Not working yet:
WifiHAL (qcom-caf) does not work correctly. This may create multiple issues, tbd.
Connection bandwidth seems to be not reported correctly
I don't know if wowlan works (interrupts working?)
Stability: After 1-2 days without reboot wifi sometimes crashes but immediately reconnects. Reason not yet understood.
Patches & Picks
Kernel:
backported and configured brcmfmac, cfg800211 wireless configuration API and wireless network stack from linux-stable v5.8 by adopting the compatibility patches from the linux backporting project.
updated Shinano device tree, updated Z3, Z3c and Z2 (Z2 test needed!) defconfigs (unset bcmdhd and enabled brcmfmac) and removed board-sony_shinano-wifi.o in the arch-msm makefile
Note: the backported drivers and compatibility-patches are located in a separate backports/ subdirectory
Sorry, this is work in progress and contains some hacks, to be cleaned up later
--> https://github.com/LineageOS/androi...1...Tom1000:lineage-17.1-driver-backport-v5.8
Vendor blobs / device z3(c): removed proprietary firmware and replaced that by publicly available firmware for bcm4339 on linux-firmware.git
z3c --> https://github.com/LineageOS/androi.../lineage-17.1...Tom1000:lineage-17.1-brcmfmac
z3 --> https://github.com/LineageOS/androi.../lineage-17.1...Tom1000:lineage-17.1-brcmfmac
Shinano-common: Use qcwcn instead of bcmdhd WLAN device, serve wpa_supplicant_overlay.conf
--> https://github.com/LineageOS/androi.../lineage-17.1...Tom1000:lineage-17.1-brcmfmac
msm8974-common: raise wpa_supplicant version (unknown if we need that) and update sysfs node for MAC address
--> https://github.com/LineageOS/androi.../lineage-17.1...Tom1000:lineage-17.1-brcmfmac
As a follow up, the driver seems to work quite stable already. I still have issues with nl80211 private commands, as a mainline brcmfmac does not seem to accept command strings passed via a libnl control socket like this:
qcwcn/wpa_supplicant_8_lib/driver_cmd_nl80211.c
@vknecht : I've seen your backporting work for the Xperia X. How does this work for Loire with SODP? Does e.g. a "set country code request" work for you, and if so, can you give me a hint?
I need some feedback from people with a Z3/Z3c/Z3Dual to see if the new builds work in affected countries, where 5GHz wifi is not working on current custom ROMs like e.g. LineageOS 17.1. I would appreciate if you test one of the builds below and send me a full log.
WARNING: The following builds are for debugging purpose only. Do not use them as a daily driver, as they have SELinux disabled and create excessive log entries. This ROM is not stable, some features are not yet implemented.
Xperia Z3 (D6603):
lineage-17.1-20201227-UNOFFICIAL-z3.zip
drive.google.com
Xperia Z3c (D5803):
lineage-17.1-20201227-UNOFFICIAL-z3c.zip
drive.google.com
Xperia Z3Dual (D6633) Update 10Jan2021:
lineage-17.1-20210110-UNOFFICIAL-z3dual.zip
drive.google.com
Z3Dual build has SELinux enabled already
If possible, please follow these steps:
Install ROM with TWRP for Android 10 or Lineage Recovery for 17.1
If possible, factory reset the device. Be sure to get rid of all former Magisk modules which try to set country codes etc. (if applicable).
Make sure a a local SIM card is inserted.
Boot the device. Enable mobile data and enable wifi. Connect to a 5GHz capable access point or router.
Optional: Increase log buffer size. This may be required as the kernel is set to verbose logging, creating large logfiles. You can do this via settings/developer options or via adb:
adb logcat -G 8M
Get close to the access point or router, so that the device would prefer 5GHz over 2.4GHz.
Reboot the device and let wifi connect. Check if device uses a 5Ghz connection. (Ignore bandwith / speed for now.)
Create a logfile, e.g. with this command via adb:
adb shell logcat -d -b all > mylog.log
The logfile may contain private information, so I recommend not to post them public. Together with the ligfile I would like to know
a) Wifi 5GHz working?
b) The country in which you have tested this.
nice work bro.
i live in iran and in this build my Z3 Dual detects wifi networks while the sim card is also connected.
but in 10 Jan 2021 update my phone can't detect my router's wifi unfortunately while the previous build could do it without problems.
hotspot turns on on both 2.4GHz and 5GHz.
in this new build cellular network and data are working.
Thanks @TheShadowOfAGhost20 !
Can you please run a root shell (E.g. by connecting via ADB, run adb root, then adb shell) and then
$> iw wlan0 scan → scan for networks
and then look if your access point is found?
Furthermore, can you please check which WiFi channel this particular router ist set to, and if possible the bandwidth?
Mr.Tom_Tom said:
Thanks @TheShadowOfAGhost20 !
Can you connect via ADB, run adb shell and then
$> iw wlan0 scan → scan for networks
and then look if your access point is found?
Furthermore, can you please check which WiFi channel this particular router ist set to, and if possible the bandwidth?
Click to expand...
Click to collapse
i did that but got this error: "/system/bin/sh: iw: inaccessible or not found"
but i found the cause: my wifi channel was set to 12. i changed it and then got detected!
TheShadowOfAGhost20 said:
i did that but got this error: "/system/bin/sh: iw: inaccessible or not found"
Click to expand...
Click to collapse
Sorry I forgot to write that you have to do this as root, I edited the post accordingly.
TheShadowOfAGhost20 said:
i found the cause: my wifi channel was set to 12. i changed it and then got detected!
Click to expand...
Click to collapse
Tha sounds reasonable. However, Channel 12 should be usable in IR.
Mr.Tom_Tom said:
Sorry I forgot to write that you have to do this as root, I edited the post accordingly.
Tha sounds reasonable. However, Channel 12 should be usable in IR.
Click to expand...
Click to collapse
channel 13 has detection problem too. the others are OK
.sorry erroneous post
New buildsFeedbacks have been positive so far, so here are some updated builds.
Lineage Sources* as of 20 March 2021
Kernel sources* based on Linux 3.4.113 with backported wifi from 5.8.18 plus cherry-pick of the following changes:
bluetooth: fixed #ifdef'ed PM callbacks ("BTLowPower" wakelock) 50f16d16b32871c5ce97b029e68692008c848bb2
SELinux enforcing
Build as userdebug, normal loglevels
* For links to sources see 1st post. Z3Dual does not have official Lineage17.1 sources yet, bringup is in progress.
Xperia Z3 (D6603):
HiDrive
hidrive.ionos.com
md5: d7aaf1fea120df3e2aad10b3a2d32226
Xperia Z3c (D5803):
HiDrive
hidrive.ionos.com
md5: 456ff87441c3a63e8dc8c7a8d03bdf39
Xperia Z3Dual (D6633):
HiDrive
hidrive.ionos.com
md5: 1848681c82d608f3212f1ace621327cb
As always, feedback is welcome.
Has anyone found a bug/installed this latest build yet? lineage-17.1-20210320-UNOFFICIAL-z3dual
Finding this super stable.. The only thing that does not work for me is the advanced boot recovery that goes back into system, But that's a known issue.
Mr.Tom_Tom said:
New buildsFeedbacks have been positive so far, so here are some updated builds.
Lineage Sources* as of 20 March 2021
Kernel sources* based on Linux 3.4.113 with backported wifi from 5.8.18 plus cherry-pick of the following changes:
bluetooth: fixed #ifdef'ed PM callbacks ("BTLowPower" wakelock) 50f16d16b32871c5ce97b029e68692008c848bb2
SELinux enforcing
Build as userdebug, normal loglevels
* For links to sources see 1st post. Z3Dual does not have official Lineage17.1 sources yet, bringup is in progress.
Xperia Z3 (D6603):
HiDrive
hidrive.ionos.com
md5: d7aaf1fea120df3e2aad10b3a2d32226
Xperia Z3c (D5803):
HiDrive
hidrive.ionos.com
md5: 456ff87441c3a63e8dc8c7a8d03bdf39
Xperia Z3Dual (D6633):
HiDrive
hidrive.ionos.com
md5: 1848681c82d608f3212f1ace621327cb
As always, feedback is welcome.
Click to expand...
Click to collapse
hi mr.tom. it's perfect as always, found no bug except wifi signal power, it's weak compared to stock roms but there was no difference in speeds. maybe it's because of wifi icon that shows little weaker signal.
and about overheating: i didn't test this build for long but while working with it i have noticed that my device is cooler than previous builds, maybe it's because of this new kernel.
i have recorded 4k for about 7 minutes then my phone rebooted i think that was because of too much heat, then i've reinstalled stock rom, however, stock rom's camera won't let me record much and the app shuts down because of heat, so i can't find out if stock rom can record 4k at least without rebooting.
i need to test this build for more time i hope the heating is now gone
and one question: can you port cyberian camera mod for these roms? or is that possible?
netwave said:
Has anyone found a bug/installed this latest build yet? lineage-17.1-20210320-UNOFFICIAL-z3dual
Finding this super stable.. The only thing that does not work for me is the advanced boot recovery that goes back into system, But that's a known issue.
Click to expand...
Click to collapse
lineage os recoveries have these problems yet, there's no fix for that, only the developer can fix it. currently the twrp works if you flash it to FOTAKernel partition but i think the twrp is useless because it doesn't install these builds.
Surely better to do: fastboot boot recovery-20201012-TESTING-z3dual.img rather than a "flash" recovery. What would be the point in flashing a recovery if its not working.
Hey
Thanks @Mr.Tom_Tom for new build and @TheShadowOfAGhost20 for testing dev builds!
today i installed the new release
but i have some problems with recovery and boot
after installing Lineage i cannot boot to recovery again
i tried adb, android advanced boot options and "fastboot boot image.img"
none of them taken me to recovery mode
so i needed to install Magisk , OpenGApps , and rom itself with adb sideload and reboot to system because i can't boot to recovery again
i'm now installing my apps for daily usage testing - i need about one or two week to test and use and see if anything is wrong or not
for now WiFi problem is gone , i have full wifi access and both sims antenna
again , thanks to everyone puts effort on this project (and sorry for bad English)
i will update this post if i found anything
navidmafi said:
today i installed the new release
but i have some problems with recovery and boot
after installing Lineage i cannot boot to recovery again
i tried adb, android advanced boot options and "fastboot boot image.img"
none of them taken me to recovery mode
Click to expand...
Click to collapse
If your going to settings\system\developer options\advanced restart\power\restart recovery , Forget it! this method doesn't work for now, & will only boot you back into Lineage. It's an issue that hopefully get's fixed in the future.
But here's a better way of entering recovery without having to flash it...
Check all your drivers are installed correctly & make sure you have the correct recovery to hand.
Here's what I Command:
adb devices
adb reboot bootloader
fastboot devices
fastboot boot recovery-20201012-TESTING-z3dual.img
Good luck!
Hey again
Thanks to @netwave i can now boot to recovery without problems by going to fastboot from adb , and booting image directly by "fastboot boot"
while using devices after installing new release , i have a problem with WiFi connectivity
when i lock the screen by power button , the wifi disconnects
for example i use whatsapp a lot and when screen is locked wifi is not connected
i checked power settings - and even set the battery profile to "Quick" (and battery saver is off) but it did not help
is this a bug or a feature?
navidmafi said:
Hey again
Thanks to @netwave i can now boot to recovery without problems by going to fastboot from adb , and booting image directly by "fastboot boot"
while using devices after installing new release , i have a problem with WiFi connectivity
when i lock the screen by power button , the wifi disconnects
for example i use whatsapp a lot and when screen is locked wifi is not connected
i checked power settings - and even set the battery profile to "Quick" (and battery saver is off) but it did not help
is this a bug or a feature?
Click to expand...
Click to collapse
Have you tried without Magisk installed? Don't use v22.0 what ever you do as it disables WiFi
Ow
I'm using Magisk and it is version 22.0
and even root not works
should i reflash ?
Edit : Ok i'm flashing again now
navidmafi said:
Ow
I'm using Magisk and it is version 22.0
and even root not works
should i reflash ?
Click to expand...
Click to collapse
Install the Magisk uninstall.zip from recovery
when your back in Lineage your still have a disabled WiFi as Magisk does not uninstall correctly.
So Install the original boot extracted from the Lineage.zip to get things working again.
- adb devices
- adb reboot bootloader
- fastboot devices
- fastboot flash boot boot.img
- fastboot reboot
Then your be sorted.
{
"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"
}
Code:
* Your warranty is now void.
*
* 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! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
This is a TWRP 3.7.0_11-0 recovery for the Helios P60 based Atom L (Atom_L) and Atom XL (Atom_XL), two rugged Android phone released by Unihertz in July 2020.
This recovery supports both devices as well as both regional variants!
You need to make sure which device and variant you need!
Team Win Recovery Project, or twrp for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Warning
Backup your data before trying to decrypt inside TWRP.
Decrypting could potentially lock you out from your ROM. I learned that the hard way.
Although I'm quite certain that I fixed the underlying issue it's better to be save than sorry.
Not Working
You tell me
Releases
Atom L EEA (european union)
Atom XL EEA (european union)
Atom L TEE (non-european union)
Atom XL TEE (non-european union)
How to install
How to Update
Links
LineageOS
Common device tree
Device tree Atom L EEA (european union)
Device tree Atom XL EEA (european union)
Device tree Atom L TEE (non-european union)
Device tree Atom XL TEE (non-european union)
Bug reporting
Spoiler: Changelog
2023-04-16
* Decryption is working now
2022-10-05
* Modified the second touchpad driver to work in recovery mode too
2022-07-15
* Switched to TWRP 3.6.2_11-0
* July 2021 vendor updates included (needs vendor to be upgraded manually)
* Decryption is not working (for now)
2022-01-30 (Only for Atom L TEE)
* Changed the patched kernel to the one from the Atom L EEA
2021-08-10
* Security string set to 2099-12-05
2021-06-16
* May vendor updates included (needs vendor update to be applied beforehand)
2021-05-11
* Decryption is fully working now
2021-04-15
* Version bump to TWRP 3.5.2
* Combining the work for the Atom L and XL
2021-03-11
* Version bump to TWRP 3.5.1
* Decryption is working now (with the exception of the user scope like /data/media/0 & others)
2021-02-18
* trustkernel daemon (teed) is working now, decryption still doesn't work
* adb is working now without the need to deactivate mtp
2021-01-15
* Timezone set to europe by default
* Vibration is back (but turned down)
2021-01-14
* Sideload is working
* Install zip/img is working
* Data decryption is not working
* MTP is not working
* ADB is working (MTP needs to be disabled)
Help from other developers is certainly welcome.
Credit and Thanks
TWRP team
@PeterCxy for starting the work on the Atom L
Enjoy!
XDA:DevDB Information
TWRP 3.7.0_11-0 for Unihertz Atom L and XL, ROM for the Android General
Contributors
a-dead-trousers
Source Code: https://github.com/ADeadTrousers/twrp_device_Unihertz_Atom_LXL
ROM OS Version: Android 11
ROM Kernel: Linux 4.x
Based On: TWRP
Version Information
Status: Alpha
Created 2021-01-15
Last Updated 2022-10-05
Hello a-dead-trousers
I bought an Atom L and want to install Lineage OS on it. As a newbie to Customs ROM, I'm trying to get ahead with the details here. ADB and Fastboot drivers on the PC are installed and I'm trying to work through points 1. Unlocking and 2. Installing TWRP recovery but am running into difficulties on my device and hoping for help: after typing `adb reboot bootloader` the phone's screen gets black with the indication '=> FASTBOOT mode...' in the lower left corner in very small caracters. Any further command on the prompt leads to an error < waiting for any devices > and < Too many open files in system > See attached image. I have to press the Power button to restart the official Android OS. How can I overcome this issue?
Honestly I normally also use Windows but for this work I switched to Linux.
`Fastboot mode` on phone screen is correct.
If the phone is in fastboot mode, connected to your PC and you type `fastboot devices` you should see it's serial number along with `fastboot` indicating the mode. Like you see it with `adb devices`.
So my guess is a problem with the windows drivers especially the fastboot portion.
Have you tried it with the MTK drivers?
https://github.com/ADeadTrousers/android_device_Unihertz_Atom_XL/blob/master/docs/HOW-TO-SPFLASH.md
Thank you for the quick response, @a-dead-trousers!
I installed the MTK drivers on my Win 8.1 PC from the link. I am still using this ADB driver . This info I got from here and also the ADB Tools needed. The result is pretty much the same. See images.
I must also mention that a pulsing sound (device driver sound) is heard when I enter `adb reboot bootloader` . This was also the case when i tried it before. The sound does not stop; I can only turn it off by pressing the Power button and starting the official OS again.
What am I doing wrong?
Sadly fastboot is quite different than adb.
In the case of adb there is a running application (adb daemon) that's communicating with your computer. It's part of the OS and can be rplaced/updated.
Fastboot on the other hand is running in a low-level hardware environment and cannot be (easily) replaced/updated.
"Hearing" sound while the phone is connected to the PC often happens when there is some sort of stray electric current or a short circuit.
To rule out a problem with your PC I would suggest you try it on another one (preferably with linux to even rule out windows as culprit)
Or try the official drivers: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Thanks so far. I had already installed the official drivers, as you can see in the prompts screen prints (version r30.0.5).
Is a Linux installation in a virtual machine (Virtual Box) promising or would the underlying Windows OS continue to cause possible problems with Fastboot? Is a direct linux installation mandatory?
How could Fastboot be updated even if it is more difficult? I think somehow Fastboot is ticking around.
I would like to try my Windows laptop first instead of the desktop. Installing Linux natively would only be the very last variant because of the considerable additional effort.
Logiciel-XDA said:
Thanks so far. I had already installed the official drivers, as you can see in the prompts screen prints (version r30.0.5).
Click to expand...
Click to collapse
Sorry I've overlooked that.
Logiciel-XDA said:
Is a Linux installation in a virtual machine (Virtual Box) promising or would the underlying Windows OS continue to cause possible problems with Fastboot? Is a direct linux installation mandatory?
Click to expand...
Click to collapse
Windows would need to provide the drivers so it would still interfere. I don't know of any VM that supports native USB passthrough but I could be wrong. So a linux installation would be mandatory for now.
Logiciel-XDA said:
How could Fastboot be updated even if it is more difficult?
Click to expand...
Click to collapse
That would require a serial interface (COM) or an unsoldering of the chip to flash it with an EPROM burner.
Logiciel-XDA said:
I think somehow Fastboot is ticking around.
Click to expand...
Click to collapse
Honestly I'm more concerned (or should I say in hopes) about the windows inbetween. The only other option would be a problem with the phone itself (see previous answer) and to get this through Unihertz support you would need to confess that you tried to tinker with the internals while the phone itself is operating just fine. If I were Unihertz I would say "Sorry, no replacement for you".
Logiciel-XDA said:
I would like to try my Windows laptop first instead of the desktop. Installing Linux natively would only be the very last variant because of the considerable additional effort.
Click to expand...
Click to collapse
Don't you have a friend or colleague with a linux machine you could ask for help? Or you could buy a RasberryPi or a similar device. Those are not so expensive and on the plus side you could use them afterwards for many other things like a home streaming server.
I followed the instructions exactly, but now the phone loops on the unihertz boot screen with the unlocked warning. It won't even turn off. No button combination does anything, except that volume up + power makes it reboot faster.
On Linux, using the latest android tools.
Is there any way to at least stop it from constantly booting? Is it possible to get it into fastboot any other way?
EDIT: For anyone else who has this problem, the manufacturer provides drivers and tools to re-flash the entire phone to stock. All the relevant links are here. This didn't work on my Windows machine, but it worked using Linux.
My phone has now been flashed back to stock, most stuff restored using Google's backup, but I guess I won't try this TWRP again, and stick to the LineageOS recovery instead.
uzalu said:
I followed the instructions exactly, but now the phone loops on the unihertz boot screen with the unlocked warning. It won't even turn off. No button combination does anything, except that volume up + power makes it reboot faster.
On Linux, using the latest android tools.
Is there any way to at least stop it from constantly booting? Is it possible to get it into fastboot any other way?
EDIT: For anyone else who has this problem, the manufacturer provides drivers and tools to re-flash the entire phone to stock. All the relevant links are here. This didn't work on my Windows machine, but it worked using Linux.
My phone has now been flashed back to stock, most stuff restored using Google's backup, but I guess I won't try this TWRP again, and stick to the LineageOS recovery instead.
Click to expand...
Click to collapse
Hi.
Sorry to hear that. This TWRP release was intended for those who had problems with the LineageOS recovery (stuck on green line on reboot and so on). I have an Atom XL so I cannot test it with 100% certainty but as the two devices are quite similar I myself had no problems with this exact TWRP on my own device.
If you stuck in a recovery "bootloop" you could try to press vol-down to boot into the bootloader (not fastboot). But the menu is in chineese.
For the TWRP release for the Atom XL I got this reply:
https://forum.xda-developers.com/t/...tom-xl-alpha-2021-01-15.4218695/post-84402809
Maybe this will help you.
In the meantime I'm planning to build a release without accessing the "/data" partition. Since it is encrypted and I wasn't able to find the correct setting for unencryption yet it doesn't make any sense to have it anyway. Also when tinkering with the encryption settings I wasn't able to boot into recovery too. So I believe this is the source of most of the problems.
Until then, stay tuned.
Cheers.
ADT
Also, I made a more up-to-date tutorial with the latest versions (drivers & tool) for flashing the stock rom:
https://github.com/ADeadTrousers/an...tom_XL/blob/master/docs/HOW-TO-FLASH-STOCK.md
If your device is stuck in a "bootloop" that is no problem at all because on every restart there is a 2 - 3 sec. time frame for the flashing to start.
Now Atom L and Atom XL are supported as well as both regional variants EEA (european union) and TEE (non-european union)
I just updated my Lineage releases but I've to postpone their TWRP counterparts.
Why, you ask? Well I had a major breakthrough on the decryption front. I'm now able to decrypt /data completely. But as always, with great power comes great responsibility ... or in this case great destruction.
Well it's true I was able to decrypt /data in TWRP but right after that LOS wasn't able to do the same anymore. Somehow running a full decrypt (by providing your pattern/password) on TWRP "destroys" all the information needed by LOS to decrypt. After that only TWRP is able to decrypt. Maybe that's a "security" feature of trustkernel ... I don't know yet.
Anyway, I had to completely reset my phone (even lost some data cause google drive couldn't load my backups).
Therefore I'm not going to release any updates until I figured out how to prevent this catastrophe for good.
I was able to fix the issue with decryption and locking yourself out from your ROM:
Decryption of /data in TWRP messes up password recognition on LOS · Issue #4 · ADeadTrousers/twrp_device_Unihertz_Atom_LXL
Right after providing my pattern in TWRP /data got decrypted but also LOS wasn't able to decrypt any more. My pattern always gets rejected. As far as I can tell /mnt/vendor/persists/t6 gets changed...
github.com
So now it's save enough for me to post an update.
But be warned:
The problem could still resurface so backup your data beforehand. It's better to be save than sorry.
I've been wasting so much time now in trying to get MTP working from within TWRP only to find out that under Windows it works just fine.
So it's only a problem under Linux (either only on Ubuntu/Debian or general I don't know)
I need to get some fresh air now or I'll go ape ****.
Hi! I've just bought Atom L and want to do some mods... Your how-to manual is awesome, thanks for that!
I'm just at the beginning on my way to flash LineageOS, but I can't get TWRP to work.
All of your TWRP versions are crashing on my device (european L, fresh new, no data), attaching adb log. I'm not sure where exactly the problem is...
ofc I've flashed vbmetas. The older lineageos TWRP image from peterCxy not just crashes, but also reboots phone, so i have no log....
I'm thinking about trying to build my own TWRP image when I'll have free time (but did this last time many years ago), but maybe it is just some small bit to tweak to make it work on my device? TIA!
edit: cannot attach log, dont know why...: https://mega.nz/file/JEAWwZgD#0EtOnG2_DNOry40D3PL6rGsJw7HUCcnKTBNYtu3bOj0
Code:
Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0 in tid 357 (recovery), pid 357 (recovery)
This looks like a null-pointer exception (0x0) within TWRP main process (recovery).
And it's trying to do it 6 times and then gives up.
Can you try to provide a kernel dump?
Code:
adb shell dmesg > dmesg.log
or maybe even download the TRWP log?
Code:
adb pull /tmp/recovery.log
Thx for fast reply! Here are dmesg and recovery logs:
319.1 KB file on MEGA
mega.nz
9.7 KB file on MEGA
mega.nz
Now it looks its crashing when composing gui, and its not giving up, it is in loop, not only 6 times
Recovery is rebooting on 'Checking resolution...'
And according to dmesg the init script keeps repeating in the end.
You said you did everything on a 'fresh new, no data'? How did you do that?
At least you'd need to activate oem-unlock from within the rom and that would 'initialize' data.
It is brand new phone, never switched on wifi or sim. I got it today, just unboxed it, and started with enabling developer tools, adb enabled, oem unlocked and then fastboot flashing unlock, vbmetas and TWRP flash.
I don't know, maybe I will connect it to wifi and try to update to newest stock firmware, then try again.
I'm just little concerned about this section, which is telling me I have debug build kernel. but maybe it is OK, original system works OK.
Code:
[ 0.000000] -(0)[0:swapper]**********************************************************
[ 0.000000] -(0)[0:swapper]** NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE **
[ 0.000000] -(0)[0:swapper]** **
[ 0.000000] -(0)[0:swapper]** trace_printk() being used. Allocating extra memory. **
[ 0.000000] -(0)[0:swapper]** **
[ 0.000000] -(0)[0:swapper]** This means that this is a DEBUG kernel and it is **
[ 0.000000] -(0)[0:swapper]** unsafe for production use. **