yashsingh1/xdaforums huggingface dataset:
[Android General] Lidenburg:
Cyanogenmod now compiles but there's something wrong with something audio related, not sure exactly what it is.

This is what I managed to pull from it. It's from /data/tombstones/tombstone_00 and is the only thing I have to go on right now.

04-28 01:12:17.321 3641 3641 D ALSAModule: switchDevice: curTxUCMDevivce None curRxDevDevice Speaker
04-28 01:12:17.321 3641 3641 D alsa_ucm: snd_use_case_set(): uc_mgr 0x41ba3378 identifier _verb value HiFi Lowlatency
04-28 01:12:17.321 3641 3641 E alsa_ucm: Invalid verb identifier value
04-28 01:12:17.321 3641 3641 E alsa_ucm: Invalid current verb value: Inactive - -1
04-28 01:12:17.321 3641 3641 F libc : Fatal signal 11 (SIGSEGV) at 0x2fe5cada (code=1), thread 3641 (mediaserver)

The problem is the last line the "F libc : Fatal signal 11", if anyone can figure out what that means, or even better, a solution for it, you will be loved by everyone in the Padfone community.

I've attached the entire file below as a .txt file so you can see what the problems are.

You can find the device tree at https://github.com/Lidenburg/android-device-asus-A68 and the kernel source at https://github.com/Lidenburg/android_kernel_asus_A68 if you want to give it a try yourself.
[Android General] RaymondX:
I don't think we Padfone 2 users will get a firmware upgrade from Asus

http://www.asus.com/News/ugUYebfgcAI96PPd

As only PFI and New PFI are mentioned, I highly doubt we will ever see anything above 4.1.1 on padfone 2...
[Android General] SiSSiDroid:
I just called Asus. I was talking to one guy who didn't know anything about it so I asked if there's someone higher who might know or I could contact. Nobody at there knew nothing, only that the plan's are reveled for Infinities... After a few minute of discussion this was the last thing he told me and kinda broke my heart...

"I'm sure that PF2 isn't getting KitKat this year and maybe not even next year..."

Remember that he wasn't sure but that's the kinda answer I got.

Kinda suck's that I've been using Asus components in my PC for age's and now they screwed me over big time in the cellphone department...
[Android General] Explorer23:
Really sad to hear that ... i hope we get at least 4.3, if not 4.4. And ofc Cyanogen :)

Anyways, I don't wanna generalize. They kinda screwed us over with Padfone series, but no matter what they do with phones, they're still top laptop manufacturer and one of the best in tablet, motherboard and graphic card departments. I probably won't buy any newer Padfone again, but I'm not ditching the whole company because of one single letdown (it's experimental project anyways ...).
[Android General] droidace:
I could've never explained it better. thank u.

my only confusion here is why didn't this device get the attention of Chinese developers? Asus threw the source code out there and it's supposed to be dominant by Chinese as this device is primarily targeting their region??
[Android General] n_god:
I'm agreeing with you, also I'm selling my pf2 with dock and newer buy asus phone. my and my wifes laptops are both asus and there are perfect, if I buy new laptop it will %75 percent asus but not padfone...
[Android General] deswong:
Encryption unsuccessful issue.

Hi,

I have had this happen this morning where the phone rebooted by itself, and then got an Encryption unsuccessful message on the screen.

I cannot re-flash this as it seems to think there is an issue with the /Data location on the Padfone2. It refuses to mount it.

This is very frustrating, I have spent the day trying all sorts of things, and cannot get it to load *ANY* rom as it cannot write or find the /Data location.

Has anyone come across this before for this particular phone? I need to get hold of the full download of an official Asus ROM I think for this, but all I can find on their sites are the updates not the full ones.

I can get into Fastboot, and ADB in recovery, that's all I can get to. I have been able to adb shell but every location reports that it is at 0 bytes length for files or empty.

Attempted many ADB sideloads, but they all fail as it has an error mounting /Data, and even in recovery it has an issue with the /cache location.

Really frustrated with this now, as I don't know what else to do with it.
[Android General] SiSSiDroid:
This is my method for reviving Padfone 2, so give it a go:

adb reboot bootloader

fastboot flash recovery *stock-recovery*.img

wipe data / factory reset

adb reboot bootloader

fastboot flash *cwm/twrp-recovery*.img (I have to do this because the stock recovery doesn't indentify ADB)

fastboot boot *cwm/twrp-recovery*.img (I have to do this because the stock recovery doesn't indentify ADB)

adb push *stock-rom*.zip /cache

adb reboot bootloader

fastboot flash recovery *stock.recovery*.img

fastboot boot *stock.recovery*.img

wait for it to reboot to stock recovery and "Apply update from cache"

EDIT: You can find all the cwm and stock recoveries from my dropbox: https://www.dropbox.com/sh/o60444of4ky7s0e/ZwHWsy4LSb
[Android General] Lidenburg:
I've gotten the encryption error too a couple of times, wiping everything and reflashing the ROM worked for me.

And the downloads from Asus' website are the full downloads.
[Android General] deswong:
Thanks for that - I have been trying this tact and this is the stumbling block I have.

>fastboot flash recovery stock.recovery.img
sending 'recovery' (10240 KB)...
OKAY [ 0.766s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 90.315s

I can do a fastboot and boot the stock recovery - would this achieve the same thing (I think so...) as I just cannot write the recovery back to the device.

If I get the WWE rom onto the device in the /cache folder, and use the stock recovery - it gives me the following when trying to install the ROM:

-- Install /cache ...
Installation aborted.

I seem to be stumbling at the wiping everything part. ADB Shell has got '#' instead of '$' so I assume the bootloader is still unlocked.
[Android General] Lidenburg:
I don't know if the stock recovery has a recovery log, but if it does it would be great if you could pull it and upload it so you can know what's causing it to fail.

If you can't get that then I would just turn it in to Asus for repair.
[Android General] Lidenburg:
Can you flash/boot CWM? if so then try to format everything from there, if not just return it to Asus, I don't know a way you could fix that. Sorry.

If the method Sissidroid doesn't work then you're pretty much screwed.
[Android General] :
Got my PadFone 2 back today, it has been repaired once again.

What is the status on getting CM running on the device? What are the problems right now?
[Android General] Lidenburg:
Just finished compiling again, gonna make a backup and will try and see if my attempt did anything and update this post with what the error is.

Also need to update the repo, our internet has been slow/down for 2 weeks so haven't been able to update it, seems to be better now though.

Update: For some unknown reason I can't mount /data which is where I get the tombstones from. I'll try and see why it does that and come back with the error once I have it.
[Android General] :
[MENTION=2379763]Lidenburg[/MENTION]: Do you have CM running or are you having problems putting the ROM together?

I don't know anything about porting a ROM to a device that is not supported? Are there drivers missing? Is the kernel causing problems? Are there functions or features not working?
[Android General] Lidenburg:
[MENTION=5176931]A51Rene[/MENTION] I can build it and flash it but it doesn't boot, seems to be something wrong/missing in some audio config, I had made a change to "snd_soc_msm_2x_Fusion3" since I think that's where the error is coming from, but since I couldn't mount /data there was no way to know what was causing it since I'm getting the logs from /data/tombstones/
[Android General] walaway:
Changing management. I don't have decent interwebs lately. Fixing it soon. Enjoy guys and sorry my country is a failure
[Android General] deswong:
:crying:

There has to be a way to do this - I think it is just a software/partitioning issue. It's out of warranty and not supported in Australia, so I would have to either buy a new one or pay almost the same amount to send it overseas and get it fixed and returned.

Interestingly I executed this and came across an interesting result:

fdisk -l /dev/block/mmcblk0

Disk /dev/block/mmcblk0: 15.7Gb, 15762194432 bytes
256 heads, 63 sectors/track, 1908 cylinders
Units = cylinders of 16128 * 512 = 8257536 bytes

Device Boot Start End Blocks ID System
/dev/block/mmcblkp1 1 266306 2147483647+ ee EFI GPT

This to me seems like it has lost the partitions completely - is this the right assumption?
[Android General] SiSSiDroid:
Should be like this:

Disk /dev/block/mmcblk0: 61079552 sectors, 58.2M
Logical sector size: 512
Partition table holds up to 32 entries
First usable sector is 34, last usable sector is 61079518

Number Start (sector) End (sector) Size Code Name
1 32768 237567 200K 0700 modem
2 262144 265143 3000 0700 sbl1
3 265144 268143 3000 0700 sbl2
4 268144 272239 4096 0700 sbl3
5 272240 282479 10240 0700 aboot
6 282480 283479 1000 0700 rpm
7 294912 327679 32768 0700 boot
8 327680 328679 1000 0700 tz
9 328680 328699 20 0700 pad
10 328700 334843 6144 0700 m9kefs1
11 334844 340987 6144 0700 m9kefs2
12 360448 366591 6144 0700 m9kefs3
13 366592 368639 2048 0700 asusdata
14 368640 370687 2048 0700 asusdata2
15 370688 372735 2048 0700 asuskey
16 372736 374783 2048 0700 asuskey2
17 374784 376831 2048 0700 asuskey3
18 376832 378879 2048 0700 m9kefsc
19 378880 380927 2048 0700 asuskey5
20 380928 382975 2048 0700 asuskey6
21 382976 389119 6144 0700 asusgpt
22 389120 405503 16384 0700 persist
23 405504 425983 20480 0700 recovery
24 425984 950271 512K 0700 tombstones
25 950272 3571711 2560K 0700 cache
26 3571712 3573759 2048 0700 misc
27 3604480 3604495 16 0700 DDR
28 3604496 6750223 3072K 0700 system
29 6750224 6752271 2048 0700 gmxt
30 6752272 61079518 51.8M 0700 userdata

So yes, your right.
[Android General] dkasak:
What is to be done?

Hi all. Is there a published status / bugzilla / TODO file / whatever of the Cyanogen port? I'm a developer, with stacks of experience in higher level languages, some hacking of C stuff ( GTK+, Enlightenment, and random things ) and some assembly experience too ( ages back ). I'm interested in helping out. It's not really clear from quickly scanning this post if there is any low-hanging fruit I could have a go at.
[Android General] Lidenburg:
First off, thank you for wanting to help, so far I've basically been trying to do this alone.

I'll do a build when I get home and flash it to see if my patch did anything, I will post what the problem is here once I have done so.
[Android General] SiSSiDroid:
Nice to hear that and welcome to the group were small but feisty !

The management of the thread is also becoming my job soon. So I will post the latest known info's about the CM progress to the OP so there you will constantly find the latest happenings of CM.
[Android General] Lidenburg:
It appears as if I have bricked my device trying to find out what was wrong so I won't be able to tell you what's causing it.

If I'm lucky I'll be able to fix it by tomorrow, if I'm less lucky I won't be able to fix it until next week, if I'm really unlucky I'll have to hand it in to Asus to fix it which will probably take a long time.

Note: I would highly advise against flashing the recovery based on the files on my current master branch for the A68, it appears as if I removed 2 pretty important lines :D
[Android General] dkasak:
Noted :D
[Android General] Explorer23:
[MENTION=2379763]Lidenburg[/MENTION]

Let's hope you don't get the motherboard changed ... I hear new A68 models can't be unlocked.
[Android General] mcstoned:
4.3 or 4.4

Does anybody have any news about a possible, well lets better say certain update to 4.3 or 4.4 ?

I dont have a PadFone 2 yet, but with the current price situation its really attractive :laugh: ... My sis bought herself a Ascend P6 yesterday... I like the implemented "permission-manager" from huawai... there must be something similar at 4.3 i read?

So, does anybody know for certain, will there be an update to 4.3 or 4.4

...

oh, also i forgot... is it possible to connect the phone via (ordinary) micro USB to windows?! I read some differing posts on the net...

Thanks in advance
[Android General] Explorer23:
About 4.3: it was supposed to come in Q3 2013 ... then it was delayed till Q4 2013 ... and then Q1 2014. Realistically speaking, there probably won't be any updates for Padfone 2 any more. Stuck at 4.1.1 :S So 4.4 is only a dream ...

Yes, connecting the phone with ordinary micro USB cable will work; not sure about tablet (I think they wired something differently in station). But the phone works 100% with classic micro USB.

You get a micro USB to ASUS 13-pin connector in package anyways, so that shouldn't be a problem.
[Android General] SiSSiDroid:
Q1 2014 ? This is new info ? I think I read from padfoneclub that someone had asked from Asus French and they told there won't be any updates... Also I've been digging trough the asus firmware and found something interesting like...

#!/system/bin/sh
#This version for A80 only
#[Setup log & env]

from /system/etc/init.asus.check_asdf.sh (yes it is asdf...)... Also [MENTION=2379763]Lidenburg[/MENTION] found something regarding the PF1 too... Can't remember what it was tho :D
[Android General] mcstoned:
Thanks for fast reply! :victory: ... even though, the news are more like :(:crying: ... its a shame, Asus does not support the PadFone 2
[Android General] Explorer23:
Well it's not really "new" info ... I came across this sometime in early december. If someone from ASUS said there won't be any updates, then we can be sure it's true. Sad ...
[Android General] Demazda:
There are also a lot of PF2 A68-related files and occurences in PFI A80 firmware and kernel sources, too.

And also, to add something to PF2 support: the "leaks" of Asus' updates planning was an unofficial fake, and Asus did never promise anything for Q3 2013. Also, yeah, Asus France told many people (including me) that PF2 is no longer supported. PFI will get 4.4 Q1 2014 and PFI2 will get it Q2.

Source: http://www.asus.com/News/ugUYebfgcAI96PPd
[Android General] SiSSiDroid:
Ummm.... There's nothing about PF2 getting KitKat at Q2 ?

Edit: omg didnt notice you said PFI 2
[Android General] Demazda:
Yeah, and that's kinda lame for them not to release any updates for PF2... I don't have one, but this device is not really old, same hardware as Nexus 4, so they should have at least done something.

At least there's some hope for Lidenburg to port CM on it, even though developing is kinda hard (I tried for PFI but did not really succeed).
[Android General] Dj Mauro:
Nothing is impossible! I hope that someone release CM on PF2!
[Android General] tetakpatak:
Guys, it is this damn money-obsessed market: they just want to sell and take the money. Preferably without any maintainance. Isn't that just sick?

There is a low that every device should get for at least 2 years updates. Isn't that just CRAZY for such a great devices such short maintaining time? And most of the brands don't even provide updates longer than 18 months.
[Android General] KB79:
Sorry to burst in, but were exactly lies the difficulty in porting CM to our PF2? If the hardware is equal to that of the N4, shouldnt it be more ... straitforward?

(My sincere apologies for the uninformed, perhaps-way-to-simple, noob question)
[Android General] Explorer23:
I guess the problem is the station. The ROM (and kernel) have to be able to run normally in both phone and tablet mode.
[Android General] tetakpatak:
The problem is to find a developer who has interest in spending hunderds of hours for porting the CM to the hardware of this device.

There is no much development and lots of dirty work must be done.
[Android General] KB79:
Would it be an option to have seperate development threads, one for the phone and one for phone + station?
[Android General] Lidenburg:
The problem is that the person trying to port CM (me), has no experience in doing so, and has to figure out how to do so. Simply getting CM to boot would not be a problem for someone who has done it before, if someone whos done it before decides to do it they could probably do it in no time, I however have no previous experience in porting CM, before I started with this I barely had any experience with Linux at all.

So the problem is that I don't know how to port CM to a new device.
[Android General] KB79:
I see now, thank you very much for your answer.

Even though I'm no dev, I would like to contribute to this effort because I feel that ASUS has abandoned us and we're on our own.

Let me reach out to a couple of friends who do have extensive Linux experience, see what they can do.
[Android General] tetakpatak:
Guys, the best would be to try with a more popular device, it is easier to check how to port as the device respository is fully open and well known.
[Android General] KB79:
True, but the exercise is not porting CM, the exercise is porting CM to the PF2 ;)
[Android General] tetakpatak:
LOL :D

True....
[Android General] gentle_giant:
overboard with the tablet

Being a N00B there's a risque of verbal diarrea output but I am going to give my suggestion anyway;

As a proud new owner of a Padfone 2 I would really like to see an upgrade to Kitkat.

After reading through all messages here and on Padfone Club I came to understand that ASUS already abandond the padfone 2. i.e. no Android updates.

I also undertood that there's an extra hurdly to take with this device: it has to suit the Tablet as well (kernel?).

I bought the padfone 2 without the tablet (only € 240,- I jumped in without thinking much). So perhaps I could take my chances and try to install a suitable Kitkat. There are probably phones out there with equal hardware specs.

Can anyone knowledgeable comment on this?

Cheers, Adrian
[Android General] Demazda:
If it were as simple as this, I think people wouldn't complain about lack of updates.

Unfortunately, it is not. Kernel does not only have to suit hardware specs, but they are totally device-specific, as they also must have the same partition scheme, must match the exact hardware, and so on. And as far as I know from my experiments with PadFone Infinity, tablet support is present in kernel, but also in the ROM itself.

The only possible way to have KitKat on the PF2 would be to port CyanogenMod/AOSP or whatever ROM based on KitKat, but this implies to have a good knowledge about how the system works, how the kernel is made, and the configuration of the device.

I know some people are working on such a port (I know Lidenburg is, maybe other people too), maybe they'll succeed one day. And I also tried on the PF Infinity, without success.
[Android General] gentle_giant:
Thanks for the answer Demazda.

in the meantime I have a real problem: I tried FramaRoot > and TWRP recovery install but bricked my device.

All I have now is an nice fancy black IPS screen saying: Invalid Kernel !!

Over at MoDaCo there's a tread tackling exactly this problem: http://www.modaco.com/topic/365818-padfone-2-invalid-kernel/ but I didn't succeed...
[Android General] s79336951:
I'm sorry to hear that gentle, I had the exact same problem (in fact I did the same thing as you did) and one solution was to bring back to ASUS support. I suspect that the bootloader was locked and the flashing of recovery screwed up something.
[Android General] gentle_giant:
Yes s79336951,

that's exactly what I forgot to do: unlocking the bootloader.

While there's a lot of information to be found it is not always very clear. But I shouldn't whine, I was too eager to get the phone unlocked and should have investigated a little better.

Living in Portugal I don't think it is worth to send it in for repair. It will easily cost € 200,- and the would be almost the price I paid.

Guess I'll stick to my old phone for another year...
[Android General] Explorer23:
200€? I doubt it ... they don't have to physically change anything, just reflash it.
[Android General] gentle_giant:
Hi Expolere23,

Hopefully you're right and they just have to reflash.

Just wondering how this is done....
[Android General] Demazda:
But can't you reflash it yourself?

I mean, if it tells you "bad kernel", theorically all you'd have to do is to boot in bootloader mode and reflash stock kernel/recovery.
[Android General] gentle_giant:
Ola Demazda,

probably I am the champion of bricks because I even didn't make 1 single phonecall before I turned it into a paperweight.

It is stuck on this message: invalid kernel!!! The only other screen I can get is by holding the volume-down button and power.

But the resulting menu (2 options) is useless because whatever the choice I make, it returns to the dreaded "invalid kernel" again.

My search on www tells me this is a tough one. hate to send it back but it seems to be the only solution.
[Android General] Demazda:
To get to bootloader, you normally have to boot it with power + volume up, you will then get to a screen with Asus logo and "Bootloader mode!!!" on screen.

Do you have access to it? If so, you will certainly be able to reflash stock kernel and recovery via fastboot commands on a terminal (if you use Linux/Mac) or command prompt (Windows).
[Android General] mu5icman:
Hi there

I'm a PadFone 2 User since the market start in the End of 2012. As all of you, I thought that this Phone will become a big community and also a good support from ASUS. The specifications seem to be perfect for this!

The Phone/Tablet are excellent products, but the support was very bad (ASUS released the PadFone Infinity about half a year after the PadFone 2) and there are no further updates after Android 4.1.1. I was following all the discussion at xda, Padfoneclub and modaco. I felt unhappy that Cyanogenmod will not be released for the Padfone 2.

Anyway, I have to say that I'm happy with the Padfone 2. The Stock Rom works nicely and rooting was possible. With the possibility of all the great root apps and after the installation of the Xposed Framework, I have to say that I can use the PadFone 2 very well. Of course, it will always leave a bitter aftertaste because there are no custom roms available and also no update to Andorid 4.3 or even 4.4...

Recovery: ClockworkMod Recovery 6.0.4.4

Xposed Framework: XPrivacy, Boot Manager, Advanced Power Menu

Root Apps: SuperSU, Titanium Backup, AdAway, GMD Gesture Control (for tablet mode), ES File Explorer, ClockSync, Tasker + SecureSettings

PadFone specific Apps: Padfone Launcher Switcher

Launcher: Apex Launcher for Phone Mode, ADW launcher for Tablet Mode (not very good, but could not find a better one)

The only and main disadvantage is that there is no SD Card slot for the PadFone 2.

When I once buy a new phone, these are the most important points: SD card Slot, possibility to root, CyanogenMod, brand!=ASUS

Until this time, I hope that my Padfone 2 will have a long life time. :D

Cheers, musicman
[Android General] gentle_giant:
Hi Demazda,

My apologies, I haven't checked this thread anymore. Just an update: I got the PF2 going again using this tip.

Perhaps it can help others too.
[Android General] SiSSiDroid:
Hello everyone !

So... Some of you might have already noticed that the OP of this thread has been changed from [MENTION=4158328]walaway[/MENTION] (big thanks to [MENTION=4158328]walaway[/MENTION] for starting this thread!) to me. Il try to update it in the next couple of day's. Also il try to get every bit of information on the progress of CM from [MENTION=2379763]Lidenburg[/MENTION], also if there's other people too working on CM please PM me with the latest information of your progress and il try to add it to the OP !

Now we need everyone to get involved if we wanna see CM for padfone 2. New year 2014, new tricks up our sleeves so we gonna do it this time ! So everyone get your gear ready and let's make it happen !
[Android General] Dj Mauro:
http://www.kolar.dk/

Something is about to happen... If only we knew when!
[Android General] Demazda:
http://www.asus.com/News/ooRHdSBjKOGE6uZI

It happened right now. PF2 will finally get KitKat + ZenUI.