Related
Hi All
I posted this information in the HardSPL thread, but I realise that most people won't read that thread again if HardSPL has already worked for them - so I'm posting here in the hope someone might have an idea. I have read the entire HardSPL thread and there is no mention of errors like I am getting:
I tried setting both registry keys mentioned in the original post of the HardSPL thread, and rebooted after applying each.
The first time I ran the batch file, I got a popup on the device, which I approved - but I still get these errors every time I run it.
{
"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"
}
I have tried from both XP 32bit, and Win7 64bit, with the same error.
I'm no expert with WinMobile, but to me the above error suggests the problem might just be a case of setting a security flag correctly somewhere?
Any and all suggestions are welcome!
My phone version details are in my signature:
Mod. edit: not dev related, moved to general
gl
Dude, first of all there are many who have problems with HSPL, if all of them make threads for their problems here it will be a mess. Second if you post it here most of us are not experts and cant help, the only one who can help is the creator, i dont know if he visit the General.
And why in your signature your phone model is T3335, i have never seen those numbers.
mirost1 said:
Dude, first of all there are many who have problems with HSPL, if all of them make threads for their problems here it will be a mess. Second if you post it here most of us are not experts and cant help, the only one who can help is the creator, i dont know if he visit the General.
And why in your signature your phone model is T3335, i have never seen those numbers.
Click to expand...
Click to collapse
Dude, first of all (as mentioned) I have read the entire thread on HardSPL, and there is nobody with these errors. Everyone who has errors with HardSPL that are not these errors, can read that entire thread, and their problems will be solved, but not this problem.
Second of all, I did not post this in General, a moderator has kindly moved it here (as mentioned) even though I thought it was Rom development related?
Third of all, I don't know if this is actually a rom problem, or simply a security problem on the phone. That is why (as mentioned) I posted this as a separate thread.
Fourth of all, my signature says T3335 because that is what my phone model is (as mentioned).
I would appreciate some valid feedback on this issue from anyone who could look at those errors and tell me if it's a problem with the phone or with the spl.
If its not a SPL or ROM problem, what could it be. I have never heard about T3335.
I just flashed my Telecom XT Touch 2 (T3335) ok with this HardSPL.
I had to go and change some registry settings ...go to my device - HKEY_LOCAL_MACHINE - Security - Policies - Policies and edit 00001001 (DWORD2) changed to DWORD1
Works sweet for me now.
skyplonk said:
I just flashed my Telecom XT Touch 2 (T3335) ok with this HardSPL.
I had to go and change some registry settings ...go to my device - HKEY_LOCAL_MACHINE - Security - Policies - Policies and edit 00001001 (DWORD2) changed to DWORD1
Works sweet for me now.
Click to expand...
Click to collapse
Effing LEGEND! I thought it was a security setting somewhere! How did you figure it out!! Thank you so much, this info needs to be added to the HardSPL thread!
It is alredy there ....
No, it is freaking not there, or else I am blind. The guide says update key 0000101B, not 00001001
I believe the Touch 2 T3335 is the WCDMA 850/2100 MHz variant of the Touch 2.
AaronNZ said:
Effing LEGEND! I thought it was a security setting somewhere! How did you figure it out!! Thank you so much, this info needs to be added to the HardSPL thread!
Click to expand...
Click to collapse
Just luck to be honest! I was stuck like you and just started playing. lol.
Anyway, have fun!
Dear newbies, please back your device up before updating, trying custom ROMs, Kernels and other modifications. Most common and easy backup methods can be found here. Please note that Acer has released firmwares that broke the update cycle. First thing to do when getting a device is a backup or you might get stuck on an old version!
Dear ROM cooks, please prompt users to create backups. Although for some it may seem common sense, other may suppose that restoring their tablet is an easy task - until Acer releases an OTA update to the current 3.1 we can't say for sure our stock 3.1 will match all the required checksums.
Please do not modify Device Information, Model number, Android version, SN and SNID if possible. I understand you take pride in your work, and you should but by over-branding the FW you can be making it very hard for developers to properly identify the device and address bugs. Some will even ignore reports from modded devices.
Thank you for your cooperation.
I agree flashing custom roms can brick a phone or tablet. Users should be aware of tue possible consequences, but they rooted the phone which makes all this possible. That by itself largely takes them outside of support.
I agree blanking sn and snid, as well as change device types etc should be pointed out where possible, but being realistic most devs will not devote the time for it.
I personally do not develop on android, but have dealt with custom roms on multiple android and other os's. I generally make I have a way to return to stable state. The net result is i have never permanately bricked a phone. Close a few times.
I think a good mandatory read post about the dangers of rooting, installing root apps or flashing romss and kernels, would a good idea before people can accesss the sub-furoms devote to that stuff.
But realize that most owners of any android, iphone, windows mobile, etc will never root(jailbreak). Only the curious. Rememberthe saying about curiousity and the cat.
DEVs - Keep up the good work.
Users - Understand the risks. If you don't understand what you are doing. THINK THREE TIMES
Hopefully, if something goes wrong someone here can help.
FLEX Version : Blank
Product SKU : 3G
SN : Blank
SNID : Blank
My Flex Version : 22_COM_GEN1 (was 04_COM_GEN1 but on my second tablet now it's 22_COM_GEN1)
My SKU should be WIFI
My SNID Should be XEH6LAN00511515CF11500
My SN Should be 11508932915
MY UID :0x03807001422172d7
How put those information back to the tablet????
rooted for sure, root explorer indeed... but where, how, etc... thanks if someone know
How to get back those lost information:
Serial Number ID (SNID)
go to https://registration.acer.com/myaccount/page11.do?link=kln2s.redirect&changedAlts=
and login
then get back your SNID from your devices list your register at ACER.... you did it didn't you ?
or that is not a SURE thing, but on my bills I have the Snid wrote down.
Serial Number (SN)
{
"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"
}
Flex Version
(that is related to the firmware, it's the last group starting with a number)
22_COM_GEN1 for the 4.010.22_COM_GEN1
SKU
WIFI
Tell that to the people trying to fix their tablet after flashing your ROM.
Just asking nicely to post a note about backing up, but no, you just have to be a jerk.
Thanks for sharing, hopefully people read it before flashing.
This is just an effort to caution the noobs and request the ROM chefs to caution the noobs, we are not trying to blame it on the Chefs, and if developers feel that noobs won't read this - well we can't force anyone to read this - but we can try and help them to not brick their device - which will lead to another 100 threads with the title " I brick my device - whats to dos now " in the dev section, if by one thread we can save 100 new threads - maybe worth a shot.
I been wanted to create this thread for longtime because i find that user way of reporting bugs isn't much positive
This lead to particular OP for the Rom Build/Mods/Apps/Themes unable to provide a proper fix
Particular problem is from the user whom take for granted steps & reading just for sake finding for "downloads"
ADDED TO THE WIKI >> HERE <<
{
"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"
}
Therefore i would like introduce few steps that make OP & User with their problem easier
Post at correct forum (Particular Device)
I found that some particular user posted on wrong forum that are not related
Example :: problem on Xperia XXXX ROM on Samsung Forum thread(This Is Improper)
Please Post on the Device Forum that dedicated for your device only
[*]Post at particular Thread that you have encounter problem
If you have a problem/bug to report on XXX Rom.Do Report on XXX Rom Thread & not YYY Rom or other's
If there's a Solution/FAQ Page for the particular rom do report on the thread instead the [DEV] thread
Doesn't require to open a thread on the Android Development Forum.It's just spam at there.We hate it(I mean you not suppose to)
[*]Do Not Use The Private Message Button
Please Never Ever Sent Any PM to developers just to report the bug you encountered.Post it on the particular thread that mentioned
Developers/OP will have an eye on it.Therefore doesn't need to sent pm to report your's
Do appreciate work by the developers & respect they have their own time too.Keep your question on thread
[*]Read OP Pages At least twice
The place that you will gain all the info you should have
Read every single notice/quote/information/instruction/faq/other's written page
Do not just head to the download section and press the download
Get every info on which particular thing you need and what you should do to install it
[*]Follow ALL the instruction given
When the OP Posted Wipe Cache & Dalvik.It mean to select that particular option only
If the OP Posted Use Only Select/Recommend Kernel.Please do only flash/install particular kernel only
Follow each and all instruction properly(No lazyness/Skipping) any one of those
[*]Search through thread whether the similar problem has been reported
Let say you have setting fc's everytime you enable the sound option.Do search before whether other user have reported or not
If The Particular Problem/Bug has been reported.Doesn't need another user to report it.(Duplicating post)
[*]Give Proper Report
Give A Report Such As This
What steps/instruction did you used?
Did you try wipe & cache
Did you tried it more then twice?
What kernel you are running on?
Which version of build you are having problem with
Do Explain the problem clearly.If you have random reboot upon selecting theme manager,
do report that it's due to the theme manager not just saying "I have random reboot"
If possible provide a screenshot
Do provide an adb logcat (everyone on this forum should have at least logcat skill)
This is one of the best answer for the dev/op to fix if you unable to describe all the problem
[*]Do not ask or force the OP/Developers to fix the problem
No matter what problem you are having,no words such as "Please" fix the problem
Developers have their own time,they choose to fix what they want,You don't pay for what you download
[*]Take your third party installation problem away
Let say you have installed a third party mod (Ex: Beats Audio) ,if you encounter any problem please post on the beats audio thread instead
If You having problem by supercharging or installing any third party patch do take to the particular thread or keep it on your own.
[*]Stop Asking Whether Will This Work Or Not
:Facepalm: Please try it yourself or see over comment by user.
If you want to know just install and test it yourself
If you afraid bricking then never go near a development thread.There's always a Risk
[*]Press thanks button to user/devs that helped you
[*]Provide logcats whenever possible
Dmesg & Logcat using simple terminal emulator
Code:
su
dmesg >/mnt/sdcard/dmesg.txt
logcat -d -v time >/mnt/sdcard/logcat.txt
Hope This Clear Enough For All User To Report Problem On What they encounter.
As developer a positive bug report are very useful to us to fix all the problem that we might not noticed
With proper method,this will not just help us to get problem solved but less unwanted post or waste of time
Any suggestion/fix can be made with reply below v
Hope this does what it does.
I recommend all user especially new member that join XDA to read this
We don't want keep reporting 10poster/spam user.Moderator have life too
very nice and helpful thread.:thumbup:
Thank you very much for this. I couldn't agree more with No.6. If it's not too much to ask, could you include a No. 12 ? 12. Provide logcats whenever possible. Logcats are like maps to help devs where to pin point the EXACT bug. If not, devs will be just as lost as you on the cause of the bug.
RohinZaraki said:
Thank you very much for this. I couldn't agree more with No.6. If it's not too much to ask, could you include a No. 12 ? 12. Provide logcats whenever possible. Logcats are like maps to help devs where to pin point the EXACT bug. If not, devs will be just as lost as you on the cause of the bug.
Click to expand...
Click to collapse
Yes,Just included that :fingers-crossed:
Indeed....It design for us to learn and use it.XDA user must have to master it before entering android development site
Zackconsole said:
[*]Provide logcats whenever possible
Dmesg using simple terminal emulator
Code:
su
cat /proc/kmsg > /sdcard/dmesg.txt
[/LIST][/SIZE]
Click to expand...
Click to collapse
shouldn't it be "adb shell dmesg > /sdcard/dmesg.txt" ?
wcypierre said:
shouldn't it be "adb shell dmesg > /sdcard/dmesg.txt" ?
Click to expand...
Click to collapse
That it via adb
the one i show is via terminal emulator
Zackconsole said:
That it via adb
the one i show is via terminal emulator
Click to expand...
Click to collapse
but still, cat /proc/kmsg is to extract the kmsg though, while your intention is to display the dmesg. just wanted to point out that error though
Good initiative, maybe put this in the wiki also?
Sent from my GT-I9300 using xda premium
_Arjen_ said:
Good initiative, maybe put this in the wiki also?
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Thanks will try do so if you recommend it
We encourage filling the wiki
Sent from my GT-I9300 using xda premium
_Arjen_ said:
We encourage filling the wiki
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Added to the wiki..sorry i am not that good in editing wiki
Zackconsole said:
Added to the wiki..sorry i am not that good in editing wiki
Click to expand...
Click to collapse
mind to fix the typo(the dmesg command) in both this thread and the wiki so that users won't be misleaded?
wcypierre said:
mind to fix the typo(the dmesg command) in both this thread and the wiki so that users won't be misleaded?
Click to expand...
Click to collapse
Added
I always wanted to do sth useful for you I will report bugs in this way from now!
Sent from my X10Mini using xda app-developers app
· Write a descriptive title. Titles such as "Please help!!!" don't count as descriptive... Yes, I know that it describes you need help. It still doesn't count.
Q&A for [KERNEL][HCR-PRO][LOLLIPOP 5.0 LRX21T][ L1-72/CM12-73]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [KERNEL][HCR-PRO][LOLLIPOP 5.0 LRX21T][ L1-72/CM12-73]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
i am really love your rom.. the stable one, but why when i try to flash new kernel, my phone boot almost 20 minutes but nothing happen.
in the end i am using the previous rom.. and btw why sometime my data could not connect ..
Problem
after flash this kernel on stock L, my Google's stuff are mess up...
Google account was erased automatically after boot
Google apps error occurred (pop up once after boot)
any Google stuff disabled... n i don't see System update tab on About phone.
did anyone confirm this?
I'm on stock lollipop and have encountered no issues with this kernel. I've flashed the last three versions.
Not sure what's going on with your install, but any kernel shouldn't be affecting the Google account on your phone, afaik.
yayakuya said:
after flash this kernel on stock L, my Google's stuff are mess up...
Google account was erased automatically after boot
Google apps error occurred (pop up once after boot)
any Google stuff disabled... n i don't see System update tab on About phone.
did anyone confirm this?
Click to expand...
Click to collapse
may be this kernel caused nuclear war ? :good:
keep go on posting like this to the forums and have fun.
JaMeVu said:
may be this kernel caused nuclear war ? :good:
keep go on posting like this to the forums and have fun.
Click to expand...
Click to collapse
I'm not feel that fun even a lil bit...
im just asking ppl who flash this kernel, if they have the same problem with me... (what's wrong with my question?) :silly:
i knew something like flash kernel won't be touch Google stuff in my previous 20+ devices... yes, im flash a holic
but my problem wasn't usual... when restore stock kernel, everything just fine...
i just need custom kernel for optimize the battery life, that's it nothing else...
regards
@JaMeVu advised me to post my question here again (http://forum.xda-developers.com/showpost.php?p=56862150&postcount=448 )
Long story short:
These are the readings I get in trickster:
{
"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"
}
I flashed busybox, but on boot trickster said I either have a broken or missing installation. So I installed busybox on rails via the recovery method (Couldn't install ***.zip from Cache or something like that) but after that I got that status
I'll quote my last post here:
evga_I said:
I'm quite careful therefore I ask beforehand. Can we trust those values? Any idea on why they are displayed higher? So then I go - 150mV to get the same result, I assume the steps remain unaltered?
All these boxes are to be checked after setting the values:
View attachment 3022256
The OP states the kernel is for more performance too, I'm thinking OC? Would you be so kind to provide me a quick check list of what settings I should set so my setup is the way you intended?
Important: If the voltages are too low and the phone won't boot or freezes, will it reset the settings on next boot or will I still be able to reflash the kernel then to get back to stock settings?
Click to expand...
Click to collapse
Any input would be greatly appreciated!
Hello:
I've posted a thread in my model of phone, to enable Miracast featura. As you probably know, Miracast feature is used in almost all phones since Android 4.2.x
Heres is the link to thread http://forum.xda-developers.com/zte-blade/general/miracast-zte-blade-l3-t3203223
I also quote the actiones I've been taking in Stock Rom rooted with KingRoot
Hi, this is my first post. I'm a self-experienced using Android. For year I had no problems with my devices. I had a Motorola G 1st generation who worked fine, but I waste it. Now, I bought ZTE Blade L3. Such as Moto G, Miracast feature is not enable (at least in my stock rom).
I want to know if this device is compatible with that technology (read that works in every phone since 4.2.x).
This phone has Android KK 4.4.4.
Tried to first connect trough WiFi Direct a Miracast Dongle (easycast), but the phone doesn't connect. Then, I tried whith screen cast option, and the same. Finally, I looked forums how to unlock modifying bootloader.ini, just as I had to do Moto G. I added the lines with BuildProp editor after rooting with Kingo Root:
persist.sys.wfd.virtual=0
persis.debug.wfd.enable=1
AAAAAND nothing happens
I need some help, first to know compatibility (wifi drect certification page is down, unfortunately), if there is a ROM that solve this problem (CM maybe?) and if there are other lines that I must add to buildprop.
Thank you very much for your asnwers, and sorry for the bad english (I'm from Chile).
If you need any further information, please ask!!! :laugh:
UPDATE: use #MirrorEnabeler and the message is "Your Rom is lacking the audio_submix file. You must contact your device mantainer and ask them NICELY no imlement it. Please refer to the red part of the original post on XDA-Developers" This going to take long time, so decided to install stock ROM from other country using SP Flash tool, to see if it has the same problem.
UPDATE 2: Stock ROM from other country, same problem. Rooted the phone to make changes using KingRoot. Followed instructions from this thread http://forum.xda-developers.com/har...experimental-enable-mirroring-device-t2812193 The thread was closed, and will create another thread for dongles (no chromecast)
It says, or those STILL having issues,
Check /system/lib/hw directory for the file "audio.r_submix.default.so".
If it doesn't exist, ask your device maintainer to add audio.r_submix.default to
the product_packages in the device.mk file. (You may not know what it means, but they will.)
So, Asked my mobile company to do the changes, they said "the manufacter must". Contacted ZTE to do what is being said, and ther is still no answer.
Will ask in thread posted after, to see if they can help me. Please let me know if somebody can run Miracasr in his Blade (also did't found another ROM that's not a Stock one)
Click to expand...
Click to collapse
I´ve trying to contact manufacter to enable the feature, but It is probable that the stock ROM (from my country) is blocking the feature, just for buying an more expensive phone.
There is NO custom Rom yet stable for my rom (MTK device)
PLEASE HELP ME!!!
Regards and SFMBE.
Got the answer from ZTE.
Said this: " am sorry to inform you that you cannot have miracast individually custom-made to use on this device hence there is no authority of Miracast.
Should there be further assistance, please do not hesitate to contact us. "
So, they cannot create the file that I asked. So, my mobile company and the manufacter said "no way dude".
CAN SOMEBODY TELL ME IF IN A CUSTOM ROM IS A WAY TO CREATE audio.r_submix.default FILE!"????
SOMEBODY CAN HELP ME PLEASE????
REGARDS
Hello
I have problems with Easycast ota and meizu mx3. After connection is just dlna option. I want to have mirror screen.
can anybody help
{
"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"
}
perfect
perfect style good working