yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Q&A, Help & Troubleshooting] the lost mobiler returns:
I am also having the same problem. an error like this. any ideas why and how to fix it? and after it aborted when my n7 booted up and i check for updates it says ur n7 is up to date, but then the version is stil 4.2.2 not 4.3. so any solution guys? is it because i'm using custom kernel? i'm using franco kernel rite now.
[Nexus 7 Q&A, Help & Troubleshooting] AndDiSa:
There are many threads dealing with these problems ... Please use the search function before starting a new thread.

To answer your question: you have a non stock system so the OTA update is failing. You need either return to stock or do the update manually. Btw. in my blog there is an article how to do so.
[Nexus 7 Q&A, Help & Troubleshooting] ItsDare:
Well, I did search the forums and didn't find anything that helped. And, like I said, I tried doing it manually and it didn't work.

Tomorrow I will check out your blog though and see if the instructions are any different than what I found elsewhere. Maybe i did a step wrong or something?
[Nexus 7 Q&A, Help & Troubleshooting] ItsDare:
Success! I had to incorporate some steps from a slightly different method of updating, but it finally worked!

Thank you!
[Nexus 7 Q&A, Help & Troubleshooting] abobobilly:
Hi! I am having the same problem and getting Status 7 error in CWM Touch.

Can you please let me know as well which method did you use? Thanks
[Nexus 7 Q&A, Help & Troubleshooting] pawelzielak:
Could you provide the detailed step-by-step instruction? I'm on the same (noob) level as you were just before you started this thread.
[Nexus 7 Q&A, Help & Troubleshooting] gallahad2000:
http://anddisa.blogspot.de/

You can use the instructions here (although he left a bit out)

1. install http://www.droid-life.com/2013/04/08/koush-releases-universal-adb-driver-for-windows/

2. install https://docs.google.com/file/d/0B1S0LCuXCnnmSWh6NGJmSE1BUWc/edit

3. install http://www.7-zip.org/download.html

4. download https://developers.google.com/android/nexus/images#nakasijwr66v

5. open the folder fastboot/adb installed to

6. open the image (#4) with 7zip (#3)

7. extract bootloader.img, boot.img and system.img into fastboot folder(#5)

8. run fasboot (should be in start menu), brings up command prompt)

9. type at command prompt "fastboot flash bootloader bootloader-*********.img" *** = use the file name that you extracted (#7)

10. type at command prompt "fastboot reboot-bootloader"

11. type at command prompt "fastboot flash boot boot.img"

12. type at command prompt "fastboot flash system system.img"

13. type at command prompt "fastboot reboot"

14. enjoy 4.3
[Nexus 7 Q&A, Help & Troubleshooting] pawelzielak:
Oh, so you did it via PC.

I still would like to try with OTA. My problem is checksum on build.prop. I modified it and now I reverted changes but there still may be some white character difference. Could anyone attach build.prop file (along with its checksum) of stock n73g a4.2.2? I'll give it one more try.

With N73G
[Nexus 7 Q&A, Help & Troubleshooting] ItsDare:
What I found most helpful in fixing my issue was this thread!

http://xdaforums.com/showthread.php?t=1907796

It is a guide to flashing the factory image to return it to stock, but can be used to update to 4.3 as well!

What I did to fix my specific problem was:

Download the 4.3 update files from androidpolice.

Extracted these three files from it as suggested on AndDiSa's blog:

bootloader-grouper-4.23.img

boot.img

system.img

Plugged my N7 into my computer and since my device doesn't show up in my computer in MTP mode, but does in PTP, I switched to PTP and typed the following code into a command window:

> adb reboot-bootloader

I personally found it necessary to erase boot, cache, recovery, system and userdata to get my update to work. However, if it works without erasing those, that is definitely preferable, and you can skip these commands:

> fastboot erase boot

> fastboot erase cache

> fastboot erase recovery

> fastboot erase system

> fastboot erase userdata

Then type these commands:

> fastboot flash bootloader bootloader-grouper-4.23.img

> fastboot reboot-bootloader

> fastboot flash boot boot.img

> fastboot flash system system.img

Then I rebooted my N7 and Voila, I was using 4.3!
[Nexus 7 Q&A, Help & Troubleshooting] bharuchakarl:
Verification fail on 4.3 update

I am using the galaxy nexus, i had rooted it and was using another custom ROM - ParanoidAndroid 3.60. I currently have the 4.2.2 and i'm trying to update it through my system update but it loads and then gives the error message "verification failed"

I've tried it using the OTA RootKeeper procedure too but the same error turns up. Please help!
[General Accessories] jofoko:
Hello everybody,

i'm running XDAs (I+II+III) in cars provided with an external power supply from the car battery.

The connector is designed as proposed in Wiki page about connectors

http://wiki.xda-developers.com/index.php?pagename=Connectors

With this design, however, the devices don't 'wake up' from Power Suspend mode, when the external AC power changes from Off to On again.

What I'm looking for, is the same behaviour as with the Active Sync craddle. If the device is Off and you put it into the craddle, the device

switches to On again.

I don't know, if this can be achieved with a hardware solution or whether the craddle sends a SetSystemPower(On) message to the device.

Any help appreciated.

greets

jofoko
[Nexus 4 Android Development] thracemerin:
m_plus kernel for Nexus 4 (mako)!

Hi All,

In an attempt to reduce the confusion related to the two versions of 4.3, I have decided to split my m_plus thread into 3 versions, a version for 4.2 (the previous thread: http://xdaforums.com/showthread.php?t=2256887), a version for 4.3 JS AOSP builds (this one) and a version for 4.3 JW builds (not yet up, but will be in the future).

Disclaimer: As usual, I am not responsible for anything that may or may not happen to your device as a result of using this kernel or any other flashable zips posted by me in this thread.

Kernel Features:

Based on the latest Google Source for 4.3

Built with the Linaro 4.7.3 toolchain (2013.07)

insecure ramdisk (ro.recure=0, ro.debuggable=1)

init.d support (by flashing the full ramdisk, requires busybox installed to /system/xbin)

Undervolting support (down to 600mV)

Gamma Control support (motley, faux and franco interfaces available)

Faux Sound Control support including poweramp

dynamic fsync

simple GPU governor

Builds:

Sources: https://github.com/thracemerin/kernel-Nexus4/tree/m_plus_43_exp_JS

Warning: These builds are for 4.3 builds beginning with the letters JS only, if you flash it on a JW based build you will have all sorts of strange graphical issues.

Personal Request: If you plan to make unofficial builds with features not included in the builds posted by me, please don't link them in the thread, all this does is result in confusion especially if someone has a problem with something you have added, it is much easier for me to provide support if I know that everyone in the thread is running the same builds I am. If you want to make a kernel with these features, feel free to start another thread so that they can be discussed and supported as appropriate.

http://goo.im/devs/thracemerin/mako/m_plus_43/JS_builds/alphas

Latest:

Alpha 5:

Flashable (anykernel): m_plus_43_alpha_5JS.zip

Note: if you need the full ramdisk for init.d support/insecure ramdisk, flash the ramdisk package alpha 4 first.

What's Added:

USB force fast charge

Enable Krait Retention

Various patches and enhancements from CAF

Previous:

Alpha 4:

Note: The anykernel version doesn't include init.d support and insecure ramdisk unless your ROM already has it, if you were on alpha 3 you will retain it.

Note 2: If you flash the ramdisk version on CM, the built-in superuser will stop working, CM includes init.d support anyway.

Flashable (ramdisk included): m_plus_43_alpha_4JS_ramdisk.zip

Flashable (anykernel): m_plus_43_alpha_4JS.zip

What's Included:

all the stuff listed in kernel features

freezer patches by Colin Cross

Thanks:

Google

LG

Qualcomm/CodeAurora

CyanogenMod

_motley

faux123

show-p1984

franciscofranco

stratosk

anyone else I failed to mention (if you feel as though you deserved to be thanked by name, please PM me)
[Nexus 4 Android Development] thracemerin:
Reserved
[Nexus 4 Android Development] thracemerin:
PowerHAL Fix:

There is an issue in the stock AOSP powerHAL where the mpdecision touch boost requests are being sent to the wrong socket, as a result there will be unexpectedly poor UI performance. Show-p1984 fixed this problem in his Stockified AOSP build and I pulled the powerHAL and made it flashable for everyone. Just flash it in recovery and reboot, if you want to go back to the stock one just dirty flash your ROM. This shouldn't cause any problems on any ROM even if it has the fix already cooked in, but if it does you can just dirty flash your ROM to remove it. Thanks to show-p1984 for the fix.

43_powerhal_fix.zip MD5: c7cebad04b5f71d067df1a45c6e538f7
[Nexus 4 Android Development] thracemerin:
One More for Science!
[Nexus 4 Android Development] ScumDroid:
Just flashed. I was losing wifi connection with semaphore when phone went into deep sleep. Ill report back. :good:
[Nexus 4 Android Development] keda:
do you have to be rooted in order for init.d to work?
[Nexus 4 Android Development] thracemerin:
Yep, need to have busybox installed too.
[Nexus 4 Android Development] AcmE85:
First of all, thanks for your work.

I want to make sure I understand the procedure correctly.

If I use CM10.2, I flash "m_plus_43_alpha_4JS.zip" to maintain the built in superuser.

init.d will still work, cause cm already supports it.

Right now I am on Alpha3 with SuperSU 1.51. So to update to alpha4 I can simply flash over.

If I want to go back to the built in superuser I have to reflash CM, then flash alpha4 via zip.

Is this correct?
[Nexus 4 Android Development] ScumDroid:
Wont stay connected to Google services when phone goes into deep sleep, bars and signal are grey when i turn screen on. I thought Google fixed all the wifi issues with N4 in 4.3 kernel?
[Nexus 4 Android Development] thracemerin:
Dirty flash CM, then flash A4 should do it, that's what I did and it worked.
[Nexus 4 Android Development] thracemerin:
Strange, it's working fine for me now.
[Nexus 4 Android Development] AcmE85:
Thanks, just wanted to reply. Works as you said.

After the first boot I had some strange behaviour,

min cpu clock did not go below 1,026 ghz and GPU Clock did not go above 200 mhz.

A restart fixed it, incase somebody notices similar behaviour.
[Nexus 4 Android Development] thracemerin:
Weird, I didn't notice that.
[Nexus 4 Android Development] ScumDroid:
Mabye its an app i have installed. Kernel is flying btw, nice work.
[Nexus 4 Android Development] LibiSC:
Is it just me or the option to give location eve with wifi off is ****ing with repeaters... I have two access points in my house and when the option was on the wifi keep disconnecting... Maybe cause In some parts I can have signal from both access points... So weird
[Nexus 4 Android Development] yash295:
+1 for this. i am also having same problem.
[Nexus 4 Android Development] thracemerin:
What ROM are you using?
[Nexus 4 Android Development] yash295:
Cm 10.2 unofficial nightly.
[Nexus 4 Android Development] thracemerin:
hmm...working perfectly for me, CM10.2 unofficial and this kernel.
[Nexus 4 Android Development] yash295:
Oh yeah cm might be the problem. Sorry for the inconvenience
[Nexus 4 Android Development] thracemerin:
The JS version should work on 4.4, but the prima driver won't work so WiFi will be broken, there is a zip file in the Semaphore thread called dePRIMAtor that will fix it for now.

Yep, the 4.3 JS version is the latest one on AOSP as of now, there are clearly changes (like prima as I said above) so we will have to wait to see what else changed, but given that most things are working I'd say the changes are likely minor. Given that there haven't been OTAs yet despite the fact that the images are posted, I'm thinking that Google will release the sources once the OTAs begin.
[Nexus 4 Android Development] sirxdroid:
I was just kidding. The N4 is a fine phone and it pains me to sell mine but I have to otherwise I will not start using the N5 full time, that's how much I like the N4. It was my first serious Android device, lots of sentimental value.
[Nexus 4 Android Development] thracemerin:
The N4, N5 and N7 (2013) are similar enough now that it may be possible to just make a kernel that contains mostly common files, that would make doing a kernel for all 3 so much easier.

I'm not planning to abandon the N4, I don't actually own the N5 the one I posted from is one that I'm supposed to be certifying for work, whether I get to keep it long term is a little up in the air, but I can at least use it long enough to do the initial bring up and then we'll see :)
[Nexus 4 Android Development] azrash:
would the august build of the JS version work fine with the recent cm 10.2 nightly? I have just updated from cm10.1 to cm10.2 a few days ago. heard the deadlock is fixed, but read that the fix is kernel side.

I understand what you feel. my first android phone is the G1, imported it to malaysia from the states. it was very cheap, but a lot of fun to mess with. zram was widely used too. didnt expect to see the zram making a comeback, but i can understand why, since google wants to make a better experience for the lower specced phone. the G1 has a borked battery though, it makes a very nice paperweight for now. :cool:

that'll be nothing short of awesome!:good:
[Nexus 4 Android Development] ShadyGame:
nevermind
[Nexus 4 Android Development] thracemerin:
That would require going to the CAF source for the kernel, which at this point isn't worth it given that we'll be going to CM11 soon. If you use the august one on CM there will be deadlocks and probably the inverted rainbow color issues too, it should work on 4.4 stock though.
[Nexus 4 Android Development] DontPushButtons:
Working great on rastakat with the wifi fix. Good to see this thread alive again.
[Nexus 4 Android Development] thracemerin:
Sources, Woot!

https://android.googlesource.com/kernel/msm/+/android-msm-mako-3.4-kitkat-mr0

https://github.com/thracemerin/kernel-Nexus4/tree/m_plus_44_exp

:cowboy:
[Nexus 4 Android Development] thracemerin:
http://xdaforums.com/showthread.php?t=2534702
[Nexus 4 Android Development] thracemerin:
Since I'm not going to support the 4.3 version of this in the future I'm going to close this thread.
[Nexus 4 Android Development] aumkarpraja:
Using the new PA alpha. A bit choppy/laggy on this ROM with the kernel but works fine otherwise!
[Nexus 4 Android Development] thracemerin:
Could be ROM related, I wonder if PA has mpdecision disabled.
[Nexus 4 Android Development] whittikins:
Where can I get alpha 3 so that I can flash Alpha 3 and then Alpha 4 to have init.d etc support? Thanks

Btw I'm running JSS15J AOSP 4.3 stock.
[Nexus 4 Android Development] lordvj:
can't access franco color control.. i'm on jss15j aosp
[Nexus 4 Android Development] AcmE85:
Alpha 3 was not provided as flashable zip, only as .img for fastboot.

So if you need init.d support you have to flash Alpha 4 via fastboot.
[Nexus 4 Android Development] thracemerin:
What do you mean? FKU doesn't work?
[Nexus 4 Android Development] thracemerin:
There appears to be an issue in AOSP where the touchboost socket was changed in the powerHAL, as a result it's not actually boosting on ROMs that haven't reverted this change. I will post a fixed powerHAL later as a flashable zip, might fix the issue for those having lag or choppy user experiences.
[Nexus 4 Android Development] thracemerin:
Flashable in post 4, if you are experiencing UI stuttering on JSS builds, try this to see if it fixes the problem.

Enjoy :victory:
[Nexus 4 Android Development] mightybrick:
This doesn't appear to be an issue any longer in CM 10.2. I looked through the error logs and didn't see any errors related to Touch Boost, like I had seen in earlier builds.
[Nexus 4 Android Development] thracemerin:
Yeah, I think it was fixed in CM in the last day or two, other AOSP builds will still be affected however.

Edit: the flashable would also appear to be in post 3, I guess I can't count.
[Nexus 4 Android Development] Taebom:
Jar jar's build also fixed touch boost.
[Nexus 4 Android Development] polaris441:
I have prepared flashable zip for alpha4 with init.d support.

Init.d folder need to be manually created using root explorer ==> "/system/etc/init.d"

Set permission to rwxr-xr-x or chmod 6755.

Edit:

File reattached.

http://www.mediafire.com/?rjb0tkork72ogre
[Nexus 4 Android Development] polaris441:
[MENTION=4303511]thracemerin[/MENTION]

It is not a new build. I just rename the img file to boot.img and use motley build 37 flashable zip kernel as a base and replace the boot.img files from yours.

I will delete the attachment as per OP request.
[Nexus 4 Android Development] thracemerin:
Nah, its fine, leave it. I shouldn't have replied since I'm in a really annoyed mood for unrelated reasons at the moment.

Edit: Heh, now its gone. I'll post one later. Anyway, sorry again I wasn't trying to be an ass.
[Nexus 4 Android Development] polaris441:
No problem.
[Nexus 4 Android Development] thracemerin:
Ok, fastboot version is gone, replaced with a flashable ramdisk version that will install the whole ramdisk and allow for init.d support and insecure ramdisk on ROMs that don't include it.

If your ROM includes init.d already, I wouldn't flash the ramdisk version as it may remove ramdisk started services like the built-in superuser on CM and other ROMs that use it.

If you really want to fastboot still, just unpack the flashable ramdisk version and flash the boot.img :)

Anyway, enjoy :victory:
[Nexus 4 Android Development] bobo1337:
A4 works like a charm on rasbeanjelly!Thanks :thumbup:

Poslano sa mog Nexus 4 koristeći Tapatalk 4
[Nexus 4 Android Development] Azurael:
I think it could be related to the fact that 4.3 has new WiFi drivers, or at least a different configuration because I can now see 5GHz networks on DSS channels and (sometimes) WiDi works with my TV, which it never did in 4.2.2... I haven't connected to any networks with repeaters since updating so I don't know if that issue applies to me.
[Nexus 4 Android Development] LibiSC:
Well at the end I think it was root related.... Let me explain... In every 4.3 rom I get random disconnects or couldn't connect at all... So to discard new drivers problems I ported the drivers to 4.2.2 kernel and worked like a charm... Yesterday pa team published a rom with root fixed... I gave it a try and WiFi was normal... Maybe It tried to write somewhere and the buggy root ****ed up something before...

Enviado desde mi Nexus 4 usando Tapatalk 4 Beta
[Nexus 4 Android Development] llevo3:
whether mp decision by default turned on or off?
[Nexus 4 Android Development] Kocai:
It's on by default.
[Nexus 4 Android Development] show-p1984:
That script is evil.

It doesn't check if it is being called on a mako and it accesses a partition directly instead of by name. Those are two mistakes that can be fatal if flashed on another device. (fatal = permanently fatal in the case of an S-OFF device)

Just sayin' :)
[Nexus 4 Android Development] thracemerin:
One could make the argument that people should look at what they're flashing before they flash it, but I didn't really look at the script, I just replaced the file from the powerhal zip that was in _motley's thread, I suppose I could put appropriate checks in just in case :)

Edit: fixed, different version in post 3 now.
[Nexus 4 Android Development] ranasrule:
Hi dev...thanks for your work...I have the following questions if you could kindly answer them:

1) Does this kernel have Touch Control support ?

2) Does it play well with Paranoid Android ? any issues with root on PA ?

3) What app do you recommend for tweaking of kernel settings ? TricksterMod ?
[Nexus 4 Android Development] thracemerin:
1) probably not, the TC dev has never shown any interest in supporting this kernel. I saw his post about what is required and I will make sure we have those settings for the next alpha, but that doesn't mean it will work.

2) as far as I know, yes. Flash the anykernel version and you should be fine.

3) Trickster works well, I personally just use scripts
[Nexus 4 Android Development] thracemerin:
NEW ALPHA!

What's Added:

USB force fast charge

Enable Krait Retention (thanks to faux123)

Various patches and enhancements from CAF (some ported to mako by faux123)

Enjoy :victory:
[Nexus 4 Android Development] AcmE85:
Up and running, thanks for the update!
[Nexus 4 Android Development] mpmilestogo:
Hi. With the earlier 4.2 kernels one had to flash a baseline kernel and then flash the updates. I'm on rasbean latest and would like to try the kernel. I think all I need to do is flash the latest alpha build? Just want to confirm that this works now instead of looking for a baseline kernel and then flashing the update.
[Nexus 4 Android Development] thracemerin:
No need to flash the base unless your ROM doesn't support init.d, just flash the anykernel version.
[Nexus 4 Android Development] pnut22r:
OP, what Rom are you using? I'd like to run this with a completely untouched aosp version of js, but it seems all of them have slight changes. Did anyone know of a fresh js build without tweaks?
[Nexus 4 Android Development] thracemerin:
I'm running my homebuilt CM10.2 right now.
[Nexus 4 Android Development] show-p1984:
Stock aosp has bugs without ending.

But here is the 100% stock js aosp version:

https://plus.google.com/u/1/108262968419038009038/posts/VoqdRjCmkHa

But you will probably want something stock like built from aosp js:

http://xdaforums.com/showthread.php?t=2387480
[Nexus 4 Android Development] hwti:
I just found my Nexus 4 cycling every second between charging off and on.

I'm using the stock charger, and it was at 92% charged.

Unplugging then plugging the charger again fixed the issue.

Could this be related to the Alpha 5 changes ?
[Nexus 4 Android Development] iPwn_:
Is there any indication that mpdecision in 4.3 is better than it was in 4.2?

If it is, it would be nice to see some sort of comparison between mpdecision + ondemand and auto-hotplug + interactive.
[Nexus 4 Android Development] thracemerin:
I don't think so, I've had this happen to me on the 4.2.2 kernel on occasion too, the stock charger has some quality issues I've always chalked it up to that but i'll look into it.

Running ondemand + mpdecision is giving me the same battery life numbers as auto-hotplug + interactive did on 4.2.2, so I've been less inclined to add auto-hotplug back, but I will at some point publish test builds with auto-hotplug for comparison.
[Nexus 4 Android Development] hwti:
I had only one issue on 4.2.2 (I didn't see it on 4.3 yet) : sometimes it stopped at 100% and discharged while still plugged.

<6>[26052.460029] msm_otg msm_otg: Avail curr from USB = 1500

<6>[26052.460303] msm_otg msm_otg: current: 0 -> 1500 (mA)

<6>[26052.460669] pm_power_set_property_usb: usb_target_ma 1500

It doesn't mean it will necessarily charge at 1.5A, but it could, and the charger is rated at 1.2A...
[Nexus 4 Android Development] sideeffects:
New PA seems to have switched to JWR. Is there going to be a compatible m+ anytime soon?
[Nexus 4 Android Development] thracemerin:
There is an A3 version in the 4.2.2 thread, I guess I could bump it up to the same as A5. This whole 4.3 release is a freakin nightmare :rolleyes:

Above 95% it switches from full charge to trickle charge to avoid overcharging the battery. I didn't change anything as far as the battery monitor or the charging behavior that I'm aware of, I'll look into it further.
[Nexus 4 Android Development] Kocai:
You could put it in here rather than opening another thread.

Sent from my Nexus⁴
[Nexus 4 Android Development] JamesInsights:
Agreed. PA is also a popular ROM so it would be awesome to have support.