Database Info

Lost Wi-fi, could be hardware, HBOOT, radio?

Hi all,
I have been running a 2.3.x ROM for a few weeks (HyperSensation, an AOSP rom) very happily until a few days ago, I realized that it didn't connect to wifi anymore.
When I go to WiFi to turn it on, it think for a while and does revert back to unchecked. If I go look at the scan, it force closes after a while.
I don't believe this is ROM specific as I did wipes, Super-Wipes, installed the version of HS I had, a newer version, other ROMs, etc.
The same behavior happens every time I try to turn on Wifi.
I am running:
T-mobile HTC Sensation
10.56.9035.00P_10.14.9035.01_M
HBOOT-1.17.111
PYRAMID PVT SHIP S-OFF RL
eMMC-Boot
Clockwork Recovery v.5.0.2.0
Any idea? Diagnosis, tips, solutions?

Should I try to upgrade the hboot and radio, could it have gotten corrupted in some fashion?

Try installing the "first-time" kernel from the ARHD Rom thread.

What will that do? Reset my wifi hardware in some fashion? Should I flash just the kernel or the entire ROM?

I flashed the latest ARD and it didn't change a thing.
Through the Sense dialog, it tries to scan and then fails (Unable to scan for networks).
Logcat says things like:
Code:
E/WifiHW ( 309): Supplicant not running, cannot connect
V/WifiStateTracker( 309): Supplicant died unexpectedly
I/WifiHW ( 309): wifi_close_supplicant_connection
D/WifiStateTracker( 309): Reset connections and stopping DHCP
E/SettingsWifiLayer( 581): Unable to scan for networks
D/WifiService( 309): enable and start wifi due to updateWifiState
D/WifiService( 309): enable and start wifi due to updateWifiState
D/WifiStateTracker( 309): Reset connections and stopping DHCP
D/NetUtils( 309): ifc_get_info addr=0 !
D/NetUtils( 309): ifc_get_info addr=0 !
D/WifiStateTracker( 309): Disabling interface
D/WifiStateTracker( 309): Disabling interface
D/WifiService( 309): setWifiEnabledPersist false persist = true getCallingPid() = 309
D/WifiService( 309): setWifiEnabled =falsemAirplaneModeOverwridden =false
D/WifiStateTracker( 309): restart wifi at die
D/WifiService( 309): setWifiEnabledPersist true persist = true getCallingPid() = 309
D/WifiService( 309): setWifiEnabled =truemAirplaneModeOverwridden =false
D/WifiService( 309): setWifiEnabledBlocking:Disable Wifi
D/WifiStateTracker( 309): Reset connections and stopping DHCP
D/NetUtils( 309): ifc_get_info addr=0 !
I/NetSharing_NSReceiver( 581): customizedNS:true
D/NetSharing_NSReceiver( 581): onReceive : android.net.wifi.WIFI_STATE_CHANGED
D/NetSharing( 581): wifi enabled change, state = false
...
D/WifiStateTracker( 309): Disabling interface
I/WifiHW ( 309): wifi_stop_supplicant enter
I/WifiHW ( 309): wifi_stop_supplicant end right 1
I/WifiHW ( 309): wifi_unload_driver enter
I/WifiHW ( 309): rmmod
I/WifiHW ( 309): check_driver_loaded
I/WifiHW ( 309): wifi_unload_driver end right 2
D/WifiService( 309): setWifiEnabledBlocking:Enable Wifi
I/WifiHW ( 309): wifi_load_driver enter
I/WifiHW ( 309): check_driver_loaded
I/WifiHW ( 309): insmod

I have the exact same problem after upgraded my ARHD 4.1.11 to 4.1.12. Everything worked well however I could not turn on the wifi

Seems, from a cursory search in these forums that this happens to quite a few people and I haven't found a definite solution. Seems the wifi adapter gets 'bricked' in some fashion and there is no way to revive it.
Can anyone suggest a way to diagnose, a more technical explanation of what's happening?

gnapoleon said:
What will that do? Reset my wifi hardware in some fashion? Should I flash just the kernel or the entire ROM?
Click to expand...
Click to collapse
i had a similar problem after upgrading to ARHD and my wifi wouldn't turn on at all. Then i tried the first_time kernel (i think from the same ARHD topic but i might be wrong). I just flashed the kernel and it fixed my wifi.

I agree,
flash the first time kernel then flash hypersensation 1.6 if u like cm7
check all md5 sums first

Did that once and it worked but then, after flashing another ROM which worked with Wi-fi for an hour or so, the same problem happened again.
Now I can't get it to work again, flashing ARHD 3.x. What is it supposed to be doing that other ROMs don't do and why doesn't it help (trying to understand why it didn't stick and why it doesn't help anymore).

I am at my wits end. I superwiped a few times, installed ARHD 3.x again, which got the wifi working. I then installed another rom (Virtuous Inquisition ICS), wifi worked for a few minutes then failed again.
Restore from ARHD 3.x backup and the wifi fails as well.

alireza_simkesh said:
Try installing the "first-time" kernel from the ARHD Rom thread.
Click to expand...
Click to collapse
Why are you telling him to flash a sense kernel for a aosp rom. It does not work and now he doesn't have wifi at all

gnapoleon said:
Should I try to upgrade the hboot and radio, could it have gotten corrupted in some fashion?
Click to expand...
Click to collapse
Just flash faux or showp kernel for AOSP/CM7 for the rom and your wifi should be back to normal. Wifi is a kenel related issue not rom

But why would a basic rom that works for everyone give me trouble with its built-in kernel?
I never flashed a kernel separately from a ROM in trying to get Wi-fi back. Why does a given rom/kernel combination that works for many not work for me?
I tried:
ARD 3.x
ARD 6.x
Hypersensation 1.5 & 1.6
Virtuous Inquisition
....
ARD 3.x is really the only one that gives me wifi for a short while before it fails again.
If I flash an ICS (not pure AOSP, but the ones with Sense removed), what should I expect to flash as a kernel?

At this point, I am ready to give up and ditch the sensation. I am thinking it might be a hardware issue. I have the latest firmware (HBoot 1.23) and have tried dozens of different roms. After Superwipes, and wipes, erasing the sdcard, re-partitioning and everything else I could think off, I can at best get wifi working on first boot for a few seconds.
GB or ICS, sense, senseless or real AOSP, it doesn't matter, I can never get it to work.
Does anyone have a last advice before I head to the Verizon store?

This is what my boot screen looks like. No ROM 2.3.x or ICS, sense, senseless or AOSP have a working wifi for me (T-mobile sensation):
{
"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"
}
Some more logcat:
Code:
E/WifiStateMachine( 229): Failed to reload STA firmware java.lang.IllegalStateException: Error communicating to native daemon
W/CommandListener( 119): Failed to retrieve HW addr for wlan0 (No such device)
D/CommandListener( 119): Setting iface cfg
E/WifiStateMachine( 229): Unable to change interface settings: java.lang.IllegalStateException: Unable to communicate with native daemon to interface setcfg - com.android.server.NativeDaemonConnectorException: Cmd {interface setcfg wlan0 0.0.0.0 0 [down]} failed with code 400 : {Failed to set address (No such device)}
D/NetworkManagementService( 229): rsp <213 00:00:00:00:00:00 0.0.0.0 0 [down]>
D/NetworkManagementService( 229): flags <[down]>
I/wpa_supplicant( 2785): rfkill: Cannot open RFKILL control device
E/wpa_supplicant( 2785): Could not read interface wlan0 flags: No such device
E/wpa_supplicant( 2785): WEXT: Could not set interface 'wlan0' UP
E/wpa_supplicant( 2785): wlan0: Failed to initialize driver interface

blahbl4hblah said:
Why are you telling him to flash a sense kernel for a aosp rom. It does not work and now he doesn't have wifi at all
Click to expand...
Click to collapse
didn't notice he had aosp rom.
Just change ur rom to ARHD and flash first time kernel.
gnapoleon said:
At this point, I am ready to give up and ditch the sensation. I am thinking it might be a hardware issue. I have the latest firmware (HBoot 1.23) and have tried dozens of different roms. After Superwipes, and wipes, erasing the sdcard, re-partitioning and everything else I could think off, I can at best get wifi working on first boot for a few seconds.
GB or ICS, sense, senseless or real AOSP, it doesn't matter, I can never get it to work.
Does anyone have a last advice before I head to the Verizon store?
Click to expand...
Click to collapse
Did u try first-time kernel?

From what I understand, first time kernel is included in ARHD 3.x (GB) & 6.x (ICS) ROMs. Is that correct? If so, I have tried it as part of me trying to get Wifi working with those ROMs?
If it's not included in those ROMs, could you send me a link? Is it a kernel I just use once and then overwrite? Is it Sense 3.x only, does it apply to ICS Senseless ROMs or AOSP roms (GB or Tripp)?
Thanks for your help,
Erik

From what I could gather, at this point, my wifi is busted. I restored the tmobile RUU and it still exhibits that behavior. Dead sensation. Hello Gnex on Verizon.

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

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

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

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

Seems good, will try
Sorry for my bad English

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

reserved........

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[APK][Flash Zips WITHOUT a Recovery!]Flash Gordon: an Edify to Bash parser/translator

THIS IS A WORK IN PROGRESS, CURRENTLY AT A VERY EARLY STAGE OF DEVELOPMENT​
What is Flash Gordon ?
In laymen's words, Flash Gordon is an apk which allows you to flash any flashable zip (except for Roms) without having a recovery installed.
You just point it to the zip you want to flash, (be it a kernel, a mod, a gapps package, a modem, a RIL, a recovery...) and it will interpret the updater-script of this package and install its content just like a recovery would.
How does it work ?
Here is what happens step by step :
You tap the "select a zip" button, select the built-in file explorer to select the zip you want to flash
Flash Gordon will first extract this zip, depending on its size it can take a little time
When you press the "Flash Now" button, Flash Gordon will locate the updater-script and start translating it into shell code, line by line
It will output the resulting translated bash script on your sdcard and execute it, thus installing the zip's content
The app creates a notification, just tap on it to reboot
In order to achieve those last 2 steps, I'm writing a full Edify to Bash parser and translator.
Here is the list of all the Edify commands this parser can currently process and what their respective bash translation is (in green), using examples:
(more will be added over time, this is really just a draft)
By no means am I a bash expert, so if you have suggestions for better bash equivalents of any edify commands please post them
Code:
package_extract_file("path/to/source/file.txt", "/path/to/destination/file.txt");
[COLOR="DarkGreen"]busybox cp -fp /path/to/source/file.txt /path/to/destination/file.txt[/COLOR]
package_extract_dir("/source/folder", "/destination/folder");
[COLOR="DarkGreen"]busybox cp -rfp /source/folder/* /destination/folder[/COLOR]
set_perm(0, 2000, 0755, "/file/or/folder");
[COLOR="DarkGreen"]chown 0:2000 /file/or/folder
chmod 0755 /file/or/folder[/COLOR]
set_perm_recursive(0, 2000, 0644, 0755, "/path/to/set/permissions/recursively");
[COLOR="DarkGreen"]chown -R 0:2000 /path/to/set/permissions/recursively
chmod 0644 /path/to/set/permissions/recursively
chmod -R 0755 /path/to/set/permissions/recursively
[/COLOR]
delete("file/to/delete");
[COLOR="DarkGreen"]busybox rm -f /file/to/delete[/COLOR]
run_program("/script/to/run.sh");
[COLOR="DarkGreen"]sh /script/to/run.sh[/COLOR]
mount("ext4", "EMMC", "/dev/block/mmcblk0p9", "/system");
[COLOR="DarkGreen"]busybox mount -o rw,remount -t auto /system [I](will soon change to -t mmcblk0p9 or whichever mount point is in the updater-script)[/I][/COLOR]
unmount("/system");
[COLOR="DarkGreen"]busybox mount -o remount,ro /system[/COLOR]
symlink("busybox", "/system/xbin/[", "/system/xbin/[[",
"/system/xbin/adjtimex", "/system/xbin/arp", "/system/xbin/ash",
"/system/xbin/awk", "/system/xbin/base64", "/system/xbin/basename",
"/system/xbin/bbconfig", "/system/xbin/blkid", "/system/xbin/blockdev",
"/system/xbin/brctl", "/system/xbin/bunzip2", "/system/xbin/bzcat",
"/system/xbin/bzip2", "/system/xbin/cal", "/system/xbin/cat",
"/system/xbin/catv", "/system/xbin/chattr", "/system/xbin/chgrp",
"/system/xbin/chmod", "/system/xbin/chown", "/system/xbin/chroot",
"/system/xbin/clear", "/system/xbin/cmp", "/system/xbin/comm",
"/as/many/lines/as/you/want");
[COLOR="DarkGreen"]ln -s busybox /system/xbin/[ /system/xbin/[[
/system/xbin/adjtimex /system/xbin/arp /system/xbin/ash
/system/xbin/awk /system/xbin/base64 /system/xbin/basename
/system/xbin/bbconfig /system/xbin/blkid /system/xbin/blockdev
/system/xbin/brctl /system/xbin/bunzip2 /system/xbin/bzcat
/system/xbin/bzip2 /system/xbin/cal /system/xbin/cat
/system/xbin/catv /system/xbin/chattr /system/xbin/chgrp
/system/xbin/chmod /system/xbin/chown /system/xbin/chroot
/system/xbin/clear /system/xbin/cmp /system/xbin/comm
/as/many/lines/as/you/want
(not sure about this one, please correct me if I'm wrong, I could change to [I]ln -s argument/number/1 argument/number/2[/I] as many times as required if needed)[/COLOR]
write_raw_image("/tmp/boot.img", "mmcblk0p5");
[COLOR="DarkGreen"]dd if=/tmp/boot.img of=/dev/block/mmcblk0p5[/COLOR]
This is just a proof of concept for the moment, I'm aiming at adding all the possible Edify commands, and maybe doing it backwards (Bash2Edify) in the future, too.
Screenshots
This is from the apk I use for debugging, so the UI is pretty barebones atm, it will quickly evolve to something more fancy and featureful
{
"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"
}
Contribute
Flash Gordon is fully Open-Source, and contributions are more than welcome!
You can check-out the full source code on my github at : https://github.com/Androguide/FlashGordon
This app depends on the following Open-Source libraries :
My fork of the CardsUI library by [URL="https://plus.google.com/101314917101345770417/posts"]Nadav Fima[/URL]
aFileChooser by Paul Burke
Frequently Asked Questions
Q: Why can't I flash a Rom with Flash Gordon ?
A: Because when some system files are replaced while the device is running, it causes it to crash and will stop in the middle of the installation, resulting in a bootloop.
Q: Where can I see the bash script translation of the package I selected ?
A: After tapping the Flash Now button, head to /sdcard/RecoveryEmulator/tmp/flash_gordon.sh
The full translation is also output to the logcat while flashing.
Q: I select a flashable zip but it tells me it is not valid or that it's not a zip package, why ?
A: Make sure that there is no whitespace in the name of the zip package you're trying to flash, otherwise it won't be recognized.
If your package has no whitespace but the app still gives this error, try to shorten its name.
Q: Which versions of Android are supported ?
A: From Froyo (2.2) up to the latest JellyBean (4.2.2)
Q: Why is this app useful?
A: Some people might not be able to install a custom recovery on their device, either because there is no custom recovery for this model, or maybe their bootloader is locked. Flash Gordon allows them to flash packages even then.
Or maybe you're simply lazy and you don't want to have to reboot to recovery to flash that new kernel or that new cool flashable mod ? Then Flash Gordon is for you too.
Or maybe just for the heck of it ?^^
Requirements
All you need is a rooted Android device with a proper busybox installed. Required applets include :
mount
sed
unzip
rm
cp
Changelog
25/04/2013 : Initial release
26/04/2013 : Added a few fixes and regex corrections. (Github commit)
26/04/2013 : Hotfix for some flashable zips mistakenly identified as unvalid + Hotfix for kernels where the updater-script uses package_extract_file(); instead of write_raw_image(); (Github commit)
Click to expand...
Click to collapse
To Do List
Using a private version of busybox to remove having busybox installed/installing new applets as a requirement for the user
Implementing an equivalent of nandroid backups (zipping the content of the defined partition(s) and generating an updater-script to allow the user to restore the backup either through recovery or through Flash Gordon
Translating ui_print(); to echo in bash and make the "Flashing" ProgressDialog's message display the content of those ui_print();
Disclaimer
If you're going to test this app, make sure you have a nandroid backup handy as it is very far from stable.
I won't be held responsible for any damage done to anything whatsoever. You use this tool at your own risk.
Download
A preview/pre-alpha/proof-of-concept/work-in-progress/whatever-but-stable apk is attached to this post.
Again, make sure to have a nandroid backup before flashing anything through Flash Gordon for the moment.
If you like this project, please press the "Tip us?" button so that more people can know about it.

Reserved

Reserved too

Last one

You made it possible man.. hats off.. ^_^
Sent from my MT27i using xda premium

Will try this out!
Sent from my LT26i using xda premium

This i will test for sure!

Amazing work once again!
Sent from my Nexus 4

For the gsm galaxy nexus at least, choosing two zips (recovery, kernel) brings back a 'file not valid'. Looking forward to the "final" version.
Edit- if this helps.. twrp 2.5.5.0 and trinity kernel. If there is something for me to do please ask.

Flashed a XXEMB6 I9300 Modem+RIL with no problems.

dirtyreturn said:
For the gsm galaxy nexus at least, choosing two zips (recovery, kernel) brings back a 'file not valid'. Looking forward to the "final" version.
Edit- if this helps.. twrp 2.5.5.0 and trinity kernel. If there is something for me to do please ask.
Click to expand...
Click to collapse
Make sure there is no whitespace in the name of the zip, otherwise the app won't be able to pick it up.
If it still doesn't work, try shortening the name of the zips, for some reason I had the same issue with files which have long names
rickoslyder said:
Flashed a XXEMB6 I9300 Modem+RIL with no problems.
Click to expand...
Click to collapse
Thanks a lot for the feedback

Androguide.fr said:
Make sure there is no whitespace in the name of the zip, otherwise the app won't be able to pick it up.
If it still doesn't work, try shortening the name of the zips, for some reason I had the same issue with files which have long names
I gave shortening the file names a try with no success. And no spaces.
Click to expand...
Click to collapse

dirtyreturn said:
Make sure there is no whitespace in the name of the zip, otherwise the app won't be able to pick it up.
If it still doesn't work, try shortening the name of the zips, for some reason I had the same issue with files which have long names
I gave shortening the file names a try with no success. And no spaces.
Click to expand...
Click to collapse
That's weird, can you please give me a link to the zip you're trying to flash or attach it here ?
Would be very helpful for me to try and track the problem down

Top development here! Thanks
Sent from my GT-I9305 using Tapatalk 2

http://db.tt/SHgN82F1. http://db.tt/9hBvqE7d
Androguide.fr said:
That's weird, can you please give me a link to the zip you're trying to flash or attach it here ?
Would be very helpful for me to try and track the problem down
Click to expand...
Click to collapse

Cool idea. Thanks. :thumbup:
Sent from my EVO using xda premium

dirtyreturn said:
http://db.tt/SHgN82F1. http://db.tt/9hBvqE7d
Click to expand...
Click to collapse
Thanks a lot :good:
I tried them both after removing flashing from the app and they got extracted and translated properly on my device.
Please make sure you have a proper busybox install, if you do, please give me the output of this command in terminal :
Code:
unzip
I made a few fixes and corrections, here is the apk (the one in the OP was updated too)

Thanx a million :thumbup:

Androguide.fr said:
Thanks a lot :good:
I tried them both after removing flashing from the app and they got extracted and translated properly on my device.
Please make sure you have a proper busybox install, if you do, please give me the output of this command in terminal :
Code:
unzip
I made a few fixes and corrections, here is the apk (the one in the OP was updated too)
Click to expand...
Click to collapse
I have busybox v1.20.2-Stericson installed... in /system/xbin. .. in terminal running .unzip. gives the busybox info, 'Usage', followed by extract files from ZIP archives with other options. I am on CM10.1 if that makes a difference. edit- checked the applet manager section and 'unzip' is installed. And had installed updated apk. sorry this post is not much help.

This is GOLD.
Sent from my Galaxy S3. Long live the original Galaxy S

Simple ROM Patcher (Replaced format with recursive delete) Faster ROM Flashing

Hey Guys, Here is a small application i created as i was fed up with the slow rom installs due to the format line of the updater-script
{
"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:
Requires NET Framework 4.5
Put simply this small application will patch the .zip
Replacing the line below
format("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "0", "/system");
With the following line
delete_recursive("/system");
It supports manually browsing to the zip file
It supports dragging the zip file on to the exe
It supports right clicking the zip file and selecting "Patch ROM Zip File"
Note: Make sure to run the exe directly once to enable right click context menu. No installation required.
1.1
Fixed small issue with .zip detection
1.0
Initial Release
Released by Cyanlabs for XDA-Developers.
http://cyanlabs.co.uk
Download Here - http://kitchen.cyanlabs.co.uk/LG_G2/index.php?dir=G2+Tools+By+Cyanlabs/
It knocks off around 5-10minutes of flashing time and only takes about 10 seconds to patch
Use this file to remove the context menu entry RemoveContextMenu.reg (it will be re-added upon launching the application again)
Source:
Code:
Imports System.IO.Compression
Imports System.IO
Imports Microsoft.Win32
Public Class Form1
Dim FileToModify As String = ""
Private Sub NsButton1_Click(sender As Object, e As EventArgs) Handles NsButton1.Click
Using dialog As New OpenFileDialog
dialog.Title = "Select ROM Zip File"
dialog.Filter = "Zip Files (*.zip)|*.zip"
dialog.RestoreDirectory = True
If dialog.ShowDialog() <> DialogResult.OK Then Return
ModifyFiles(dialog.FileName)
End Using
End Sub
Private Sub Form1_Load(sender As Object, e As EventArgs) Handles MyBase.Load
WriteRegistryHandler()
Try
FileToModify = My.Application.CommandLineArgs(0)
If FileToModify.Contains(".zip") Then
ModifyFiles(FileToModify, True)
Else
MsgBox("Invalid file selected!")
End If
Catch ex As Exception
End Try
End Sub
Sub ModifyFiles(update As String, Optional close As Boolean = False)
Try
Using archive As ZipArchive = ZipFile.OpenRead(update)
Dim File As ZipArchiveEntry = archive.GetEntry("META-INF/com/google/android/updater-script")
If System.IO.File.Exists(Application.StartupPath & "\" & File.Name) Then System.IO.File.Delete(Application.StartupPath & "\" & File.Name)
File.ExtractToFile(Application.StartupPath & "\" & File.Name)
archive.Dispose()
End Using
Catch ex As NullReferenceException
MsgBox("no updater-script found")
Application.Exit()
End Try
Try
Dim reader As New StreamReader(Application.StartupPath & "\updater-script")
Dim s = reader.ReadToEnd().Replace("format(""ext4"", ""EMMC"", ""/dev/block/platform/msm_sdcc.1/by-name/system"", ""0"", ""/system"");", "delete_recursive(""/system"");")
reader.Close()
If System.IO.File.Exists(Application.StartupPath & "\updater-script") Then System.IO.File.Delete(Application.StartupPath & "\updater-script")
Dim writer As New StreamWriter(Application.StartupPath & "\updater-script")
writer.Write(s)
writer.Close()
Using archive As ZipArchive = ZipFile.Open(update, ZipArchiveMode.Update)
archive.GetEntry("META-INF/com/google/android/updater-script").Delete()
archive.CreateEntryFromFile(Application.StartupPath & "\updater-script", "META-INF/com/google/android/updater-script")
End Using
If close Then MsgBox("Patched Successfully!", MsgBoxStyle.Information, "Success")
Application.Exit()
Catch ex As Exception
MsgBox(ex.Message)
Application.Exit()
End Try
End Sub
Private Sub Label2_Click(sender As Object, e As EventArgs) Handles Label2.Click, Label1.Click
Process.Start("http://cyanlabs.co.uk")
End Sub
Sub WriteRegistryHandler()
Registry.CurrentUser.CreateSubKey("Software\Classes\CompressedFolder\shell\Patch ROM Zip File\command")
Registry.CurrentUser.OpenSubKey("Software\Classes\CompressedFolder\shell\Patch ROM Zip File\", True).SetValue("Icon", """" & Application.ExecutablePath & """")
Registry.CurrentUser.OpenSubKey("Software\Classes\CompressedFolder\shell\Patch ROM Zip File\command", True).SetValue("", """" & Application.ExecutablePath & """ ""%1""")
End Sub
End Class
Linux version
mattmannlt said:
I threw these together for Linux. Any other Linux users out there here you go.
LG-G2-RomFormatFix.sh
Nautilus script for right click menu.
LG-G2-RomFormatFix.sh
Thanks fma965. Good find.
Click to expand...
Click to collapse

sub'd. interested in this. possible to make it work via mac? and also on android itself?

Looks interesting, will take a look
Sent from my LG-VS980 using Tapatalk

I could make it work on Mac and Android but I don't have the skills for the coding languages used on those platforms
Sent from my LG-D802 using Tapatalk

I hear ya! So slow formating on this device.
This will come in handy for the real flash addicts.

Yep. Added this to my soon to be released EnergyROM for the LG G2. Thanks for the tip

Would be great if this could be done on Android. Download ROM with the phone, patch it, flash it
Thanks!

MaluNoPeleke said:
Would be great if this could be done on Android. Download ROM with the phone, patch it, flash it
Thanks!
Click to expand...
Click to collapse
Read up!

fma965 said:
Hey Guys, Here is a small application i created as i was fed up with the slow rom installs due to the format line of the updater-script
Code:
Put simply this small application will patch the .zip
Requires NET Framework 4.5
Replacing the line below
format("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "0", "/system");
With the following line
delete_recursive("/system");
It supports manually browsing to the zip file
It supports dragging the zip file on to the exe
It supports right clicking the zip file and selecting "Patch ROM Zip File"
Note: Make sure to run the exe directly once to enable right click context menu. No installation required.
Version 1.0 - Released by Cyanlabs for XDA-Developers. http://cyanlabs.co.uk
Download Here - http://kitchen.cyanlabs.co.uk/LG_G2/index.php?dir=G2+Tools+By+Cyanlabs/
It knocks off around 5-10minutes of flashing time and only takes about 10 seconds to patch
Use this file to remove the context menu entry RemoveContextMenu.reg (it will be re-added upon launching the application again)
UPDATE: And yes this is a simple application it has only around 70 lines of code, this is one of my most basic applications and it was designed to be quick and basic, i can code programs that are much more advanced than this... check my github for proof, (http://github.com/cyanlabs)
Click to expand...
Click to collapse
Thank you good sir, I was doing this manually for a long time, now I no longer need to do this with your script!

djkinetic said:
Thank you good sir, I was doing this manually for a long time, now I no longer need to do this with your script!
Click to expand...
Click to collapse
My first and hopefully not last contribution to the LG G2 community, I have made many contributions while i was in the xperia play community as can be seen in my signature
offtopic: dont forget XDA has a thanks button
------------------------
v1.1 Uploaded - Read OP For Info

If any one with android/java programming skills is here then this post may help
http://pastebin.com/KiqLaTLT or http://pastie.org/8499361 (detailed information on what my application does so that some one can recreate it in java using the java class java.util.zip and inputstreams

Linux Versions
I threw these together for Linux. Any other Linux users out there here you go.
LG-G2-RomFormatFix.sh
Nautilus script for right click menu.
LG-G2-RomFormatFix.sh
Thanks fma965. Good find.

mattmannlt said:
I threw these together for Linux. Any other Linux users out there here you go.
LG-G2-RomFormatFix.sh
Nautilus script for right click menu.
LG-G2-RomFormatFix.sh
Thanks fma965. Good find.
Click to expand...
Click to collapse
Nice work, Uh could these run under terminal emulator on Android?
Sent from my LG-D802 using Tapatalk

fma965 said:
Nice work, Uh could these run under terminal emulator on Android?
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
Is this patcher thing only for linux? cause I can't run it since its on win-32 bit.....

HeXaLox said:
Is this patcher thing only for linux? cause I can't run it since its on win-32 bit.....
Click to expand...
Click to collapse
mine is for Windows
the other one is for Linux
Sent from my LG-D802 using Tapatalk

FMA Saves the day again ^_^ +thnx bud

great idea but I easy question: why dev don't change script in rom? In my rom I use this form first ver

acer73 said:
great idea but I easy question: why dev don't change script in rom? In my rom I use this form first ver
Click to expand...
Click to collapse
well yes of course that is the ideal outcome but I can't control the devs so I make my own method
Sent from my LG-D802 using Tapatalk

I used this in my last round of ROM updates, but there is an issue with it. I had experienced this once and thought it was my recovery. One of my port testers experienced the same problem, so I decided to confirm the issue.
When I go back to my restore of my original stock ROM, do a Factory Reset, and then flash my ROM (with your included code), the ROM install fails. However, if I flash the same ROM (without your included code), the ROM installs fine. If I am also on a custom ROM and then flash and then flash my ROM (with your included code), the ROM installs fine.
Something about the original stock ROM creates this issue. I can't confirm a custom stock ROM, but I thought you may want to include this information in the OP in case anyone else runs into this issue. I'll include my exact steps in case you want to see it in action.
STEPS
ITEMS USED: I had my HeatshiverSX v1.5 (your code included) and a HeatshiverSX v1.5 copy (without your code). I had a backup of my original stock ROM, and used TWRP as my recovery.
Restored the backup.
Booted into OS.
Booted into recovery.
Factory Reset.
Flashed HeatshiverSX v1.5 (with code).
Install failed.
Factory Reset again.
Flashed HeatshiverSX v1.5 copy (without code).
Install worked.

Heatshiver said:
I used this in my last round of ROM updates, but there is an issue with it. I had experienced this once and thought it was my recovery. One of my port testers experienced the same problem, so I decided to confirm the issue.
When I go back to my restore of my original stock ROM, do a Factory Reset, and then flash my ROM (with your included code), the ROM install fails. However, if I flash the same ROM (without your included code), the ROM installs fine. If I am also on a custom ROM and then flash and then flash my ROM (with your included code), the ROM installs fine.
Something about the original stock ROM creates this issue. I can't confirm a custom stock ROM, but I thought you may want to include this information in the OP in case anyone else runs into this issue. I'll include my exact steps in case you want to see it in action.
STEPS
ITEMS USED: I had my HeatshiverSX v1.5 (your code included) and a HeatshiverSX v1.5 copy (without your code). I had a backup of my original stock ROM, and used TWRP as my recovery.
Restored the backup.
Booted into OS.
Booted into recovery.
Factory Reset.
Flashed HeatshiverSX v1.5 (with code).
Install failed.
Factory Reset again.
Flashed HeatshiverSX v1.5 copy (without code).
Install worked.
Click to expand...
Click to collapse
THanks for the information, Wouldn't this be due to something relating to the partition being formatted and not rm -rf'd ?

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

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

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

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

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

：手指划线：

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

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

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

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

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

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

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

Do games work on this rom?

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

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

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

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

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

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

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