yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy R i9103] parajsinghal:
Thanks a lot Adam.

You're right. Lockscreen lags, but I have no idea how to solve this as of now. There are many errors in the background that are not affecting the build but need to be fixed. That is increasing a lot of logging. I am hoping once I fix those lock screen may get a little faster but I am not sure. Only time will tell :)

Sometimes when I change something in settings, it doesn't get saved. Must do it 1-2 more times and it works. -- Agreed I have faced this too. Will look into it when other major issues are solved.

Music player doesn't recognize songs on external sd. I didn't try photos.

This is not the case with me. Work like a charm. It recognizes SD card just fine. :confused:

Torch is lazy like with BlueBerry mod.

Yeah, maybe there's a fix for it somewhere, but I will deal with it later.
[Samsung Galaxy R i9103] parajsinghal:
Yup. I personally installed GPlay seperately. I am not sure if I can attach that to OP. But I will surely add that the rom misses Google play.
[Samsung Galaxy R i9103] chandanbs:
I found a way to bypass the FC errors and reboots while asking for root permissions from apps like TB and CWM.

What i did was install this apps and then.. go to

Permission manager app (installed on this rom).

1. go to apps tab.

2. Select your app from "monitoring apps" section.

3. check "I trust this app" slider, then in privacy option, enable all the available options.

4. now launch your app. it will run without asking any root credentials.. :laugh:

Hi Paraj,

If you can fix the FC/infinite reboot when changing the default theme setting, this rom would really be in flying colors..
[Samsung Galaxy R i9103] F3niX:
awesome news.

Just one question. Does cam,data,texts and calls work fine without any issues. If so I will flash this for sure and test it
[Samsung Galaxy R i9103] parajsinghal:
Thanks a lot buddy for your help.

I may not get time during weekdays but I will definitely look into the open issues next weekend. Time to watch some cricket now. Match on ;)
[Samsung Galaxy R i9103] D™:
its have all sounds..?? which sound you want to decrease..?? can you mention also..??:confused:
[Samsung Galaxy R i9103] Pradeep21:
Sorry forgot to mention...i want to decrease only sms notification aound...not phone ring, but both the settings are together..
[Samsung Galaxy R i9103] D™:
hhuuppppp...buddy, the solution will be biased. Means you need to disable the Message tone. Go to message-> Message settings-> select ringtones-> select any sound which is as low as you want.

Or create a blank mp3 file (means no sound) & set it as your message tone.:D
[Samsung Galaxy R i9103] Pradeep21:
I dont want to disable...i just want reduce notification sound...without interupting ringtone sound..
[Samsung Galaxy R i9103] D™:
download GO sms pro & check if it helps..:fingers-crossed:
[Samsung Galaxy R i9103] Adam77Root:
[MENTION=2019828]parajsinghal[/MENTION]: Any plans on uploading your patchrom code somewhere (e.g. Github)?
[Samsung Galaxy R i9103] parajsinghal:
Hey sorry guys, been away for a long time now. Had to take my phone to the service center today because it was not charging .. thought it was some USB connector issue ... as it turns out, the slot just required some cleaning, stupid me !!! :o

Positive Side, reminded me of good old XDA where I could have asked some friends for help ;) and happened to bump by this thread.

First of all I have to admit awesome progress guys, Adam you are the hero man!! Thanks :good:

And many thanks to Karthik and Grarak for the superb work you guys have done. Thanks Vikesh for managing it all so well and I thank everybody who keep this community going.

Now coming to the question. Sorry to disappoint you Adam but I got no copy of my work. My system crashed and I didn't care to backup things before a format. That said, I think it was useless. Everyone moved to JB and my work was based on ICS code.

Now I have some time again for development right now ( not much though ) and I am happy to do it from scratch for JB, the only issue being - even MIUI v5 is still on 4.1. MIUI is yet to move to 4.2. So either we need a stable 4.1.2 code or we wait for MIUI to move to 4.2.2 if we want to have MIUI JB.
[Samsung Galaxy R i9103] karthik050782:
Hi paraj, welcome back.. I am trying for miui v5. I will post the issues here if I am unable to solve..

Current status: in bootloop, I think the issue is I haven't fixed the rejected smali. Now fix is going on..
[Samsung Galaxy R i9103] parajsinghal:
Super!! Happy to help :)

One question - You working on jellybean patchrom with current cm10.1 as base rom?
[Samsung Galaxy R i9103] karthik050782:
Nope, even apktool won't support 4.2. So using CM-10... As very new to this, studying... is it mandatory that all the rejects should be fixed?
[Samsung Galaxy R i9103] parajsinghal:
Maybe a few are not that important to fix. But my advice fix them all and fix them the correct way ( no shortcuts ) or they will come back to haunt you as defects sooner or later.

So is cm10 stable enuf to be used as a daily driver? Coz Miui will have the same defects as cm10 and I don't think Adam supports cm10 any longer.
[Samsung Galaxy R i9103] Adam77Root:
Although I don't support it, I can build an updated version of it if MIUI gets bootable. The differences are not that much, so it should be straightforward to backport the configs.

Sent from my CM10.1-powered GT-I9103
[Samsung Galaxy R i9103] parajsinghal:
That really is great. Like I said before I have some free time these days. I can try and get Miui to boot with CM10 but only if Karthik is okay with it. He is already working on Miui with cm10. Or if Karthik can commit his code I may just be able to help him faster.
[Samsung Galaxy R i9103] karthik050782:
As you are experienced, I will commit my source and you can give us miui v5
[Samsung Galaxy R i9103] karthik050782:
Here it is

https://github.com/karthik050782/patchrom_i9103
[Samsung Galaxy R i9103] parajsinghal:
Thanks a lot buddy.. Downloads are on. Hopefully I will fix some rejects tonight.
[Samsung Galaxy R i9103] karthik050782:
I have tried to move the widgets to framework2, but that is causing bootloop..

Current source in github will give error in framework.. we need to find an alternative solution to fix this..

It seems android dex only support 64k.. Hope you have faced this in your earlier build..
[Samsung Galaxy R i9103] Adam77Root:
Yes, maximum number of classes in a dex file is limited to 2^16-1 (65535). That's why CM also had to split framework.jar into two files.
[Samsung Galaxy R i9103] parajsinghal:
Yeah, I remember that. Moving stuff to framework2 was quite a pain. But keeping stuff close to i9100 conf always helped. Still had to make a couple of exceptions. I will see how it goes this time. Thanks for the heads up.
[Samsung Galaxy R i9103] Adam77Root:
Meanwhile I started compiling CM10 with the latest sources. It is now at the dexing stage, so it should finish soon. Had to resolve some conflicts, but otherwise the integration was pretty seemless. Hope I didn't forget anything. :cyclops:

And it's completed! Will upload tomorrow afternoon. Everything that works in CM10.1 works here too. The zip needs some changes to get bootable and fully functional. Since these can be included in the porting phase, I don't rebuild the zip, I will upload them separately.
[Samsung Galaxy R i9103] hydromax:
What languages ​​are prepared to support the MIUI rom?

For example, Turkish support?

Thanks.

---------- Post added at 07:17 PM ---------- Previous post was at 07:14 PM ----------

Can you offer multi-language support is not very difficult?
[Samsung Galaxy R i9103] parajsinghal:
So, I have already started fixing the reject files. Will move on to build only after fixing the rejects. Good thing is not many Smali files to fix. Got only 25-30 rejects as compared to 90-95 I got with stock rom for MIUIv4 :)

But a few are giving me real trouble especially the AudioService. I may consider replacing the entire file and then merging method that don't exist in miui file, if Adam did not make any specific changes to this file. Will see that tomorrow.

Regarding language support, let's get it to boot first. One step at a time. If possible, I will add language support.
[Samsung Galaxy R i9103] Adam77Root:
Here is the build: http://www.mediafire.com/?8j2v1yqy6rbscs3,1tsbs3mz5ipisc4

libwebcore.so has been recompiled later, it is needed to get the build bootable. Also, libjni_latinime.so must be removed from the GApps package or Android keyboard will crash repeatedly. [MENTION=4524474]mj.vikram[/MENTION] has posted a fix for this somewhere previously, but I couldn't find it.
[Samsung Galaxy R i9103] mj.vikram:
it in this link Key Board Fix
[Samsung Galaxy R i9103] parajsinghal:
Thanks a lot guys. So what I am gonna do is continue with the previous build. Once I get it to boot, I will re-base to the new build.
[Samsung Galaxy R i9103] hydromax:
Thanks paraj. I look forward to.
[Samsung Galaxy R i9103] karthik050782:
Me too stuck in the same error.. I felt moving some smali to framework2 produced this error...
[Samsung Galaxy R i9103] parajsinghal:
Splitting framework is fine I guess ... I did that the last time as well. And as Adam suggested CyanogenMod does that too. The way I see it, they are just java classes packed in jars and as long as you have them in the BootClasspath you should be fine. I think the issue lies elsewhere.
[Samsung Galaxy R i9103] karthik050782:
But have you manually moved any smali from framework to framework2?
[Samsung Galaxy R i9103] Adam77Root:
I assume splitting framework is okay, there shouldn't be so many methods to reach the limit. All issues in the log can be traced back to framework2 optimization failed. I don't know so much about the internals of a dex file, but checking the logcat, I could backtrace the error (in file http://dexandroid.googlecode.com/svn/trunk/dalvik/libdex/DexSwapVerify.c):

dexFixByteOrdering() [ERROR: Byte swap + verify failed] ->

swapEverythingButHeaderAndMap() [Swap of section type %04x failed] -> case kDexTypeAnnotationsDirectoryItem ->

iterateDataSection() ->

iterateSectionWithOptionalUpdate() [Trouble with item %d @ offset 0x%x] ->

swapAnnotationsDirectoryItem() ->

swapMethodAnnotations() [Out-of-order method_idx: 0x%x then 0x%x]

dexdump (checking that offset) and dexopt (manual optimization) tool could help maybe.
[Samsung Galaxy R i9103] parajsinghal:
Thanks Adam, I was thinking to move everything from framework2 to framework3 and let only miui use framework2. So that should negate the >65K methods probability(else even i9100 and other phone builds should not compile). It should also gives us where there problem lies - framework2 or framework3 i.e MIUI or our code.

Once I establish that, I will try and use the dexdump and dexopt tool to see if they can help.
[Samsung Galaxy R i9103] parajsinghal:
Alright guys, issue resolved.

Turns out there are some issues with the scripts ( not sure if the problem was with miui or i9100 customized scripts - or maybe just I made a bad configuration somewhere :) ) and they are misbehaving / eating up errors . I was executing the entire process of generating framework jars step by step manually while I wanted to create a separate fraemework-miui.jar when I saw some errors. Fixed those and framework jars work fine now.

The build still doesnt work though, looks like some library issues or the build is just messed up becoz I pushed the framework jars manually (don't think it should coz any issue).

Logcat http://pastebin.com/DBpZBjs4

I will try to customize the scripts to work for our device later and create a complete build again.

[MENTION=4719724]Adam77Root[/MENTION] Thanks for suggesting dexdump, although it gave me the same error as in logcat, which is beyond my understanding but I could atleast test the jars on my dev env rather than flashing again and again ;) Any clue from the logcat?

[MENTION=4393631]karthik050782[/MENTION]: Yes buddy, I had to move stuff from framework to framework2 manually.
[Samsung Galaxy R i9103] Adam77Root:
I only see three errors there:

DexOpt: illegal method access (call Landroid/text/util/Linkify;.applyLink (Ljava/lang/String;IILandroid/text/Spannable;)V from Lmiui/text/util/Linkify;)

DexOpt: couldn't find field Lcom/android/internal/policy/impl/PhoneWindowManager$14;.val$screenOnListener

DexOpt: couldn't find field Lcom/android/server/am/ActivityManagerService$9;.val$doneReceivers

Otherwise, the segfault interestingly comes in android::register_android_view_InputDevice(), but there isn't any native registration issue in logs.
[Samsung Galaxy R i9103] parajsinghal:
Yeah, the DexOpt and verify(VFY) issues normally don't cause major issues. I got loads of them last time, I am actually happy to see just three;)

Moreover they are logged just once. So if there were causing the issue they should be present before each segfault. Anyway, I willl fix those and retry with a fresh build.

Sorry, I don't have any clue about segfaults. But yes, by reading your statement, it does seem a liitle stange to me. So no clue what might be causing this?
[Samsung Galaxy R i9103] Adam77Root:
It's not an intended segfault as I see. Intentional segfaults usually crash at 0xdeadbaad, in this case it is 0x0000002c. Did you fix those three errors since then?

What is 'shelld' and 'oemfix'? What are they used for?
[Samsung Galaxy R i9103] parajsinghal:
I did fix those issues but couldn't test last night. I was again getting framework2 dex optimization error with the modified script. I will now try with the manual step by step framework creation again.

I am travelling hometown over this weekend .. Not sure if I will get suffient time.

Regarding shelld, it a miui specific executable added by miui patchrom. Don't know what it does. Found in miui /system/bin folder. oemfix - have no clue about it. Problem is there is not much documentation about miui lying on the internet. Or maybe there is but no one converted from Chinese to English.
[Samsung Galaxy R i9103] Adam77Root:
Did you eventually succeed with fixing the segfault? When fixing the rejects, did you change anything in android.view.InputDevice?
[Samsung Galaxy R i9103] hydromax:
The research been stopped?

What's the latest developments?
[Samsung Galaxy R i9103] venkatkkesavan:
developers need/will not give daily status or ETA...be patient..and this is development thread...don't spam it...
[Samsung Galaxy R i9103] parajsinghal:
No the development is not stopped.

Like every summer, took a vacation and went trekking, this time to Pindari Glacier in Uttrakhand. Couldn't reach there though. I think my Indian friends must have a pretty good idea why? Still, not much trouble in Kumaon region( although some people are stuck at Pindari ), we even had mobile connectivity at places. Just had to stay a few extra days in Bageshwar district due to landslides and broken roads.

Really feeling sorry for the people stuck at various places and I hope Army and ITBP are able to rescue them.

Sorry for going off topic, its just the state of mind I am in.

So I am again at hometown, had to show my face to my parents, because they were worried and all. Will reach Noida on Monday and then I can resume work.

[MENTION=4719724]Adam77Root[/MENTION]: Was still stuck at Segfault issue before I left for vacation.
[Samsung Galaxy R i9103] parajsinghal:
Okay so came back yesterday night, and yay!! Problem solved.

So there was actually something wrong with the framework. I don't know why manual built jar was not throwing the error and giving segfault but I worked hours to drill down to the problem causing smali. Fixed a few other issues and voila!!

Past the boot loop stage now. But major issues ahead .. Nothing works. Everything keeps crashing. Worse, I can't get a logcat, adb not working... Tried everything, latest adb, changed cables, changed ports, set ro.adb.secure=0 and many other kernel changes but it just won't work.

Help needed with adb. Any clue [MENTION=4719724]Adam77Root[/MENTION]?
[Samsung Galaxy R i9103] Adam77Root:
Nice work! I knew you was gonna do it! :)

In 'init.rc', find 'adbd' and remove 'disabled' option from it. That will fix adb issues. This will have to be reverted as soon as development settings don't crash anymore.

Sent from my GT-I9103
[Samsung Galaxy R i9103] parajsinghal:
Thanks a lot. Can't wait to have a look at the logcat.

Too bad I can't work today .. Have to prepare for a JPA training I am giving tomorrow.
[Samsung Galaxy R i9103] parajsinghal:
Nope, adb still doesn't work for me :(

Strangely I alway had adb working after first install or wipe data, but only to the point where MIUI boots up. Once in MIUI adb closes and then no logcat. Not until to wipe data again. Don't get useful MIUI specific by then in on the short duation adb works. This has been happening from the beginning.

Read somewhere that MIUIv5 has 4.2.2 similar RSA security even though it runs on 4.1.2. But for most people ro.adb.secure=0 does the trick. For me it doesn't :( Any ideas?

[MENTION=4719724]Adam77Root[/MENTION]: Buddy if possible can you give a boot.img that you think should enable adb, maybe I am doing something wrong, I use AdiPat'stool to unpack and pack.
[Samsung Galaxy R i9103] Adam77Root:
Yes, it works on first install. It gets disabled when dexopting is done and services are starting.

Try setting ro.debuggable=1 as well.

Alternatively, you can try always insecure adbd file by Chainfire. I attach the necessary binary for SDK version 16 (4.1.2). This does not rely on any of the settings and gives you root shell.
[Samsung Galaxy R i9103] parajsinghal:
ro.debugable=1 is already set. I will try with the insecure adb if I get time today else I will do it tomorrow.
[Samsung Galaxy R i9103] parajsinghal:
adbd had to go in ramdisk sbin folder, right? Still adb does not recognize my device, remember, its not showing offline, it just does not recognize the device,, Strange :confused:

I must be doing something wrong. If its not much trouble, could you please build me a boot.img that you believe should work, so I am sure it is not related to the way I am making changes in the ramdisk and recreating boot.img
[Samsung Galaxy R i9103] Adam77Root:
Which boot.img are you using? Could you upload it?

Another issue I can think of is maybe disabling USB status. There is a sysfs entry for it: /sys/class/android_usb/android0/enable. MIUI maybe disables this.
[Samsung Galaxy R i9103] parajsinghal:
I am attaching both - 1st from CM10 and the 2nd I modified for MIUI
[Samsung Galaxy R i9103] Adam77Root:
Here you are. Unpacked with kitchen, replaced adbd. BTW Doesn't MIUI needs some custom bootclasspath entry?
[Samsung Galaxy R i9103] parajsinghal:
Nope, still no luck :crying:

This time I did not need to add any modofications to bootclasspath because the whole MIUI framework is now adjusted within framework.jar and framework2.jar. For ICS we had to make an additional framework-miui.jar, thus the bootclasspath addition was required.
[Samsung Galaxy R i9103] karthik050782:
Is it getting enabled at the time of boot?

I feel it is because of the security in miui

Try this : http://en.miui.com/thread-2050-2-1.html
[Samsung Galaxy R i9103] karthik050782:
No updates?
[Samsung Galaxy R i9103] parajsinghal:
Nope. I hate to say it but I haven't had time to try it yet. My dad retired this weekend and I was once again at home planning out and executing his retirement party. Will try to try it tonight.

Sorry guys, I have been unexpectedly busy recently. Not this time though, this was planned and expected :)

But I am not giving it up, not after coming so close ;)
[Samsung Galaxy R i9103] hydromax:
What is the latest situation developing?

The project continue?
[Samsung Galaxy R i9103] Grarak:
After 2 hours work
[Samsung Galaxy R i9103] happy008:
you will make this？
[Samsung Galaxy R i9103] Grarak:
sure :)
[Samsung Galaxy R i9103] Grarak:
Almost solved all issues.

Release coming soooooooon...
[Samsung Galaxy R i9103] Tha TechnoCrat:
:):rolleyes:
[Samsung Galaxy R i9103] happy008:
you are a god very expect:o:victory:
[Samsung Galaxy R i9103] Vpabc:
OH. thanks:p:p:p
[Samsung Galaxy R i9103] karthik050782:
Please create a new thread... Thanks for this work buddy, i love miui
[Samsung Galaxy R i9103] hydromax:
when it comes to the new version?
[Samsung Galaxy R i9103] happy008:
i also want to know
[Samsung Galaxy R i9103] Grarak:
never
[Samsung Galaxy R i9103] happy008:
when will you publish the new rom'miui v5'

a lot of people look forword to this rom
[Samsung Galaxy R i9103] hydromax:
I've had disappointment.
[Samsung Galaxy R i9103] mj.vikram:
why buddy what happened...
[Samsung Galaxy R i9103] Grarak:
They ask for ETA :'(
[Samsung Galaxy R i9103] D™:
lolzzzz.. that was such a straight forward answer i have ever read on XDA.
[Samsung Galaxy R i9103] Tha TechnoCrat:
Willi got real angry.

Even I got pissed when people kept asking us"Hey Team Radium when will you release CM 10.2 for Flo"?:mad:

Sent from my Galaxy R powered by Android 4.3
[Samsung Galaxy R i9103] Grarak:
Not angry about you guys :) I'm a little bit angry about the i9500 forum -.-

Anyway before this went totally off topic

There are 2 bugs to fix

1. camera

2. device doesn't boot up after wipe cache
[Samsung Galaxy R i9103] D™:
can we discuss about i9500 in Offtopic? sorry if i m wrong here but [MENTION=4443334]Grarak[/MENTION] buddy do tell me if u r facing any problem there in i9500 thread.
[Samsung Galaxy R i9103] adityaf:
Sirr please the solution for this error please

1. D/dalvikvm( 132): DEX prep '/system/

framework/ext.jar': unzip in 42ms, rewrite

625ms

2. D/dalvikvm( 132): DexOpt: --- BEGIN

'framework.jar' (bootstrap=1) ---

3. I/ServiceManager( 131): Waiting for service

broadcom.tvservice...

4. E/dalvikvm( 366): Out-of-order entry types:

0x12fb then 0x12fb

5. E/dalvikvm( 366): Trouble with item 611 @

offset 0x1593a8

6. E/dalvikvm( 366): Cross-item verify of

section type 1003 failed

7. E/dalvikvm( 366): ERROR: Byte swap + verify

failed

8. I/ServiceManager( 288): Waiting for service

media.audio_policy...

9. E/dalvikvm( 366): Optimization failed

10. W/dalvikvm( 132): DexOpt: --- END

'framework.jar' --- status=0xff00, process

failed

11. E/dalvikvm( 132): Unable to extract+optimize

DEX from '/system/framework/framework.jar'

12. D/dalvikvm( 132): Unable to process

classpath element '/system/framework/

framework.jar'

13. I/ServiceManager( 134): Waiting for service

broadcom.tvservice...

14. D/dalvikvm( 132): DexOpt: --- BEGIN

'framework2.jar' (bootstrap=1) ---

15. E/dalvikvm( 367): outsSize (6) >

registersSize (4)

16. E/dalvikvm( 367): Trouble with item 3051 @

offset 0x168d10

17. E/dalvikvm( 367): Swap of section type 2001

failed

18. E/dalvikvm( 367): ERROR: Byte swap + verify

failed

19. E/dalvikvm( 367): Optimization failed

20. W/dalvikvm( 132): DexOpt: --- END

'framework2.jar' --- status=0xff00, process

failed

21. E/dalvikvm( 132): Unable to extract+optimize

DEX from '/system/framework/framework2.jar'

22. D/dalvikvm( 132): Unable to process

classpath element '/system/framework/

framework2.jar'
[Samsung Galaxy R i9103] Adam77Root:
Team Radium?

Sent from my LG-P880
[Samsung Galaxy R i9103] D™:
Yes..exactly.

Thanks,

Disturbed™

______________________________________________________

Wait for my time, U gonna pay for what U have done. - Disturbed™
[Samsung Galaxy R i9103] Adam77Root:
Haha buddy, very informative. :D

Sent from my LG-P880
[Samsung Galaxy R i9103] Mr.Spummy:
They make roms for micromax.
[Samsung Galaxy R i9103] Adam77Root:
The ICS version of CM Gapps works fine, I use those. You can add it to the OP.

Regarding music: it works well now, I might not have waited enough for it to finish media scanning. :D

Maybe another issue: when I reboot into recovery in the MIUI software update app (I didn't try normal reboot), the phone hangs with a blank screen and touchkey backlight turned on.

Yes, everything works fine except some minor issues. Feel free to flash! :beer:

Sent from my GT-I9103
[Samsung Galaxy R i9103] parajsinghal:
Yes buddy they work alright. But there is more work needed to close some open issues and to attain overall stability.
[Samsung Galaxy R i9103] Bhavik Jain:
Dude u said that it is ported. Can u plz post a guide on how to port rooms plz :begging: